Connection String Parser
Free and fully in-browser.
Loading tool...
What is Connection String Parser?
A connection string parser breaks a database connection string into its individual parts — scheme, username, password, host, port, database name, and options — so you can verify each value before pasting it into a deploy config. It understands the URL format used by PostgreSQL, MySQL, MongoDB, and Redis, the ODBC / ADO key=value format, the libpq keyword/value format, and the SQL Server tedious URL form. Edit any field and the tool rebuilds a valid string in the same format.
Key Benefits
- Instantly see every component of a connection string
- Edit fields and rebuild a valid string safely
- Supports URL, ODBC, and libpq formats
- Password masking for screen shares
- Runs offline — credentials never leave the browser
Common Use Cases
- •Verifying credentials before deploying to staging or production
- •Retargeting a local connection string for a cloud provider
- •Debugging failed database connections part by part
- •Onboarding developers who are new to connection string formats
- •Auditing .env files for unexpected or outdated options
How to Use the Connection String Parser
- Paste the connection string: Paste any postgres://, mysql://, mongodb://, redis://, or Server=...; string into the input box.
- Review the detected parts: The tool detects the dialect and splits the string into username, password, host, port, database, and options.
- Edit fields if needed: Change any field — host, port, database name, or options — to retarget the string for another environment.
- Copy the rebuilt string: Copy the rebuilt connection string and paste it into your .env file or deploy configuration.
Key Features
- Parses URL-style strings for PostgreSQL, MySQL, MongoDB, Redis, and SQL Server
- Understands ODBC / ADO and libpq keyword=value formats
- Edit any field and rebuild a valid connection string instantly
- Password show/hide toggle for screen shares and demos
- Detects the database dialect from the scheme automatically
Frequently Asked Questions
What connection string formats does this tool support?
It parses URL-style strings (postgres://user:pass@host:5432/db?opt=1) used by PostgreSQL, MySQL, MongoDB, Redis, and AMQP, ODBC / ADO strings (Server=...;Database=...;User Id=...;), libpq keyword/value strings (host=x port=5432 dbname=y), and the SQL Server tedious URL form (sqlserver://host;database=db;user=u;password=p).
Is my password sent anywhere?
No. All parsing happens locally in your browser with plain string operations — nothing is uploaded, logged, or stored. The same code runs offline once the page is loaded.
What is the difference between URL and ODBC connection strings?
URL strings start with a scheme like postgres:// and are common in web frameworks and hosted providers. ODBC / ADO strings use semicolon-separated key=value pairs like Server=host;Database=db and are common in .NET and Windows tooling. libpq keyword/value strings (host=x dbname=y) are the native PostgreSQL CLI format.
Why does editing a field change the rebuilt string?
The parser splits the string into structured fields, and the output is rebuilt from those fields — not by copying the input. If a field has no value (for example no port), it is simply omitted from the output, which keeps the rebuilt string valid.