What connection string formats does this support?

Any semicolon-delimited Key=Value string, which covers SQL Server, PostgreSQL (via Npgsql), MySQL and most ADO.NET-style providers, since the parser does not validate provider-specific keys, only the general Key=Value;Key=Value shape.

Is it safe to paste a connection string with a real password into this tool?

The parsing runs entirely in your browser with plain JavaScript string splitting, so the connection string and any password inside it are never transmitted anywhere, but you should still avoid pasting production secrets into any browser tab you don't fully trust.

Can I convert JSON back into a connection string?

Yes, edit the JSON object on the right and the tool joins each key and value with an equals sign and separates entries with semicolons, producing a connection string ready to paste into appsettings.json or an environment variable.

What happens if a value itself contains an equals sign?

Only the first equals sign in each semicolon-separated segment is treated as the key/value separator, so anything after it, including additional equals signs in a base64 token or password, stays part of the value.

Connection String Parser

Parse an ADO.NET/database connection string into key-values (and back), locally.

Local, Runs entirely in your browser, your data never leaves your device.

Loading tool…

Break a connection string into its Key=Value parts

ADO.NET connection strings pack a server, database, credentials and driver flags into one semicolon-separated line, which makes them tedious to read or edit by hand. This tool splits the string on each Key=Value segment into a JSON object, preserving key order and case, and converts a JSON object back into the same format. It runs locally, which matters because most connection strings carry a plaintext password.

How to use the Connection String Parser

Paste a connection string like the SQL Server example into the left panel, or edit the sample already loaded.
Read the parsed keys and values as JSON on the right, including Server, Database, User Id, Password and any driver-specific flags.
Edit the JSON directly and the tool rebuilds the equivalent Key=Value; string on the fly.
Copy the result, or send it to another tool such as the appsettings.json converter to slot it into a config file.

Parsing splits on semicolons and takes only the first equals sign in each segment, so a password containing an equals sign stays intact as part of the value.

Keys are kept exactly as typed, including their original casing and spacing, since ADO.NET providers generally treat keys case-insensitively but round-tripping the original text avoids surprising a downstream tool that does not.

Frequently asked questions

What connection string formats does this support?: Any semicolon-delimited Key=Value string, which covers SQL Server, PostgreSQL (via Npgsql), MySQL and most ADO.NET-style providers, since the parser does not validate provider-specific keys, only the general Key=Value;Key=Value shape.
Is it safe to paste a connection string with a real password into this tool?: The parsing runs entirely in your browser with plain JavaScript string splitting, so the connection string and any password inside it are never transmitted anywhere, but you should still avoid pasting production secrets into any browser tab you don't fully trust.
Can I convert JSON back into a connection string?: Yes, edit the JSON object on the right and the tool joins each key and value with an equals sign and separates entries with semicolons, producing a connection string ready to paste into appsettings.json or an environment variable.
What happens if a value itself contains an equals sign?: Only the first equals sign in each semicolon-separated segment is treated as the key/value separator, so anything after it, including additional equals signs in a base64 token or password, stays part of the value.