Network and HTTP

Query String Parser

Convert query strings into readable JSON for UTM, OAuth, filters, redirects, and deep-link debugging.

Security notice

Query strings can contain tokens, authorization codes, or state values. Mask sensitive values before sharing.

Paste your dataJSON, JWT, URL, Base64 or CSV

Input

Paste or type

Try an example:

Output

Run an action

Paste your data. Zippy detects the context and shows compatible actions.

Processed locallyNo upload · no account · your data stays in this browser

Quick examples

Debug OAuth parameters

Input: ?code=abc&state=xyz&redirect_uri=https%3A%2F%2Fapp.com

Output: { "count": 3, "params": [ { "key": "code", "value": "abc" }, { "key": "state", "value": "xyz" }, { "key": "redirect_uri", "value": "https://app.com" } ], "grouped": { "code": [ "abc" ], "state": [ "xyz" ], "redirect_uri": [ "https://app.com" ] } }

Query String Parser FAQ

Can I paste a full URL?

Yes. The tool extracts everything after ? and ignores the fragment after # while parsing parameters.

Does it show repeated parameters?

Yes. Output includes an ordered list and a grouped object to reveal repeated keys.

Does it work for UTM parameters?

Yes. Use it to review utm_source, utm_medium, utm_campaign, and other tracking parameters.

What happens to encoded values?

URLSearchParams decodes common percent-encoded values, such as spaces and nested URLs.

Is the query string sent to a server?

No. Parsing runs locally in your browser.