URL Encoder / Decoder

About URL Encoder / Decoder

URL Encoder / Decoder converts text to percent-encoding and back. Choose Encode to turn spaces, symbols and non-ASCII characters into safe %XX sequences for query strings and URL parameters, or Decode to make an encoded URL readable again. It uses the browser's encodeURIComponent and decodeURIComponent, so characters like /, ?, & and = are encoded too, which is what you want for a single parameter value. When decoding, + is read as a space, as in query strings and HTML forms. The output updates as you type, malformed input is highlighted with an error message instead of a broken result, and the output has a copy button. Developers use it to build API requests, debug redirect URLs and read encoded links.

How to use

1. Select Encode to percent-encode text, or Decode to turn an encoded string back into readable text; switching modes moves the current result into the Input box so you can convert it back.
2. Type or paste your text or URL into the Input box; the result appears in the Output box as you type.
3. Click Copy next to Output to copy the result to your clipboard, or CLEAR next to Input to start over.

Limitations & notes

• Encoding uses encodeURIComponent, so characters such as :, /, ?, & and = in a full URL are encoded too.
• Decoding turns + into a space, as form encoding does; a literal plus must be written as %2B, which is how the encoder outputs it. An unencoded + in a URL path will therefore decode as a space.
• Switching between Encode and Decode moves the current output into the Input box, so the new output shows it converted back; if there is no output yet (empty or invalid input), your input is left as is.

FAQ

What is URL encoding?

URL encoding, also called percent-encoding, replaces characters that are not allowed or have special meaning in a URL with a % followed by two hex digits. For example, a space becomes %20.

Why are slashes and colons encoded in my URL?

This tool encodes every reserved character, as encodeURIComponent does, because it is meant for individual parameter values. Encode only the value part (for example the search term) rather than the whole URL if you want to keep the structure.

Should a space be %20 or +?

In URL paths and with encodeURIComponent, a space is %20. The + form is used in HTML form encoding (application/x-www-form-urlencoded) and many query strings. This encoder always writes %20, and the decoder accepts both, turning + into a space.

Why does decoding show an error?

The input contains a % that is not followed by two valid hex digits, or a sequence that is not valid UTF-8. The Input box is highlighted and an error message appears below it; fix or remove the stray % and try again.