Developer Tools Runs in your browser Free · no account

Query String Parser

The query string parser splits a query string into its parameters and shows each value percent-decoded, as the receiving server would read it. It accepts a whole URL or a bare parameter string, and flags any parameter that appears more than once.

Options
Query string or URL 0 characters
Parameters

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the Query String Parser

  1. Paste a full URL or just the query string — a leading question mark is optional.
  2. Read the decoded values in the table.
  3. Turn on sorting to compare two long tracking URLs side by side.

Example

Input
?q=hello%20world&page=2
Output
q     | hello world
page  | 2

Common use cases

  • Reading a long analytics or advertising URL to see what is actually being tracked.
  • Debugging why a search or filter parameter is not reaching your application.
  • Checking how a space or accented character was encoded by a client.
  • Spotting a parameter that has been accidentally repeated.

Limitations and things to watch for

  • Values are shown decoded. A value that was double-encoded will still look encoded after one pass — run it through again to see the original.
  • Repeated parameters are all listed, because servers genuinely disagree about which one wins. PHP keeps the last, some frameworks collect them into an array, and others take the first.
  • A plus sign is decoded as a space, matching how form submissions are encoded. In a path segment a plus is a literal plus, so do not paste a path here.

Frequently asked questions

What happens with a repeated parameter?
Every occurrence is listed and the tool flags the duplication. That matters because there is no single standard for which one wins: PHP keeps the last, Rails collects them into an array, and some servers take the first.
Why did %20 become a space?
Because that is what it means. The table shows values as the receiving application would read them after percent-decoding, which is usually what you want when debugging.
Can I paste a whole URL?
Yes. The query string is extracted from it automatically. A bare parameter string, with or without a leading question mark, also works.
Is my URL sent anywhere?
No. Parsing happens in your browser, which matters because query strings routinely carry session identifiers, tokens and search terms.

Share this tool