URL Decoder
URL Decoder
Decode percent-encoded URL text with per-line and recursive decode options.
InputsManual input67 charsAuto run
File input
Choose a file
Click, drop, or paste from clipboard.
Options
4
More actions
Manual
ManualDecoded output
0
No output yet.
Live
Manual
Ready
67
Input
0
Output
0
ms
Flow
- Choose decode mode for whole URL strings or URL components.
- Optionally decode each line independently.
- Use recursive mode to unwrap multiple encoding layers safely.
Example
Worked example: decode a search URL
- 1 Input = https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Djson%2520tools
- 2 First decode pass returns q=json%20tools.
- 3 Recursive decode converts q to json tools.
Final decoded URL is https://example.com/search?q=json tools.
How
- Paste encoded input into the first textarea.
- Pick decodeURIComponent or decodeURI mode in the options panel.
- Review output, then copy or swap values if you need to re-run another pass.
Cases
- Debug encoded query parameters from browser URLs.
- Decode webhook payload fragments copied from logs.
- Inspect double-encoded text from third-party integrations.
Avoid
- Using decodeURI for a standalone query value that needs decodeURIComponent.
- Forgetting to enable plus-as-space when input uses + for spaces.
- Decoding repeatedly without checking whether additional passes are necessary.
Table
| Conversion | Result |
|---|---|
| %20 | space |
| %2F | / |
| %3F | ? |
| %26 | & |
| %3D | = |
FAQ
What is the difference between decodeURI and decodeURIComponent?
decodeURI is for full URL strings while decodeURIComponent is for individual URL parts like query values.
Can this decode each line separately?
Yes, turn on the per-line option to decode multiline payloads safely.
Does this tool show malformed encoding errors?
Yes, invalid percent-encoding is reported in the error panel with line context.
Switch
Switch12
No match.