Free tools that run in your browser. Use any tool without an account.

Favourites Cart
Sign in
Join free

Query String Parser

  • Free
  • Runs in your browser
  • No account needed

Paste a URL or query; the tool extracts the search part after ? and returns decoded key/value rows or JSON. For example, ?a=1&b=2 yields two decoded pairs ready to copy with one click.

Query String Parser runs in your browser. Your text is never uploaded or stored.

Runs in your browser. Your files and values are not sent to us. Report a problem
Advertisement

About Query String Parser

You paste a full URL or the query part after the question mark. The tool shows decoded name/value pairs and can convert them to a table or JSON. You can also paste JSON and convert it back to a query string. The parser runs in your browser using the browser URL rules from WHATWG and the URLSearchParams API, so nothing you type is uploaded to a server. Developers and QA engineers use it to inspect UTM tags, debug broken links, verify API query parameters, or prepare test requests. The interface gives three options: To table, To JSON, and JSON to query string. One click copies the output to your clipboard. The tool shows repeats in source order and decodes + as space per the form-encoding rules. It does not emulate framework-specific parsing such as PHP parse_str. See the WHATWG URL Standard, RFC 3986, and MDN for details.

How to use it

  1. 1Paste a full URL or a query string into the input box
  2. 2Choose To table, To JSON, or JSON to query string
  3. 3Click Parse or Convert to run the parser in your browser
  4. 4Click Copy to send the result to your clipboard
Advertisement

Worked example

Input: https://shop.example/cart?id=123&qty=4&note=one+item Option: To JSON Exact output copied: {"id":"123","qty":"4","note":"one item"}

How it works

Text tool that runs in the browserOptions: To table, To JSON, JSON to query stringOne click copies the outputNothing typed is uploaded

Source: WHATWG URL StandardRFC 3986, URI Generic SyntaxMDN Web Docs - URLSearchParams. Last checked 5 November 2026.

What it is good for

  • Runs entirely in your browser so input is not uploaded
  • Shows decoded, ready-to-copy output with a single click
  • Handles parse and build workflows: table, JSON, or JSON to query string
  • Does not emulate server-side frameworks; backend handling can differ from browser parsing
  • Does not guess legacy character encodings; use UTF-8 input for consistent decoding
Advertisement

Questions people ask

Will the tool show raw and decoded values?

The tool shows decoded values by default to make reading easier. It also preserves the raw percent-encoded text so you can compare both forms for debugging.

Does a plus sign become a space?

Yes. In browser and form-style parsing, a plus sign decodes to a space. Use %2B if you need a literal plus sign.

How does it handle repeated keys like tag=a&tag=b?

The tool lists each occurrence in source order so you see every value. Server frameworks differ: many collect repeats into arrays, while some languages overwrite the first value.

Will the fragment after # be parsed or sent to a server?

No. The fragment is client-side only and is not sent in HTTP requests. The parser ignores the part after # when building query pairs.

Is it safe to paste sensitive URLs here?

The parser runs in your browser and does not upload input to our servers. Still, sending personal data to third-party systems can have legal implications; consult local data protection guidance for the EU, UK, Nigeria, or Gulf states.

Which character encoding is used for decoding?

Modern browsers use UTF-8 for encoding and decoding query strings. Legacy servers may expect other encodings, so use UTF-8 for consistent cross-platform results.

Help keep every tool free

FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.

Advertisement
Advertisement