URL Decode
Decode percent-encoded (URL-encoded) text back into readable characters instantly in your browser. Reveal the real content of a tracking link, read an encoded value from server logs, or translate a non-ASCII filename from a Content-Disposition header.
Usage examples
Reading garbled text copied from a browser address bar
If a query parameter in the address bar looks like %EC%95%88..., paste it in to see what the original text was.
Checking an encoded value left in server logs
When an access log or request parameter still has an encoded value, decode it to read the actual input.
Revealing the hidden content of a shared link
If a parameter in a link someone sent you is encoded and hard to read, decode it to see the actual content.
Reading a webhook payload captured for debugging
Paste an encoded body or header value logged from an incoming webhook request to see the literal data your endpoint actually received.
Translating a non-ASCII filename from a Content-Disposition header
When a download header shows something like filename%2A%3DUTF-8%27%27%E6%97%A5%E6%9C%AC%E8%AA%9E.pdf, decode it to confirm the intended file name before writing custom parsing logic.
Quick reference
ASCII characters
| Encoded | Decoded |
|---|---|
| %20 | U+0020 |
| %21 | ! |
| %22 | " |
| %23 | # |
| %24 | $ |
| %25 | % |
| %26 | & |
| %27 | ' |
| %28 | ( |
| %29 | ) |
| %2A | * |
| %2B | + |
| %2C | , |
| %2F | / |
| %3A | : |
| %3B | ; |
| %3C | < |
| %3D | = |
| %3E | > |
| %3F | ? |
| %40 | @ |
| %5B | [ |
| %5C | \ |
| %5D | ] |
| %7B | { |
| %7C | | |
| %7D | } |
| %0A | U+000A |
| %0D | U+000D |
| %09 | U+0009 |
| + | + |
UTF-8 multi-byte sequences
| Encoded | Decoded |
|---|---|
| %C3%A9 | é |
| %C3%B1 | ñ |
| %C3%BC | ü |
| %E2%82%AC | € |
| %C2%A9 | © |
| %E2%80%94 | — |
| %ED%95%9C | 한 |
| %E6%97%A5 | 日 |
| %F0%9F%98%80 | 😀 |
Frequently asked questions
Is the text I paste sent to a server?
No. Decoding happens entirely in your browser, and what you paste is never sent to a server.
Why am I seeing an error?
You'll see an error when the input doesn't match valid URL-encoding format — for example, a % followed by something other than two hex digits, or a string that cuts off mid-sequence.
Does + also turn into a space?
No. This tool follows the encodeURIComponent/decodeURIComponent convention, where only %20 decodes to a space. Treating + as a space is a separate rule used only for form submissions (application/x-www-form-urlencoded).
What happens if I paste plain text?
If there's no percent-encoding in it, your input just passes through unchanged. It won't error out, so it's safe to try.
What's the difference between this and decodeURI?
This tool uses decodeURIComponent semantics, which decodes every percent-encoded character, including reserved ones like &, =, and / that decodeURI deliberately leaves encoded because they're structurally meaningful in a full URL. decodeURIComponent is the right choice for decoding an individual value, like one query parameter, rather than a whole URL.
Can I decode an entire URL with query parameters in one go?
You can, but be aware that unencoded structural characters like ? and & in the original URL will stay as-is since they were never percent-encoded, while every %XX sequence elsewhere in the string will be decoded. For inspecting individual parameter values, it's often clearer to decode them one at a time.
Why does multi-byte text decode into a single readable character instead of multiple symbols?
Percent-encoding represents each raw UTF-8 byte of a character separately, so a non-ASCII character often becomes several %XX sequences in a row — for example, é becomes %C3%A9. When decoded together, those bytes are reassembled into the one correct character, which is expected UTF-8 behavior, not an error.