Paste a full URL or just the part after the ?. The parser lists every parameter with its decoded value next to the raw one, flags keys that appear more than once, and exports the result as JSON or as a one-parameter-per-line view that makes long tracking URLs readable. It runs in your browser.
How the parser reads a query string
It splits the query on &, then each pair on the first =, so a value may itself contain =. Keys and values are decoded the way URLSearchParams and most servers do it: percent-escapes are decoded and + becomes a space. Everything after # is the fragment, which browsers never send to the server, so it is shown separately.
| Input | Key | Value |
|---|---|---|
| ?q=hello+world | q | hello world |
| ?redirect=https%3A%2F%2Fexample.com | redirect | https://example.com |
| ?debug | debug | (no value) |
| ?filter= | filter | (empty) |
| ?eq=a=b | eq | a=b |
Repeated keys
A key can appear several times, as in ?color=blue&color=black. The table keeps every occurrence in order, and the JSON view turns them into an array. Servers differ here: some keep only the first or last value, and some (PHP, for example) only build an array when the key ends in []. See array parameters for the conventions per framework.
Changing the parameters
The parser only reads. To change, add or remove parameters and copy the rebuilt URL, use "Edit these parameters", which opens the URL in URL Editor with one row per parameter.