About online JSON and GET parameter conversion
hidevtool converts between flat JSON objects and GET query strings—the name=value pairs after ? in a URL or in API documentation.
Paste either format and click Convert; direction is detected automatically. Useful for building requests, checking links, and turning log lines into structured JSON.
Online JSON & GET query swap capabilities
Auto direction
Input starting with { is treated as JSON and becomes a query string. Lines with = and &, or a full URL with ?, become formatted JSON. A short hint under the buttons confirms which way it went.
JSON → query string
- Flat objects only—one level of keys, scalar values (string, number, boolean).
- Output looks like name=hidevtool&page=1 with URL encoding when needed.
- Arrays become repeated keys, matching many HTTP clients and server frameworks.
Query → JSON
- Paste raw query text or an entire URL; ?…# is extracted automatically.
- Duplicate keys become JSON arrays.
- Numeric and boolean-looking values are parsed when unambiguous.
Limits
- Nested JSON objects are not supported—flatten first.
- Very large pastes run in the browser; split huge logs if the tab slows down.
Common use cases
Front-end requests
Turn a JSON params object into the query segment for fetch or axios.
Debug & docs
Paste a copied browser URL and get readable JSON for tickets or README examples.
Log triage
Convert query fragments from access logs into objects for diffing or scripts.
Frequently asked questions
- How do I convert JSON to a URL query string?
- Paste a flat JSON object into the input box and click Convert. If the text starts with {, the tool outputs a GET parameter string such as key=value&key2=value2 ready to append after ? or &.
- How do I turn URL GET parameters into JSON?
- Paste the query portion (for example status=ok&page=2) or an entire URL. The tool builds formatted JSON—click the output area to copy.
- How do I extract query parameters from a URL as JSON?
- Paste the query string after ? or the full URL and click Convert. Path and hash are ignored; each key=value pair becomes a JSON field.
- Why does nested JSON fail?
- GET query strings are naturally flat. Only a single-level JSON object is supported. Flatten nested data before converting.
- What happens when the same key appears twice in the query?
- Repeated keys become a JSON array for that name, which matches how many servers accept multi-value GET parameters.
- Is my input uploaded?
- No. Parsing and conversion run entirely in your browser.