Connection string builder & decoder
Fill in a form and get the connection string in every format your drivers use - ADO.NET, JDBC, ODBC, URLs, libpq, Go DSNs and more - side by side. Or paste one to see what every key does and what is risky. It all runs in your browser: nothing you type is sent anywhere.
Open this connection in SQLly
Opens SQLly's connection editor filled in.
Open this connection in SQLly
Private by design. The builder and decoder are plain JavaScript running in this tab. The page sends no request with what you type, stores nothing (not even in your browser), and keeps working offline once loaded. The Open in SQLly link goes from your browser straight to the app on your computer.
Pick your database
Each engine page opens the builder on that engine and adds a full keyword reference, its common connection errors and their fixes.
SQL Server
ADO.NET, ODBC, JDBC, Go URL, SQLAlchemy URL
PostgreSQL
URI, Keyword/value, ADO.NET (Npgsql), JDBC, ODBC
MySQL
URI, JDBC, ADO.NET, ODBC, Go DSN
MariaDB
JDBC, ADO.NET, Go DSN, SQLAlchemy URL, URI
SQLite
File path, URI filename (read-only), ADO.NET, JDBC, SQLAlchemy URL
Oracle
Easy Connect, Easy Connect over TLS, Connect descriptor, JDBC thin, ADO.NET (ODP.NET)
Redis
URI with TLS, URI with an ACL user (Redis 6+), StackExchange.Redis, redis-cli
ClickHouse
HTTP URL, Native DSN, JDBC, ADO.NET
DuckDB
File path, JDBC, SQLAlchemy URL, CLI, read-only
libSQL
Database URL, URL with auth token, Local sqld
Connection string formats, and how to escape them
Most connection-string bugs are escaping bugs: a password with an @, a ; or a quote that the driver splits in the wrong place. Each format has its own rule.
| Format | Looks like | Special characters |
|---|---|---|
| URL / URI | postgresql://user:pass@host:5432/db?sslmode=verify-full | Percent-encode reserved characters in the user, password and database: @ → %40, : → %3A, / → %2F, ? → %3F, # → %23, % → %25, space → %20. |
| ADO.NET | Server=host;Database=db;User ID=u;Password=p; | Wrap a value with ;, a leading or trailing space, or a leading quote in "…" (or '…'), and double the quote character inside: Password="a;b""c". |
| ODBC | Driver={ODBC Driver 18 for SQL Server};Server=host;Pwd={p;w}; | Wrap the value in braces. Driver names always are. |
| JDBC | jdbc:sqlserver://host;databaseName=db, jdbc:postgresql://host/db?user=u | Vendor-specific. Microsoft: braces, with } doubled. PostgreSQL, MySQL, MariaDB: URL query, so percent-encode. |
| libpq keyword/value | host=h dbname=db user=u password='a b' | Single-quote values that are empty or contain spaces; write \' and \\ for a quote or backslash. |
| Go MySQL DSN | user:pass@tcp(host:3306)/db?tls=true | The password needs no escaping; parameter values are URL-escaped; parameter names are case-sensitive. |
| StackExchange.Redis | host:6380,password=p,ssl=true | Commas separate options, so a password with a comma has to be set in code. |
| Oracle Easy Connect | host:1521/service_name | No credentials inside; pass the user and password separately. |
What the decoder checks
- Certificate checks turned off.
TrustServerCertificate=true,sslmode=require,tls=skip-verify,sslMode=trustand pgJDBC'sNonValidatingFactoryall encrypt without checking who answered. - No TLS, or TLS that can fall back.
sslmode=disableorprefer,Encrypt=False,ssl-mode=DISABLED,redis://with a password, plain HTTP to ClickHouse. - Defaults that changed. No
Encryptmeans encrypted and validated in Microsoft.Data.SqlClient 4.0+, ODBC Driver 18 and JDBC 10.2+, but not in older drivers or go-mssqldb. - Secrets in the string. Plain-text passwords and auth tokens,
Persist Security Info=True, Turso tokens that have expired. - Typos and borrowed keywords. Unknown keys for the detected driver,
host:portwhere SQL Server wantshost,port, case-sensitive Go parameters, unescaped@in URL passwords, an Oracle SID that should be a service name. - How SQLly reads it. The decoder also runs the same rules as the SQLly app's own connection-string reader, so you know what the app will fill in.
Connection string FAQ
Is my connection string sent anywhere?
No. The builder and the decoder are JavaScript that runs in your browser tab. Nothing you type or paste is uploaded, logged or stored, not even in your browser's storage, and the page keeps working with the network switched off once it has loaded.
Which databases and drivers does it cover?
SQL Server and Azure SQL, PostgreSQL, MySQL, MariaDB, SQLite, Oracle, Redis and Valkey, ClickHouse, DuckDB, and libSQL / Turso. For each engine it writes the formats that really exist for it: URLs, ADO.NET, JDBC, ODBC, libpq keyword/value strings, Go DSNs, SQLAlchemy URLs, StackExchange.Redis strings, Oracle Easy Connect and TNS descriptors, plus ready-to-paste code for Python and Node.js.
How do I put special characters in a password?
It depends on the format. In a URL, percent-encode them: @ becomes %40, : becomes %3A, / becomes %2F, % becomes %25. In an ADO.NET string, wrap a value that contains ; or a quote in double quotes and double any double quote inside. In ODBC and Microsoft's JDBC driver, wrap it in braces {...} and double a closing brace. In a libpq keyword/value string, use single quotes and backslash-escape ' and \. The builder does all of this for you.
What does the decoder check?
It reads the string the way the driver would, lists every key with what it does, and flags problems: certificate checks turned off (TrustServerCertificate=true, sslmode=require, tls=skip-verify), TLS disabled or optional, plain-text passwords and tokens, misspelled or unknown keywords, host:port where SQL Server wants host,port, unescaped characters in URL passwords, SID-versus-service-name mix-ups in Oracle, and defaults that changed between driver versions such as Encrypt in Microsoft.Data.SqlClient 4.0.
Why does my connection fail with a certificate error after a driver upgrade?
Microsoft.Data.SqlClient 4.0, ODBC Driver 18 and the Microsoft JDBC Driver 10.2 all switched to encrypting by default and validating the server's certificate. A SQL Server that still uses its self-signed certificate then fails with "The certificate chain was issued by an authority that is not trusted". Install a certificate from a CA your clients trust; set TrustServerCertificate=true only for local development.
What is "Open in SQLly"?
SQLly is a desktop SQL client for macOS, Windows and Linux. The button builds a sqlly://connection/new link that opens SQLly's connection editor already filled in with your host, port, database and user. The password is only put in the link if you tick the box, and SQLly never writes it to its connection file. The link goes straight from your browser to the app on your computer; it does not pass through any server.
Engine guides
Connect once. Then just write SQL.
SQLly is a native SQL workbench for macOS, Windows and Linux. Paste a connection string into its connection editor, keep passwords in your system keychain, and get schema-aware IntelliSense on database and more.