QueryString Parser
NewParse and edit URL query strings with key-value table view.
| Key | Value | Action |
|---|
Exports
Frequently Asked Questions
Does this preserve repeated keys like tag=dev&tag=tools?
Yes. Repeated keys stay as separate rows in the editor, and the JSON/object exports collapse them into arrays when the same key appears more than once.
What does it do with keys like foo[] or items[2]?
Those are recognized when building the structured export. foo[] pushes onto an array, and items[2] assigns a value into a numeric array index.
Why does the reconstructed query always start with a question mark?
Because buildQuery() always prefixes the joined parameter string with ?. Even an empty table reconstructs to just ? rather than an empty string.
Why are spaces encoded as + in the output?
This tool encodes keys and values with encodeURIComponent and then swaps %20 for +, which matches common form-style query-string encoding.
What export formats does it support?
You can export the parsed params as plain JSON, as a JavaScript object literal assignment, or as URLSearchParams append() code you can paste into an app.