Query String to JSON
Paste a full URL or just the query part and get structured JSON. Percent-escapes and +-as-space are decoded, bracket and dot nesting is rebuilt, repeated keys collect into arrays, and numbers and booleans are recognised.
How to convert a query string to JSON
- Paste a whole URL, a
?…fragment, or a barea=1&b=2string — all three work. - Any
#fragmentis discarded, since it never reaches the server. - Leave nesting on to rebuild
tags[0]anda.binto real structures, or tick Keep flat keys to see exactly what was sent. - Tick Split comma-separated values if your API uses the comma-joined array convention.
- Copy or download the JSON.
How ambiguity is resolved
- Repeated keys —
t=x&t=ybecomes an array. A key that appears once stays a scalar, which is the behaviour of most server-side parsers. - Numeric bracket keys —
a[0]creates an array; a non-numeric key creates an object. - Keys with no value —
?flagbecomes an empty string, nottrue, matching how servers report it. - Malformed escapes — a stray
%that is not valid percent-encoding is kept literally rather than throwing.
Privacy
Nothing is uploaded. The conversion runs in this tab using your own browser's JavaScript engine — no server sees your data, and the page keeps working with the network disconnected.
FAQ
My URL contains a token. Is that safe to paste?
The parsing runs in your browser and the URL is never transmitted. Still, treat tokens carefully and clear the pane afterwards — and remember that a token in a URL is already exposed to browser history and server logs wherever it came from.
Why did my zip code become a number?
Type inference. A value with leading zeros stays a string, but a plain numeric value becomes a number. Switch Value types to strings to keep everything verbatim.
Can I rebuild the query string?
Yes — JSON → query string. For URL surgery beyond parameters, see urltoolskit.org.