Query String Parser
Parse a URL query string into key and value pairs.
How to use Query String Parser
Free query string parser: split a URL or a key equals value string into an editable list of parameters, entirely locally.
Open Query String Parser on toolpermarket and fill in the inputs the tool asks for.
Provide the value or text the tool asks for in the single input field. The field is labelled clearly so you always know what to enter.
Press Parse to compute the result. The output appears immediately below the form. Adjust the inputs and recalculate as many times as you need.
Read the result and use it as needed. If the number looks off, re-check your inputs and run it again — the math is deterministic, so the same entries always return the same answer.
Worked example. Pasting ?utm_source=news&id=42 shows two lines: utm_source = news and id = 42.
Tips for accurate results.
Drop the leading question mark if you pasted the whole URL.
Encoded values such as %20 are decoded for you automatically.
Empty keys or values are labelled (empty) so nothing is hidden.
When to use Query String Parser. Inspecting tracking parameters on a link you were sent. Debugging why a form submitted the wrong fields. Documenting what a shared URL actually carries.
When you actually reach for this
- You need the key/value pairs out of a URL's ?... section to inspect or log what a request actually carried.
- You are debugging why a filter or pagination param is not reaching your backend.
Where this tool stops being accurate
- Repeated keys either collapse to the last value or become a list depending on the convention; this tool shows both forms.
- Values are decoded but not typed — "true"/"123" stay strings and you must cast them in code.
Frequently asked questions
Is my query string uploaded?
No. Parsing happens entirely on your device; the string is never transmitted to a server.
What if a value is URL-encoded?
It is decoded before display, so %2F or %20 show as the real character rather than the escape.
Can it handle many parameters?
Yes. Every &-separated pair becomes its own line, however many there are.
A param appears twice in the URL — which value do I get?
That depends on your server framework; some take the first, some the last, some give an array. This tool surfaces all occurrences so you can decide.
My & in the query broke parsing — why?
That is HTML-entity encoding, not URL encoding. Decode HTML entities first, then parse the raw query string.