What this parser helps you check
- Decode raw query strings without losing the original repeated-key order.
- See whether the input came from a raw query, a full URL, or a path with query.
- Copy a normalized query string after optional plus-to-space decoding or key sorting.
- Catch malformed escape sequences and suspicious duplicate parameters before release.
Wave 9 dev-data expansion
Inspect and normalize a query string
The share URL stores settings only. It never includes the URL or query string you paste here.
Paste a query string or URL, then parse it.
When to use this page instead of the URL encoder
Use the URL encoder when you need to transform one text value into percent-encoded form or decode a single fragment. Use this parser when the question is about structure: repeated keys, UTM campaigns, multi-value filters, and the exact normalized query that should be kept.
If the next step is validating JSON data carried inside a parameter, continue with JSON formatter. If you need to inspect a full payload or token flow, Base64 tool is often the next page to open.
FAQ
How is this different from the URL encoder?
The URL encoder converts text to percent-encoded form or decodes it. This page is for inspection: it splits an existing query string or full URL into key-value pairs and shows repeated parameters, decoded values, and a normalized output.
Can I paste a full URL instead of only the query part?
Yes. You can paste a full URL, a path with query, or a raw query string. The parser identifies the source type and extracts the query parameters for review.
How are repeated keys handled?
Repeated keys are kept as separate rows in the original order. The summary shows how many duplicates were found so you can check APIs that expect arrays or repeated parameters.
Does the share URL include my query string?
No. The share URL stores only lightweight settings such as whether plus signs decode as spaces and whether keys should be sorted. The input itself stays in your browser.