How to encode or decode a URL
- Choose Encode or Decode.
- Pick what you're working with: a single query value or path part, or a whole URL.
- Paste your text. The result appears as you type, and errors point to the exact character.
- Copy the result, or press Swap to check it round-trips.
Common percent-encodings
| Character | As typed | Encoded |
|---|---|---|
| Space | (space) | %20 |
| Ampersand | & | %26 |
| Equals | = | %3D |
| Question mark | ? | %3F |
| Slash | / | %2F |
| Hash | # | %23 |
| Plus | + | %2B |
| é | é | %C3%A9 |
Why URLs need encoding
Characters such as &, = and ? have jobs in a URL: they separate parameters and values. When one of them appears inside a value, say a search for “fish & chips”, it has to be written as a % followed by its hex code so the server reads it as text. Non-English letters are encoded the same way, byte by byte, from UTF-8.
Common uses
- Putting a search term in a link. Encode a value such as a name with an ampersand before adding it to a query string, so it doesn't split into two parameters.
- Reading a tracking link. Links in emails and ads are full of %20, %3D and %2F. Decode them to see the real destination and every parameter in plain text.
- Reading form data from a log. Decode a form submission from a request log with + means space turned on to see what was actually typed.
- A redirect URL inside another URL. Login and redirect links carry a whole address as a parameter. Encode it with Query value or path part, so its own ? and & don't break the outer link.