Parsed URL & params
| Part | Value |
|---|
| Key | Decoded value |
|---|
URL Decoder
Debugging a tracking link, a redirect or a form-encoded query string? Paste the full URL (or just the ?key=val part) and get protocol, host, path, hash plus every decoded key → value in a copyable table — or flip between encodeURIComponent and encodeURI output with one click.
Frequently Asked Questions
When do I use encodeURIComponent vs encodeURI?
encodeURIComponent escapes everything except unreserved marks — use it for each query value. encodeURI keeps :/?#[]@!$&'()*+,;= intact — use it on a complete URL.
Why does «+» become a space?
HTML forms encode spaces as + (application/x-www-form-urlencoded). Enable «+ as space» when decoding form submissions or old query strings.
Does the params table handle duplicate keys?
Yes — repeated ?a=1&a=2 keys each get their own row, so nothing is silently overwritten.
Is pasting a URL with tokens safe?
Yes — parsing uses URL/URLSearchParams and every cell is written via textContent, so nothing in the URL can execute script. And no data leaves the page.