URL Query String Parser

What Is the URL Query String Parser?

This tool parses a URL's query string (the part after ?) into its individual key-value parameters, automatically URL-decoding each value -- useful for quickly inspecting a long tracking or API URL.

How to Use This Tool

Paste a URL or a query string (e.g. ?utm_source=google&utm_medium=cpc). Each parameter and its decoded value appears instantly in a clear list.

What the Output Table Shows

Results appear as a two-column table with a Key column and a Value column, one row per parameter, in the order they appear in the URL. Percent-encoded values are decoded for you, and a plus sign inside a value is shown as a space, following the form-encoding convention used by the browser's own query-string parser. If the same key appears more than once, each occurrence gets its own row rather than being merged, so repeated parameters such as several tag values stay visible. A parameter with no equals sign, like a bare flag, is shown with its name and an empty value.

How the Input Is Split

If your text contains a question mark, everything after the first question mark is treated as the query string. If there is no question mark, the whole text is treated as a query string. A fragment at the end of a full URL, the part after a hash sign, is not stripped separately, so it may end up attached to the last value. Remove the fragment yourself if you paste a link that has one. Leading and trailing spaces around your paste are ignored.

Worked Example

Paste this hypothetical link: https://shop.example.com/search?q=blue%20shoes&size=9&utm_source=newsletter&utm_medium=email&tag=sale&tag=new. The table lists six rows: q with the value blue shoes, size with 9, utm_source with newsletter, utm_medium with email, and two rows for tag, one with sale and one with new. You can immediately see that the tag key is repeated, something that is easy to miss when reading the raw link.

Practical Uses

• Auditing marketing links to confirm the tracking parameters (campaign source, medium and name) are spelled consistently before a campaign goes live.
• Debugging API requests by reading the parameters a client actually sent.
• Understanding redirect and login links that carry long encoded values, such as a return address nested inside another link.
• Finding parameters that should be removed for clean sharing, such as session or click identifiers.
• Checking that special characters survived a trip through an email client or chat app.

Nested and Double-Encoded Values

A value may itself contain another URL, such as a redirect target. The tool decodes one level, so the nested link appears as readable text in the Value column. If it still shows percent codes, it was encoded twice; copy that value and paste it back into the tool, or into a URL decoder, to peel off the next layer. To inspect the inner query string, paste the decoded inner link into the tool again.

Limits and Cautions

• The tool reads only the text you paste. It does not fetch the link or check whether it works.
• Semicolon-separated parameters, sometimes used in older systems, are not split; only the ampersand is treated as a separator.
• Path segments, such as a product id in the address itself, are not parameters and are not listed.
• Links with private tokens, password reset codes or session ids should be handled carefully. Parsing happens in your browser and nothing is sent to a server, but avoid sharing screenshots of sensitive values.

Frequently Asked Questions