Everything runs in your browser, so private links, API callbacks, campaign URLs, and temporary tokens are not uploaded. The parser uses the browser's standard URL and URLSearchParams APIs, then adds an editable table on top so you can inspect and rebuild parameters without losing repeated keys.
Query string parser
Draait volledig in je browser - niets uploaden, geen account.
Query string parser
0Paren
0Sleutels
0Dubbele
0Lege waarden
Editable parameters
Paste a query string or add a row to start rebuilding parameters.
Rebuilt query
-With leading ?
-Percent-encoded text is decoded in the table, then encoded again in the rebuilt output.
Paste a URL or query string to parse its parameters
What is Query string parser?
Query string parser turns the part of a URL after the question mark into readable Sleutel/Waarde rows. Paste a raw query string of a full URL to decode percent-encoded text, keep duplicate keys in order, edit parameters, and rebuild a clean query string or updated URL.
Zo werkt het
- 1Paste a URL or query string. Use a full URL like <code>https://example.com/?a=1</code>, a raw query like <code>a=1&b=2</code>, or a query with a leading question mark.
- 2Review decoded rows. The table shows each key and value after percent decoding. Duplicate keys stay as separate rows in their original order.
- 3Edit, add, remove, or sort. Change keys and values directly, add missing parameters, remove noisy rows, or sort the list by key when you want a stable output.
- 4Copy the rebuilt output. Copy the encoded query string, the version with a leading question mark, the updated full URL, or a JSON array of key/value pairs.
Voor wie
- Developers debugging callbacks can paste OAuth, webhook, or redirect URLs and inspect every decoded parameter row.
- Marketers checking campaign links can read
utm_*values, spot blanks, and rebuild a clean tracking URL. - QA teams reproducing bugs can edit one parameter at a time and copy the updated query string into a test case.
- Support teams handling shared links can see duplicate keys and blank values that are easy to miss in a long URL.
Veelgestelde vragen
Is this query string parser free?
Yes. It is free to use with no sign-up, no download, and no usage limit. Paste a query string or URL and the decoded rows appear immediately in your browser.
Is my URL or query string uploaded?
No. Parsing, editing, and rebuilding all happen locally in your browser. That is useful when a URL contains access tokens, email addresses, campaign IDs, or other values you do not want to send to another server.
Can it parse a full URL?
Yes. Paste a full URL and the tool reads only the URL's search parameters, preserves the path and fragment, and gives you a rebuilt full URL after edits. You can also paste a raw query string with or without the leading question mark.
Does it keep duplicate keys?
Yes. Duplicate keys are preserved as separate rows in the order they appear. The duplicate summary calls them out so you can see cases like <code>tag=shoes&tag=summer</code> without accidentally merging them.
How are blank values handled?
Blank values stay blank. A parameter such as <code>empty=</code> appears with an empty value, and a key without an equals sign is treated the same way by <code>URLSearchParams</code> when it is rebuilt.
Are percent-encoded values decoded?
Yes. Values like <code>blue%20shoes</code> show as <code>blue shoes</code> in the table. When you copy the rebuilt query, the tool encodes values again using browser-standard form-url-encoded rules.
What happens to the part after #?
In a full URL, the fragment after <code>#</code> is preserved when the rebuilt URL is copied. In a raw query string, anything after <code>#</code> is ignored because fragments are not part of the query parameters.