How to use it
- Paste the encoded text or URL.
- Leave Encoding on URL and Direction on Decode (preselected here).
- Tick Use + for spaces if the text is form data.
- Copy the result or download decoded.txt.
Worked example
caf%C3%A9%20%26%20cr%C3%A8me%3F decodes to café & crème?. a+b stays a+b, and becomes a b once Use + for spaces is ticked. 100% is reported, because the % at position 4 has no hex digits after it.
Formats and limits
| Input | Percent-encoded text |
|---|---|
| Output | Text |
| Engine | TextEncoder/TextDecoder with strict validation |
Limitations
- Only UTF-8 is decoded; Latin-1 escapes such as %E9 are reported as invalid.
- Decoding is done once; text that was encoded twice (%2520) needs a second pass: paste the result in again.
- In Full URL scope, escapes of reserved characters such as %2F and %3F are kept as escapes.
Questions
Why are + signs not turned into spaces?
In a URL path, + is a plus sign. Tick Use + for spaces when the text comes from a form or a query string that uses + for spaces.
It says an escape is not valid.
Every % must be followed by two hex digits. A literal percent sign has to be written %25; the message gives the position of the broken escape.
It says the bytes are not valid UTF-8.
The text was encoded in an older character set, for example é written as %E9 in Latin-1. Only UTF-8 is decoded here, and the position of the first bad sequence is shown.
Is my text uploaded?
No. The text is processed in your browser and nothing is uploaded.
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
This page opens the Encoding toolkit ready for this task. See the privacy policy for how toolsdocks handles data.