Query String Parser
Parse URL query parameters into readable key-value pairs, including repeated parameters and encoded values.
Query input
Parameters
| Key | Value |
|---|---|
| No parameters yet. | |
Inspect query parameters
Paste either a full URL or only the part after the question mark. Repeated parameters are preserved as separate rows so nothing is silently lost.
Related tools
Use the URL Parser for the rest of the URL components or the URL Encoder & Decoder for percent-encoded values.
Browser-local
Parsing happens in your browser and no query values are uploaded.
How to use this tool effectively
Parse the query portion of a URL into readable key-value rows while preserving repeated parameters. This helps with campaign links, API requests, filters and browser routing.
Common uses
- Inspect UTM campaign parameters in a marketing URL.
- Debug repeated parameters such as tag=dev&tag=web.
- Separate a long query string into values you can review individually.
- Copy parsed parameters as structured JSON for troubleshooting.
Example: repeated query keys
?tag=dev&tag=web&page=2
tag = dev tag = web page = 2
Repeated keys are preserved because many frameworks intentionally allow a parameter to appear more than once.
Common mistakes to avoid
- Do not assume every repeated parameter should be collapsed into a single value.
- Encoded characters should be decoded according to URL/query-string rules before interpreting the text.
- A fragment after # is not part of the query string even if it contains question marks or ampersands.
Parsing happens locally. KRIYANO does not visit the URL or store the parameters you paste.
Frequently asked questions
Can I paste a full URL instead of only the query string?
Yes. The tool can extract the query portion from a full URL and then display the parameters.
Why are repeated keys kept?
Repeated query keys are valid and are commonly used for filters, tags and multi-select inputs. Preserving them avoids silently changing the request meaning.
Are UTM parameters special?
They are ordinary query parameters with conventional names such as utm_source and utm_campaign. The parser treats them like any other key-value pair.