JSON to Query Parameters Converter

Convert JSON objects into URL query strings with configurable array formats, nested key notation, and optional base URL.

How to Use

  1. Paste a JSON object in the input panel.
  2. Choose array format, nesting style, and encoding options.
  3. Optionally enter a base URL to generate a complete link.
  4. Copy the query string, full URL, or download as a .txt file.

Why Convert JSON to Query Parameters?

Many APIs accept data through URL query parameters for GET requests. Converting a JSON payload into a query string lets you quickly build API calls, test endpoints in a browser address bar, or construct cURL commands for debugging.

Different frameworks expect different array and nesting conventions. Rails uses bracket notation, Express.js often uses repeated keys, and some APIs expect comma-separated values. This tool supports all common formats so you can match your target API.

Features

  • Four array serialization formats: brackets, indices, comma, repeat
  • Nested object flattening with dot or bracket notation
  • Optional base URL for complete link generation
  • Configurable URL encoding (values only, keys+values, or none)
  • Null value handling: omit, empty, or literal
  • Alphabetical parameter sorting
  • Parameter breakdown table showing all key-value pairs
  • One-click copy for query string or full URL
  • 100% browser-based — no data uploaded

Frequently Asked Questions

How are nested JSON objects converted to query parameters?

Nested objects are flattened using either dot notation (user.name=John) or bracket notation (user[name]=John). You can choose which format to use in the options.

What array formats are supported?

Four formats: Brackets (items[]=1&items[]=2), Indices (items[0]=1&items[1]=2), Comma-separated (items=1,2), and Repeat (items=1&items=2). Choose the one your API expects.

Can I add a base URL to get a complete link?

Yes. Enter a base URL in the options bar and the tool will combine it with the generated query string to produce a complete, ready-to-use URL.

How is URL encoding handled?

By default, only values are encoded. You can switch to encode both keys and values, or disable encoding entirely for raw output. Encoding follows standard percent-encoding (RFC 3986).

What happens to null values?

You can choose to omit null keys entirely, include them with an empty value, or include them as the literal string "null".

Is my data sent to a server?

No. All conversion happens in your browser. Your JSON data never leaves your machine.