Convert a JSON object into a URL query string — percent-encoded, with nested keys in bracket (PHP/Rails) or dot style, and null handling you control.
Show calculation steps
Processed privately in your browser — nothing you paste is uploaded, logged or stored.
Query strings without hand-encoding
Building a query string by hand means percent-encoding, bracket conventions and array indexes — all easy to get subtly wrong. Paste a JSON object and get the encoded string: nested keys in bracket style (filters[open_now]=true, the convention PHP and Rails parse natively) or dot style, arrays indexed, spaces and unicode percent-encoded, nulls skipped or kept empty as you choose.
Worked example
{ "search": "coffee shop", "page": 2,
"filters": { "open_now": true }, "tags": ["wifi", "quiet"] }becomes:
search=coffee%20shop&page=2&filters[open_now]=true&tags[0]=wifi&tags[1]=quietWhen to use it
- Constructing API GET requests with structured filter objects.
- Building shareable URLs that encode a UI state.
- Debugging how a server will see a parameter set.
Limitations to know
- There is no official standard for nested keys in URLs — bracket and dot are the two dominant conventions; match what your server parses.
- Some APIs want unindexed arrays (tags[]=wifi&tags[]=quiet) or repeated keys; a quick find-replace on the output covers those variants.
- Privacy is structural: URLs land in server logs, browser history and Referer headers — never put passwords, tokens or personal data in query parameters. The tool repeats this warning on every run.
Common errors and fixes
- Server ignores my nested params — it probably expects the other style; switch brackets/dots.
- URL too long — practical URL limits hover around 2,000 characters; the stats line shows yours, and big payloads belong in a POST body.
How to use the JSON to URL Parameters Converter
- Paste a JSON object — its keys and values become the parameters.
- Pick bracket style (PHP/Rails) or dot style for nested keys.
- Click "Build query string".
- Append the result after a ? in your URL.
Frequently asked questions
How is nested JSON encoded in a query string?
There is no official standard, so the tool offers the two dominant conventions: brackets — filters[open_now]=true, tags[0]=wifi — which PHP and Rails parse into nested structures automatically, and dots — filters.open_now=true — which some APIs prefer. Match your server.
What gets percent-encoded?
Everything that needs it — spaces, unicode, symbols — per standard URL encoding, while brackets are kept readable since servers accept them literally. The result is safe to paste into a URL.
How are arrays represented?
Indexed brackets by default: tags[0]=wifi&tags[1]=quiet. PHP-style unindexed tags[] and repeated plain keys are other conventions in the wild — if your API expects those, a quick find-replace on the output gets you there.
Is data in URLs private?
No — query strings land in server logs, browser history, analytics and Referer headers. The tool reminds you on every run: never put passwords, tokens or personal data in a URL; send sensitive data in a request body instead.
