PostgreSQL Connection URL Builder
Build a PostgreSQL connection URL from individual fields — host, port, credentials, SSL mode, schema, and pool options — with correct percent-encoding and a Prisma-compatible variant. Processed locally, never transmitted.
Free to use · Runs in your browser · No account required
Processed locally in your browser
Nothing you enter here is uploaded, transmitted to a server, or stored by this tool. Connection details are processed locally and never transmitted or stored — avoid real production credentials on shared devices.
Runs entirely in your browser — nothing is sent to a server
Connection details
Scheme prefix — postgres:// is an accepted alias.
Default 5432.
Special characters are percent-encoded automatically.
Prisma variant only.
Prisma variant only.
Prisma variant only.
One key=value per line, or & separated. Duplicate keys collapse to the last value.
Connection string
postgresql://localhost:5432/?sslmode=prefer
How to use this tool
- 1Fill in host, port, database, and credentials — or load the example to see it populated.
- 2Pick an SSL mode appropriate for your environment (require or stricter in production).
- 3Switch between Standard and Prisma output — Prisma adds schema, connection_limit, and pool_timeout.
- 4Use Reveal password only when you're sure no one else can see your screen, then copy the result.
Every part of the URL, explained
- protocol
- The scheme, always postgresql:// (postgres:// is an accepted alias).
- username / password
- Credentials before the @ — percent-encoded so special characters can't break the URL.
- host
- The server's hostname or IP address.
- port
- The TCP port PostgreSQL listens on — 5432 by default.
- database
- The database name, after the final /.
- sslmode
- How strictly the client verifies TLS — see the SSL mode notes below.
- schema
- Prisma-specific: the default schema for the connection.
- connection_limit / pool_timeout
- Prisma-specific: connection pool size and the seconds to wait for a free connection.
SSL modes, from least to most strict: disable, allow, prefer, require, verify-ca, verify-full. disable never uses TLS; require encrypts but doesn't verify the server certificate; verify-ca and verify-full additionally validate the certificate chain and hostname. Most managed Postgres providers expect at least require.
Encoding matters: characters like @, :, /, and # have special meaning inside a URL. An unescaped password containing one of these can silently truncate the connection string or point the client at the wrong host — this tool percent-encodes your username and password automatically.
Frequently asked questions
Are my credentials sent anywhere?
No. The connection string is assembled entirely in your browser using JavaScript's URL encoder — nothing is transmitted or logged.
Why does my password look different in the URL?
Characters such as @, :, /, and # have special meaning inside a URL. This tool percent-encodes your password so the connection string parses correctly.
What's the difference between the standard and Prisma output?
Both use the same postgresql:// scheme. The Prisma variant additionally appends schema and connection_limit/pool_timeout query parameters that Prisma's client reads directly.
Related writing
- PostgreSQL Connection URL Explained, Piece by PieceA component-by-component breakdown of the PostgreSQL connection URL — user, password, host, port, database, and query parameters — plus safe environment-variable handling.
- How to URL-Encode Special Characters in PostgreSQL Connection StringsEncode PostgreSQL usernames and passwords safely without breaking the scheme, host, port, database name, or query parameters.
- PostgreSQL SSL Modes Explained for Node.js and PrismaUnderstand PostgreSQL sslmode choices, certificate and hostname verification, and the differences between libpq, node-postgres, Prisma, and hosted providers.
- PostgreSQL Connection Pooling: Direct Connection vs PoolerCompare direct PostgreSQL connections, application-side pools, and external poolers for persistent Node.js, serverless, Prisma, and migration workloads.
Planned — not yet published
- PlannedPrisma DATABASE_URL configuration for local, staging, and production— Pooling, `schema`, and `sslmode` differences per environment.
- PlannedFixing Prisma P1001: "Can't reach database server"— A triage flow from DNS to firewall to pool exhaustion.
Related tools
- Configuration
Environment File Validator
Check .env content for duplicate keys, malformed lines, and missing values.
- API development
CORS Configuration Generator
Generate framework-specific CORS configuration from your allowed origins and methods.
- Data formatting
JSON Formatter & Validator
Format, minify, and validate JSON with clear syntax-error locations.