Query String Parser
Parse a URL or query string into a readable table and JSON. Decodes percent-encoding, groups repeated keys into arrays. Copy any value. Free.
About the Query String Parser
This query string parser breaks a URL's parameters into a clear table and equivalent JSON. Paste a full URL, a bare query string, or anything starting with '?', and it decodes every parameter — turning %20 back into spaces and %26 back into ampersands — so you can read the real values at a glance.
It uses the browser's URLSearchParams engine for correct, standards-compliant decoding, and handles the cases people forget: repeated keys (tag=a&tag=b) are grouped into an array in the JSON output, empty values are shown explicitly, and malformed percent-escapes produce a clear error instead of silently corrupting data.
You get a copyable value for each parameter, a total and unique-key count, and a pretty-printed JSON representation ready to drop into code or tests. Everything runs locally in your browser, so URLs containing tokens or session IDs never leave your machine.
How to Use the Query String Parser
- 1Paste a URL or query string into the input box.
- 2Click Parse parameters.
- 3Read the decoded key/value table and the JSON representation.
- 4Copy any individual value or the whole JSON.
Frequently Asked Questions
What input formats does it accept?
A complete URL (https://example.com/search?q=hi&page=2), a query string with a leading ?, or a bare a=1&b=2 string all work. Any fragment after a # is ignored, so you can paste a whole address without cleaning it up first.
How are repeated parameters handled?
When the same key appears more than once — like tag=a&tag=b — the table lists each occurrence, and the JSON output groups them into an array (tag: ["a", "b"]). This matches how servers typically interpret multi-value parameters.
Does it decode percent-encoding?
Yes. Values are URL-decoded, so %20 becomes a space, %40 becomes @, and UTF-8 sequences like %C3%A9 become é. If the string contains a malformed escape (a lone % or %ZZ), the parser reports an error rather than returning corrupted text.
Is the URL I paste kept private?
Yes. Parsing runs entirely in your browser using the native URL APIs, so URLs containing access tokens, session IDs or other sensitive parameters are never sent anywhere.