URL Encoder

Encode the inner address in full and paste the result after the equals sign. The colon becomes %3A, the slashes %2F, and the inner question mark and ampersands become %3F and %26, so the outer link stops falling apart. Skip this and the server reads the inner query string as its own parameters.

In a path and in ordinary query parameters %20 is the correct form; a plus is only valid in form data submitted as application/x-www-form-urlencoded. This tool emits %20, which every system accepts. Switch to a plus only when the receiving side explicitly expects form encoding.

Because bytes are encoded, not characters. A Cyrillic letter takes two bytes in UTF-8, and each byte is written as a percent plus two hex digits, giving you %D0%9F. Links grow noticeably longer as a result, which is normal but worth watching where a legacy system caps URL length.

No, and it is a common mistake. Running a full URL through an encoder turns the scheme and host into percent sequences and the link stops opening. Encode the value of a single parameter and leave the structure — the colon, the slashes, the & and = separators — untouched.

Latin letters, digits and a small unreserved set: hyphen, underscore, period and tilde. The standard says those may stay as they are. Everything else — spaces, non-Latin letters, brackets, slashes, punctuation and the reserved URL delimiters — is replaced by percent sequences.

No. The conversion is done by the page script in your open tab, so a promo code, an order number or a draft campaign tag never leaves the machine. Nothing is logged, and the clear button wipes both fields if someone else can see the screen.