URL Decoder
Decode a percent-escaped URL or value back into readable text. Long links are automatically broken down into their query parameters.
Component escapes every reserved character — use it for a single query value. Whole URL keeps :/?#&= intact so the link stays usable.
Form encoding (application/x-www-form-urlencoded) writes spaces as + instead of %20.
0 chars · 0 bytes · 0 lines
Result
0 chars · 0 bytes · 0 lines
About URL decoding
Decoding reverses percent-encoding: every %XX sequence becomes its original byte, and the resulting byte stream is read as UTF-8 text. You run into escaped URLs in server logs, redirect chains, analytics exports and tracking links, where decoding is the only way to see what a link actually contains.
Paste a full link and this tool also lists every query parameter with its decoded value, which is the fastest way to inspect long tracking URLs. If the text came from an HTML form, spaces may appear as + — enable the option to convert them back.
What this tool handles
Both encoding scopes
Switch between encodeURIComponent for single values and encodeURI for a complete link, instead of guessing which one a tool used.
Query parameters unpacked
Paste a long tracking link and every parameter is listed with its decoded value, so you can see exactly what is being carried.
Form encoding aware
Optional + as space handling matches how HTML forms and many backends encode data, in both directions.
Frequently asked questions
Why does decoding fail?
A percent sign must be followed by exactly two hex digits. A bare % or a truncated sequence like %E4%B8 stops decoding, and the error message points at the problem.
Why do I get + instead of spaces?
Form-encoded data writes spaces as + instead of %20. Turn on the "+ as space" option when decoding query strings produced by HTML forms or older backends.
The result is still garbled — what now?
The text was probably encoded twice. Decode the output once more. If it stays garbled, the original bytes were not UTF-8.
Are the links I paste stored anywhere?
No. Decoding and parameter parsing run entirely in your browser; nothing is sent to a server.