Turn percent-encoded URLs and parameters back into readable text - locally in your browser, with no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Links and addresses are full of cryptic sequences like %20, %C3%A4 or %2F - that is percent-encoded text made transport-safe. To read or process it, though, you want it back in plain form. This tool decodes such strings: %20 becomes a space, %C3%A4 becomes ä. That way you immediately see what a link or a parameter really contains.
Optionally you can treat plus signs as spaces. That is needed when the data comes from a classic web form (application/x-www-form-urlencoded), because there a plus sign stands for a space instead of %20. Without this option a plus sign stays unchanged, as plain URL encoding specifies. That way the result matches exactly the source your text comes from.
Decoding runs entirely locally in your browser in pure JavaScript - your text is not uploaded, not stored, and no foreign library is loaded from a CDN. If a %-sequence is broken (such as a lone % without valid hex digits), the tool says so honestly instead of inventing a wrong result. You can download the result as a text file.
| Input formats | Text input |
|---|---|
| Output format | TXT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: The tool decodes percent-encoding per RFC 3986; it does not decrypt anything and does not check whether an address is reachable. An invalid %-sequence leads to an honest error instead of a wrong result. Whether a plus sign is a space depends on the source - that is what the option is for. Very large texts are limited by your device memory.
No. Decoding runs entirely locally in your browser; your text never leaves your device and is not stored.
When the data comes from a submitted web form. There a plus sign stands for a space. In plain URLs the plus sign stays a plus sign.
The tool reports an honest error instead of producing a wrong result. A valid percent escape is % followed by exactly two hex digits.
With the URL encode tool: it makes arbitrary text URL-safe. This tool is the way back.