URL query string → JSON

Client

Paste a query string from a link or server log—get a JSON object with coerced booleans and numbers when the value is unambiguous.

Learn more: query strings to JSON

Parse URL-encoded key=value pairs into a flat JSON object—duplicate keys keep the last value per URLSearchParams rules.

Coercion

The strings true and false become booleans; numeric-looking values become numbers; empty values map to null. Everything else stays a string.

Query string → JSON

?

Parses application/x-www-form-urlencoded text; strips a leading ? or # if present. Numbers and booleans are inferred when unambiguous.

Common use cases

  • Turn pasted query strings from browser address bars or server logs into editable JSON.
  • Inspect repeated parameters and encoding after copying a failing request from DevTools.
  • Compare decoded objects with the encode tool to catch typos in parameter names.

Common mistakes to avoid

  • Trusting automatic boolean or number coercion

    Ambiguous strings may stay as strings. Confirm types match what your backend validates.

  • Pasting the full URL instead of the query component

    Strip the scheme, host, and path when the parser expects only the part after ?.

FAQ

Is decoding done on your servers?

No. Parsing runs locally in your browser.

Does this handle multipart or JSON bodies?

It targets application/x-www-form-urlencoded query strings. Other content types need different parsers.

More tools

Related utilities you can open in another tab—mostly client-side.