Encode and decode URLs.

Component mode escapes everything except letters, digits and - _ . ! ~ * ' ( ), so slashes, ampersands and equals signs are encoded. Full URL mode leaves those structural characters alone, so the scheme, the path and the query string keep working.

Yes. Each character outside ASCII becomes its UTF-8 bytes, percent-encoded, so é becomes %C3%A9. Decoding turns them back.

No. The conversion runs in this page and makes no request with your text.

Yes. Encoding and decoding need no account and cost nothing, and there is no limit on how often you use them.

The decoder follows the percent-encoding rules, where + is an ordinary character. HTML forms write spaces as +, so a query string from a form keeps its plus signs here. Replace them with %20 first if you need spaces back.

Every % has to be followed by two hexadecimal digits. A lone %, or one followed by anything else, stops the decode and the tool explains why. A literal percent sign is written as %25.

Decoding %26 would turn it into &, which would split one query value into two. Full URL mode keeps the escapes of structural characters as they are, so the address means the same thing. Component mode decodes them all.

It is encoded again. Each % becomes %25, so %20 turns into %2520. Decode first if you are not sure which you have.

It treats the box as one piece of text, and a line break is encoded as %0A in both modes. Paste one URL at a time when each needs its own result.

No. The text lives in this page while it is open, and nothing is saved in the browser or sent anywhere.

No. It only rewrites characters a URL cannot carry, and anyone can reverse it. Do not rely on it to hide a value.

Not if you want it to keep working as a link. Component mode escapes the slashes, the colon after https and the ? before the query, so the result reads as one value. Use it for a URL that goes inside another URL's query string, such as a redirect address.

Both modes write a space as %20. A + for a space belongs only in form data, and this tool never writes one.

Each byte that cannot appear in a URL as it is gets written as % and two hexadecimal digits. A space is %20, and é, which is two bytes in UTF-8, becomes %C3%A9.

In Component mode # becomes %23, so it stays part of the value. Left as # in a URL, it would start the fragment and cut the value short.

Any part holding text that can contain spaces, accents or symbols, most often a query value or a path segment. The scheme, the domain and the separators between the parts stay as they are.

No. Letters keep their case, and the hex digits the encoder writes are upper case, as in %C3%A9. Decoding accepts either case.

Each escaped byte takes three characters, so a space grows to %20 and an accented letter to six characters. Text in a script that uses more bytes per letter grows more.

No. It encodes or decodes whatever text you give it and does not check that the result is a working address. A typo in the domain stays a typo.

No. The box takes text of any length, and the result updates as you type.

Yes. Choose Decode with Component mode and every escape turns back into its character, %26 and %3D included. The & and = signs that come back no longer show where each value ends, so read the result rather than reuse it.

Use Full URL mode, which keeps the slashes. Component mode turns each / into %2F, which is right for a single path segment and wrong for a whole path.

No. The ' is one of the characters both modes leave alone, along with ( ) ! ~ and *. Write it as %27 by hand if the place you paste the URL needs it escaped.