We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
JSON and GET Converter
Was this tool helpful to use?
Your feedback helps us make it better
Free online JSON and GET parameter converter. Quickly convert between URL query strings and JSON objects.
Choose how arrays are serialized in GET parameters: brackets, indexed, or repeated keys
Apply percent-encoding to values for safe transmission of special characters
Adds '?' at the beginning of the result, ready to be appended to an API endpoint
Enter content on the left to see real-time conversion results here
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
JSON represents named values and nested structures in a text format. A URL query string expresses parameters as key-value pairs, commonly joined with ampersands, such as page=2&status=open. This converter translates between those two representations so you can inspect or prepare a query string without manually assembling every separator and bracket.
In JSON-to-query mode, nested object keys become bracket paths. For instance, {"filter":{"status":"open"}} becomes filter[status]=open. Scalar values are written as text, so this is a serialization of parameters rather than a type-preserving JSON transport.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
When the input contains an array, choose among bracket notation, indexed keys, and repeated keys. For {"tag":["red","blue"]}, these styles produce forms like tag[]=red&tag[]=blue, tag[0]=red&tag[1]=blue, or tag=red&tag=blue. The format expected by an API depends on its server-side parser; there is no single query-string convention that every service interprets identically.
Nested objects inside arrays may require indexed paths so each value remains addressable. Compare the result with the receiving API’s documentation before using it in a request.
Use cases
See how the tool fits into real work and everyday tasks.
Query strings use URL characters with defined meanings, so spaces and reserved characters may need percent encoding. The encoding switch lets you match the conventions expected by the destination. The separate question-mark option adds a leading ? when you want the output to include the boundary between a URL path and its query portion.
For example, an encoded space may appear as %20. Do not assume that the text shown by every server or browser will look identical: parsers may normalize or decode values as they read them.
Choose JSON to query string, or query string to JSON.
Provide valid JSON for the first direction, or a parameter string for the reverse direction.
For JSON input, choose an array style, whether to encode values, and whether to include ?.
Check key names, nesting, repeated values, and encoding before copying the result into an API example or address.
Q&A
Find concise answers to common questions and confusing cases.
Choose the style documented by the receiving API; bracket, indexed, and repeated keys are conventions, not universal rules.
No. Query values are text, so convert them to the types your application expects.
The server-side parser may interpret brackets, repeated keys, and empty values differently. Check the API’s own parameter documentation.
Notes
Review scope, result limitations, and important precautions before use.
A generated query string is a text representation, not a guarantee that another service will parse it as intended. Verify parameter names, array conventions, encoding, and value types against the destination API before sending a request.
Related
Discover related tools, collections, and available API capabilities.