Parse query strings without reinventing split("&") bugs
Paste a query (with or without `?`); see keys/values. Build mode: edit table → encoded string. Uses component encoding rules.
chars: 38
When to use
Debugging redirects, documenting API examples, or fixing duplicate keys in a query.
Examples
How it works
URLSearchParams-style parse (note duplicate key behavior). Shows decoded pairs.
Common pitfalls
- Duplicate keys may become arrays or last-wins depending on UI.
- Leading ? is optional.
- Hash fragments (#...) are not query params.
How this differs
Parses a whole query. URL Encode/Decode work on individual values.
FAQ
How are duplicate keys handled?
Per `URLSearchParams` (arrays / last-wins — document UI choice).
Hash fragments?
Strip `#...` or ignore — say which.
Related to URL encode?
Encoder for single values; this page for whole maps.
Uploaded?
No.
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.