Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for URL decoding
Decode iteratively if data was encoded more than once.
+ may mean space in form encodings — know your context.
Invalid percent sequences should be treated as errors.
Decoded output may include reserved characters — re-encode when embedding.
Do not execute decoded strings as code or URLs blindly.
Turn percent-encoding back into text
Processing stays in your browser — your input is not uploaded to our servers.
URLs encode spaces as `%20` (or `+` in query strings) and non-ASCII as UTF-8 percent sequences. This decoder reverses that so query params are readable.
Decode once. Double-decoding can turn a safe string into unexpected characters.
Decode a URL component
Paste the encoded string
A full URL or a single query value both work; know which you have.
Decode
Check that `%` sequences were valid hex. Broken encoding throws rather than guessing.
Copy the readable value
Do not put decoded credentials back into a public ticket.
URL decode FAQ
Plus vs %20?
In `application/x-www-form-urlencoded`, `+` is a space. In path segments, `+` is a plus. Use the variant that matches the source.
Is this opening the URL?
No. It only transforms text. No HTTP request is made.
Local?
Yes.