Skip to content
Allin
Sign up · Sign in

JSON to query string

Turn a flat JSON object into a URL query string.

Related tools

All JSON, XML & formats tools →
Query string to JSONParse a URL query string into JSON and build one back. Repeated keys become an array, tag[]= and filtre[prix]= expand into arrays and objects, + is a space and %C3%A9 is é.Query String BuilderBuild a URL query string from key/value rows with correct percent-encoding, array syntax options and a UTM preset — or parse an existing URL back into rows.JSON String Escape / UnescapeTurn raw text into a JSON-safe string and back, with control characters, \uXXXX, emoji surrogate pairs and lone surrogates handled exactly like JSON.stringify.CSV to JSON converterParse CSV text (with header row) into a JSON array of objects, handling quoted fields. Drop a file in rather than pasting it — it is read in your browser and never uploaded.JSON comment removerStrip // and /* */ comments from JSONC to make it valid JSON. Drop a file in rather than pasting it — it is read in your browser and never uploaded.JSON flattenerFlatten a nested JSON object into one level of path keys — and put it back together again. Arrays are indexed as user.roles[0] or user.roles.0, values keep their type, and an empty object stays visible as {}. Takes a whole file, so a long log does not have to go through the clipboard.JSON formatterFormat, beautify or minify JSON — with instant validation.JSON keys extractorList all the keys of a JSON object as dot-notation paths. Works on a pasted block or on a file you drop in.

JSON to query string works straight from this page — free, instant, nothing to install. It sits under JSON, XML & formats in our catalogue, alongside Query string to JSON and Query String Builder.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does JSON to query string do?

Turn a flat JSON object into a URL query string.

When would I actually use this?

Making a machine-generated blob readable, finding the character where a parse fails, and shrinking a file before it ships.

What is the most common mistake?

Assuming valid means correct. A document can parse cleanly and still have the wrong shape for whatever will read it — validation checks the syntax, not the schema.

How is JSON to query string different from Query string to JSON?

They sit next to each other but answer different questions: Query string to JSON is the one to open when you need it to parse a URL query string into JSON and build one back. Repeated keys become an array, tag[]= and filtre[prix]= expand into arrays and objects, + is a space and %C3%A9 is é. Pick whichever matches what you're starting from — both are free.

Is there a tool for the next step?

Query String Builder is the closest one after this: Build a URL query string from key/value rows with correct percent-encoding, array syntax options and a UTM preset — or parse an existing URL back into rows.

What else is worth having open alongside it?

JSON String Escape / Unescape and CSV to JSON converter — they come up in the same task often enough to be worth a second tab.

Where do the figures come from?

Parsing and serialisation follow each format's specification. Key order and whitespace are not semantically meaningful in JSON or YAML, so a reformatted document is equivalent even when the bytes differ.

Further reading

All guides →
ExplainerEscaping a String for JSON: Three Characters Are Mandatory, and One Is a TrapRFC 8259 requires exactly three things to be escaped inside a JSON string. Everything else is optional. The one that actually breaks pipelines is a lone surrogate — legal in JSON text, impossible in UTF-8, and silently replaced the moment your data is written out.ExplainerJSON to CSV When the Structure Is Nested: Why There Is No Right AnswerThe same two orders come out as five columns from one converter and ten from another, and neither is wrong. Dotted paths, arrays of scalars, arrays of objects and records with different keys — four decisions, made for you, usually silently.ExplainerXML to JSON: Attributes, Repetition, and the Single-Element Array TrapTwo documents that differ only in how many children exist produce two different JSON shapes, and no converter can tell them apart without a schema. Plus what this one really does with attributes, mixed content and whitespace — and the one thing it still cannot record.ExplainerCSV to JSON: The Five Cases That Break Every ConverterQuoted delimiters, embedded newlines, ambiguous types, duplicate headers and encoding. Each one was run through the converter and the exact output is printed here — including the two cases it does not rescue.ComparisonJSON vs XML: What's the Difference?JSON and XML both store structured data as text, but they trade off differently. Here's how each looks, where each wins, and how to choose.ExplainerJSON Is Simpler Than You Think, and That Is the ProblemJSON has no integer type, no date type, no comments and no schema. Every one of those absences produces a specific bug: a 19-digit ID comes back off by 21, a timestamp becomes a string nobody agreed on, NaN cannot be written down, and duplicate keys are legal. All of it run, in two languages.