🔌 Connection String Builder
Fill in your database details and get ready-to-paste connection strings — ADO.NET, JDBC, URI and Entity Framework 6 formats. Nothing you type leaves your browser.
Frequently Asked Questions
What is a connection string?
A single string that tells a database driver how to reach your database: the server address and port, the database name, credentials, and options like encryption or pooling. Each ecosystem has its own syntax — ADO.NET uses Key=Value pairs separated by semicolons, JDBC uses jdbc: URLs, and MySQL/PostgreSQL/MongoDB also accept URI form (mysql://user:pass@host/db).
What are the default ports for each database?
SQL Server 1433, MySQL/MariaDB 3306, PostgreSQL 5432, Oracle 1521, MongoDB 27017. If you leave the port blank the tool omits it, and the driver uses these defaults. SQLite is a file, so it has no host or port at all.
What does Integrated Security / Windows Authentication mean?
For SQL Server, Integrated Security=True logs in with the Windows account running your application instead of a username/password in the string — the recommended option on Windows because no secret is stored in config. When it's enabled the tool drops the User Id and Password keys automatically.
What is the difference between an Entity Framework 6 and EF Core connection string?
EF Core uses the plain provider string (the ADO.NET output above) passed to UseSqlServer()/UseMySql()/UseNpgsql(). EF 6 with an EDMX model needs the special wrapper this tool generates: metadata=res://*/Model.csdl|ssdl|msl, the provider invariant name (System.Data.SqlClient, MySql.Data.MySqlClient, Npgsql…), and the inner provider connection string with quotes escaped as " in config files.
How are special characters in passwords handled?
In Key=Value strings, values containing ; = or quotes are wrapped in single quotes ('p;ss=word'). In URI formats (mysql://, postgresql://, mongodb://) the username and password are percent-encoded, so @ : / and # in a password won't break the URL.
Is it safe to type my real password here?
The page runs entirely in your browser — nothing is transmitted, logged or stored, and the Share button excludes the password. That said, the wider best practice applies anywhere: keep connection strings in environment variables or a secret manager, not committed to source control.