JSON → query
Nested structures are flattened into a[b]=c or similar keys. Arrays get indexes too, so you can match backend binding.
Non-ASCII text and spaces are URL-encoded.
JSON to GET parameters
Processed locally You can also load data via #data={"name":"Ada"} or #url=... It is cleared from the address bar after it is read.
How to use
Convert between objects and URL query strings. Build GET requests or restore address-bar parameters to JSON without counting & and encodings by hand. Nested objects are flattened into bracketed keys where possible.
query → JSON
Turn page=1&q=json Restore to an object. Copy the query from the address bar or a capture.
Duplicate keys follow this page’s parser. Spot-check complex repeated parameters.
Done locally
Full URLs are not sent to us. You can debug intranet API parameters here too.
POST bodies that are already JSON do not need this page—just format them.
Example
{"page":1,"q":"json","tags":["a","b"]}page=1&q=json&tags=a&tags=bWhat about spaces and non-ASCII text?
They follow URL-encoding rules. Before pasting back into the address bar, confirm the server decodes the same way.
Do I still need this for POST JSON?
If the body is JSON, use the formatter. This page is for the query string.
PHP / Rails-style bracket keys?
They are expanded into nested objects where possible. If your framework differs, tweak against its docs.
What about parameters after the hash (#)?
This page handles the query after ? . If a single-page app puts state in the hash, copy only the query part.
Recommended workflow
- Choose JSON → GET or GET → JSON.
- Paste an object or query string and inspect the result.
- Append the query to an API URL for a test request, or paste JSON back into tests.
- For encoding mismatches and garbled text, compare against the server’s
decodeURIComponent/ framework binding.
GET has length limits. If there are many parameters or a large JSON blob, use a POST body instead of stuffing everything into the query.