Download Supabase JDBC Driver

Download the Supabase JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the Supabase JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Supabase. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each Supabase driver uses its own syntax — see the connection details below.

The Supabase JDBC driver

Supabase is an open-source Firebase alternative built on top of PostgreSQL, providing a full backend-as-a-service platform with a hosted database, authentication, real-time subscriptions, and storage. It exposes the underlying PostgreSQL database directly, giving developers full SQL access and the ability to use any PostgreSQL-compatible tool. Supabase supports extensions such as pgvector for AI embeddings and PostGIS for geospatial data.

The Supabase JDBC URL

• Required File(s): postgresql-xxx.jar
• Java Driver Class: org.postgresql.Driver
• JDBC URL: jdbc:postgresql://{HOST}:{PORT}/{DB}
• Website: Supabase

Connecting to Supabase

Supabase offers the same database through three routes, and the one you pick decides both the port and the user name. Open Connect on the project dashboard to see all of them.

1. Pick a route that suits a JDBC client. The direct connection on port 5432 and the session pooler on port 5432 both behave like an ordinary PostgreSQL server. Avoid the transaction pooler on port 6543: it does not support prepared statements, which the PostgreSQL JDBC driver relies on.
2. Check that your network can reach it. The direct connection is IPv6 unless the project has the IPv4 add-on, which is why it fails on many home and office networks. The shared pooler answers over IPv4 on every plan — use it when the direct host does not resolve for you.
3. Use the matching user name. A direct connection signs in as postgres. Through a pooler the user carries the project reference, as in postgres.abcdefghijklmnop. Copying the host from one route and the user from another is the usual reason authentication fails.
4. Copy the JDBC URL from the Supabase dashboard. You will find it in the Connect dialog, which shows a string per route.
5. Paste the URL into DbSchema. In the Connection Dialog set Connection Mode to Edit the JDBC URL Manually and paste the string you copied. The user and the password are entered in the first tab, not in the URL.

Keep ?sslmode=require in the URL, and put the password in the password field rather than in the string. Row Level Security policies do not block schema reading, so tables, foreign keys and pgvector columns all reverse engineer normally.

DbSchema and Supabase

DbSchema connects to Supabase PostgreSQL using the standard JDBC driver, visualizing tables, Row Level Security policies, foreign key relationships, and pgvector extension columns, making it easier to design and document your Supabase database schema.