Web & URLs
Query parameters to JSON
Turn `?foo=bar&baz=1` style strings into a JSON object for code and debugging.
When you copy a URL’s query section from the address bar or network panel, turning it into JSON makes it easier to diff, log, and manipulate in JavaScript. Repeated keys become arrays so you do not lose multi-value fields like `tag=a&tag=b`.
Similar tools
Quick links to related utilities—same workflow, different input or output.
- Web & URLsURL encode / decodePercent-encode text for query strings or decode encoded values back to plain text.Open
- Web & URLsHAR file viewerInspect HAR captures with timings, sizes, MIME types, and per-request headers.Open
- Data formatsJSON formatterPretty-print or minify JSON for debugging, reviews, and smaller payloads.Open
FAQs
Should I include the leading ?›
Either works—the parser strips a leading `?` if present.
How are duplicate keys handled?›
If a name appears multiple times, values are collected in order—often as an array—so nothing is silently overwritten.
Are values always strings?›
Query strings are text; numbers and booleans stay as strings unless you coerce them in code.
Can I go from JSON back to a query string?›
Use your language’s URLSearchParams or a small script; pairing with JSON.stringify of the object is common.
General
Do these tools send my data to Exemplar’s servers?›
By default, conversion and formatting run entirely in your browser. Nothing is uploaded to Exemplar for normal paste-and-transform workflows. Tools that deliberately open an external service (for example, a third-party speed test) are called out on the page.
Do I need an account or install anything?›
No account is required. Everything runs in the browser—there is nothing to install for these utilities. They complement the Exemplar platform but work standalone.
Are these utilities open-source or the same as other sites?›
These pages are built for Exemplar’s audience (developers working with APIs, config, and ops data). Behavior may differ slightly from other online tools; always verify critical output in your own environment.
Are there size or performance limits?›
Very large inputs can slow down or crash the tab—especially for images, huge JSON, or multi‑MB HAR files. For production-scale data, prefer local CLI tools, streaming parsers, or your own pipelines.
Can I use output in production?›
Yes, when you have validated it. Parsers and formatters here aim to be helpful for everyday tasks but are not a substitute for tests, schema validation, or security review where it matters.
Where can I read more about privacy?›
See our Privacy policy at /privacy for how exemplar.dev handles site analytics and general data practices.