.NET Connection String Builder
Build or parse SQL Server, PostgreSQL, and Redis connection strings with the real .NET builder types. Fill in the fields, or paste an existing string to break it apart.
Private by design: everything runs in your browser. Nothing is sent to a server, and passwords never leave this tab.
Fields
Waiting for the .NET runtime…
Connection string questions
How do I build a SQL Server connection string in .NET?
Use a connection string builder: set properties like Server, Database, and Integrated Security, then read ConnectionString. This tool does that with .NET's DbConnectionStringBuilder, so quoting and escaping match what .NET produces.
Is my password sent anywhere?
No. The builders run as .NET compiled to WebAssembly inside your browser tab. Nothing is uploaded, logged, or stored, so passwords stay on your machine.
Why does the SQL Server tab say it uses the generic builder?
Microsoft.Data.SqlClient is not available in WebAssembly, so SQL Server strings use the generic .NET DbConnectionStringBuilder. Quoting and escaping are real .NET, but keywords are not validated or normalized to their synonyms (Server vs. Data Source).
What does a PostgreSQL connection string look like for Npgsql?
A semicolon-separated list such as Host=localhost;Database=mydb;Username=app;Password=secret. The PostgreSQL tab uses NpgsqlConnectionStringBuilder, so keywords are validated.
What format does StackExchange.Redis use?
A comma-separated string: the endpoint first, then options, for example localhost:6379,ssl=true,password=secret. The Redis tab parses and writes it with ConfigurationOptions.