Connection URLs that do not break.

Type your username, password and server. Get a correct connection URL, with every special character percent-encoded.

Everything runs in your browser — nothing is stored, nothing is sent to any server.

Your connection URL

Username only
Password only

Why a password can break a URL

A connection URL looks like smtp://user:password@server:587. It uses some characters as separators. The @ separates the login from the server. The : separates the username from the password. When your username or password contains one of these characters, the program reads the URL in the wrong place and the connection fails.

The fix is to write each special character as a percent code. For @, write %40. Only the last @, the one before the server name, stays as it is. This tool does that for you.

The percent codes

CharacterWrite it asWhat it does in a URL
@%40Separates the login from the server
:%3ASeparates username, password and port
/%2FStarts the path
#%23Cuts off the rest of the URL
?%3FStarts the options
[ ]%5B %5DReserved for IPv6 addresses
%%25Starts a percent code
&%26Separates options

FAQ

My username is an email address. Do I encode its @ too?
Yes. [email protected] becomes user%40example.com. Only the last @ in the URL stays, the one before the server name.
Which characters are always safe?
Letters, digits and these four symbols: - _ . ~. This tool encodes everything else. The password generator can make passwords that use only these symbols.
Is it safe to type my password here?
The encoding runs in your browser. No request is made. You can verify: open your browser's network tab and type. The password field is hidden by default, and the result is hidden too.
Where do I use the result?
In settings that take one connection string: SMTP_URL, DATABASE_URL, REDIS_URL, mailer DSNs, and similar. If your application has separate fields for username and password, type them as they are. Do not encode them.

More free tools