Abfragezeichenfolgen-Parser

What the Query String Parser does

URLs are easy to read until they fill up with encoded characters and tracking parameters, at which point a single link can become an unreadable wall of percent signs and ampersands. This tool takes any URL or bare query string, splits it into its individual parameters and fragment, decodes each value, and lays everything out in a clean key-and-value table. Reach for it when you need to inspect what a link is actually carrying: debugging an API request, decoding a messy redirect, checking which analytics tags a marketing link is appending to you, or verifying that a callback URL contains the parameters you expect.

How it parses and decodes

A URL's query string is the part after the ?, made up of key=value pairs joined by &, while the fragment is whatever follows the #. This parser first slices off the fragment, then the query, then hands the query to the browser's native URLSearchParams, which is the same engine your browser uses internally. That gives you standards-correct decoding for free:

• Percent-encoding is reversed — %20 becomes a space, %2F becomes /, and multi-byte UTF-8 sequences like %D0%9F are reassembled into the correct characters.
• Plus signs become spaces in the query component, matching how form submissions encode whitespace.
• Repeated keys are preserved, so a link with two id= parameters shows both rows rather than silently dropping one.
• The fragment is decoded separately, because it plays by its own rules.

One detail worth internalising: the fragment after # is never sent to the server by the browser — it stays entirely client-side and is used for in-page anchors or single-page-app routing. That is why single-page apps often stuff state into the fragment, and why a token placed after a # behaves very differently from one placed in the query. Seeing the query and fragment split apart here makes that boundary obvious.

Concrete examples and tips

Paste a typical newsletter link such as https://example.com/article?utm_source=news&utm_campaign=july&gclid=abc123#top and the table immediately separates the real destination from the tracking cruft: utm_source, utm_campaign, a Google gclid, and the harmless #top anchor. That makes it trivial to strip the tracking parameters before you share a link, so you are not passing along identifiers that tie the click back to you. Developers reach for it constantly to eyeball OAuth redirects, signed download URLs and webhook callbacks without hand-decoding by eye — the same kind of debugging you would do against our API. A couple of gotchas: a raw + in a value legitimately decodes to a space, so if you need a literal plus it must be encoded as %2B; and if a link double-encodes a value (%2520), you will see one layer peeled here and may need to run the result through again.

Your privacy here

Everything happens locally in your browser. The URL you paste is parsed by JavaScript on this page and never transmitted — we do not see, log or store the links you inspect. This matters because query strings routinely contain session tokens, email addresses and other sensitive values, and with this tool those never leave your device.