Skip to content

Query String Parser

Parse, decode, normalize, and convert URL query parameters to JSON.

Query Input
Decoded Parameters
KeyValueRaw
qweb utilsq=web%20utils
utm_sourcenewsletterutm_source=newsletter
utm_mediumemailutm_medium=email
page2page=2
tagjsontag=json
tagxmltag=xml
JSON Output
Normalized Query String

Query String Parser

Parse URL query strings into decoded keys and values, then copy the data as JSON or a normalized query string.

Useful for

  • Debugging encoded API parameters
  • Inspecting marketing and UTM links
  • Converting repeated query parameters into JSON arrays

How to use Query String Parser

The query string parser turns URL parameters into decoded key-value data. It helps when a link has many campaign, filter, or redirect parameters.

Developers often use this page when they need query string parser, parse query string, query string to json, and url query parser.

Privacy and data handling

This tool can handle security-sensitive text, so it is meant for local inspection and test data.

  • Normal use does not require uploading your input to a server.
  • Use redacted tokens, passwords, secrets, headers, and connection strings when possible.
  • Copy buttons use your browser clipboard permission, so clear the clipboard after handling secrets.

Examples

Parse query parameters

Input

utm_source=newsletter&page=2

Output

{
  "utm_source": "newsletter",
  "page": "2"
}

Decoded query data is easier to inspect than a long URL string.

Steps

  1. 1Paste a full query string or URL.
  2. 2Review decoded keys and values.
  3. 3Copy the parsed data as JSON if needed.

Common use cases

  • Inspect campaign parameters.
  • Debug redirect URLs.
  • Turn query strings into JSON for tests.

Practical tips

  • Repeated keys may become arrays.
  • Nested query formats depend on the parser used by your backend.
  • Remove private tokens before sharing parsed output.

FAQ

What is a query string?

It is the part of a URL after the question mark. It usually stores parameters as key-value pairs.

Why do query values contain percent signs?

They are URL encoded. Decoding turns percent-encoded values back into readable text.

Related Developer Tools