Introduction

The Syntax Headache

Every modern backend framework (like Prisma, Django, Rails, or Express) usually requires you to provide a single DATABASE_URL environment variable to connect to your database.

However, the syntax for these connection strings is notoriously easy to mess up. A single misplaced slash or an un-escaped special character in your password can result in hours of debugging "Authentication Failed" or "Invalid Hostname" errors.

The Anatomy of a Database URI

Almost all database URIs follow a standard structure based on RFC 3986:

dialect://username:password@host:port/database?options

1. The Dialect

This tells the driver what protocol to use.

• PostgreSQL: postgresql:// or postgres://
• MySQL: mysql://
• MongoDB: mongodb:// or mongodb+srv:// (for cloud clusters)
• Redis: redis:// or rediss:// (for SSL)

2. The Credentials

This is your username and password. If your password contains special characters like @ or /, you must URL-encode them. (Our tool does this automatically).

3. The Host and Port

This is the IP address or domain name of your database server.

• Default Postgres Port: 5432
• Default MySQL Port: 3306
• Default MongoDB Port: 27017
• Default Redis Port: 6379

4. The Database Name

The specific logical database you are connecting to on that server.

5. Query Options (Optional)

Additional configuration flags passed to the driver. For example, ?sslmode=require ensures that the connection to the database is encrypted, which is often mandatory for cloud providers like Supabase or Heroku.

How to use this generator

Simply select your database dialect from the dropdown, fill in your credentials, and the tool will instantly assemble the perfect, URL-encoded string. You can toggle the password visibility to ensure it is encoded correctly before copying it to your .env file.