URL Encoder and Decoder
Encode text to URL-safe format (percent-encoding), or decode URL text back to plain text — both directions update automatically.
How to use the URL encoder
- Type in the "Plain text" field to see the URL-encoded version automatically.
- Or paste URL-encoded text into the other field to decode it back.
- Both fields update each other live.
What is URL encoding?
URL encoding (also called percent-encoding) replaces characters that aren't safe in a URL — like spaces, accented letters, "&" or "=" — with a "%" followed by the character's hexadecimal value. A space, for example, becomes %20. This is necessary because certain characters have special meaning in a URL (for example, "&" separates parameters in a query string), and must be encoded if they're meant to be part of the value itself.
This tool is typically used when building links with dynamic content, debugging API calls, or reading a cryptic URL full of percent signs.
Frequently asked questions
Why do certain characters need to be URL-encoded?
Because characters like spaces, "&", "=", "?" and "#" have special meaning in URL structure. Without encoding, they would be interpreted incorrectly — for example, as a separator between parameters instead of part of the value.
What does "Invalid URL encoding" mean?
It means the text contains a "%" character that isn't followed by valid hexadecimal digits (e.g. "%ZZ"), which means the text can't be interpreted as valid percent-encoding.
Is this the same as Base64?
No, they're two different encodings for different purposes. URL encoding makes text safe to use in a URL. Base64 re-encodes text or binary data into a 64-character alphabet, often used to embed data in text formats. We also have a dedicated Base64 tool.