URL-decode mangled logs into something readable
Paste `%7B%22a%22%3A1%7D`-style junk; get the original characters.
chars: 30
When to use
Reading access logs, debugging redirects, or reversing encode.
Examples
How it works
decodeURIComponent with try/catch for malformed % sequences; optional + → space.
Common pitfalls
- Lone % or bad hex throws.
- Decoding twice can corrupt data.
- + only means space in form bodies.
How this differs
Opposite of URL Encode. Query String Parser handles full ?a=1&b=2 strings.
FAQ
Double-encoded strings?
Decode twice carefully; show intermediate.
Invalid `%`?
Error instead of silent garbage.
Related to HTML entities?
Different — use HTML Decode.
Reverse?
URL Encode.
Related tools
Runs in your browser. Nothing is uploaded. Not a security product —hashes and JWT decode are for debugging, not password storage or auth advice.