JSON to Query String
Convert JSON into a URL-encoded query string using the browser's native URLSearchParams. Nested objects are dot-flattened, arrays/objects are JSON-stringified. All values are percent-encoded per RFC 3986.
JSON in, Query String out
See exactly how JSON maps onto Query String — the converter on this page produces output identical to the example below.
{
"page": 1,
"limit": 20,
"filter": "active",
"sort": "name",
"tags": ["dev", "tools"]
}page=1&limit=20&filter=active&sort=name&tags=%5B%22dev%22%2C%22tools%22%5D
What you'll use this for
Converting JSON to Query String is a daily task in API integration, config management, and data pipelines.
API integration
Build GET requests from object-shaped params in your code.
Config migration
Generate shareable URLs from app state stored as JSON.
Data import
Encode filter/search parameters for analytics APIs.
CI pipelines
Generate query-string-encoded webhook URLs in build scripts.
How to convert JSON to Query String
Paste your JSON
Drop it into the left editor. The sample is loaded by default — clear it or click the wand to reload.
Click Convert
Or leave auto-convert on for live updates. Conversion runs entirely in your browser — no upload.
Copy or download
Copy to clipboard or save the output as query.txt.
Reverse if needed
Jump to the Query String to JSON converter for a round-trip check.
Frequently asked questions
Query strings are text-only. All values are stringified before percent-encoding.
Nested objects are dot-flattened (filter.status=active). Arrays and remaining objects become JSON strings.
Yes. No signup, no limits.
You'll see a clear parse error in the output panel.
Use the Query String to JSON converter for the opposite direction.
About JSON and query strings
URL query strings encode parameters after the ? in a URL as key=value pairs joined by &. Defined by RFC 3986, with bracketed/repeated-key conventions varying by framework (Rails, PHP, Express).
Common pitfalls
- No universal way to encode nested objects — different frameworks use different conventions.
- This tool uses dot-flattened keys and JSON-stringifies arrays.
- All special characters are percent-encoded per
URLSearchParams. - Query strings have practical length limits (~2k chars on older clients).