Delimiter.live
20 tools

JSON Tools

JSON tools handle the everyday work of reading and reshaping JSON: pretty-printing a compact API response, checking that a payload actually parses, shrinking it before deployment, converting it to CSV for a spreadsheet, and pulling single values out with JSONPath. Every JSON tool on Delimiter.live parses in your browser, so production payloads are never uploaded.

JSON is the default interchange format for web APIs, configuration files and log pipelines, which means most developers meet it in one of three broken states: minified into a single unreadable line, subtly malformed after a hand edit, or shaped correctly but in the wrong format for whatever needs to read it next.

The tools below cover all three. Formatting and validation tell you what the payload is and whether it parses; the converters move it between JSON, CSV, XML and YAML; JSONPath extraction pulls out the two fields you actually care about from a response with four hundred.

Read and repair

4 tools

Turn a minified or broken payload into something you can inspect, and find out exactly where it fails.

Compare and combine

2 tools

Work out what changed between two documents, or layer one over another.

Reshape

4 tools

Change the shape of a document without changing what it means.

Convert to another format

8 tools

Move records between JSON and the formats spreadsheets, config systems and older APIs expect.

Query and extract

2 tools

Find the values you need in a large response without writing a script.

What people use these for

  • Pretty-print a minified API response so you can read the structure while debugging.
  • Confirm a hand-edited config file still parses before committing it.
  • Turn a JSON export into a CSV a colleague can open in Excel or Sheets.
  • Convert a YAML pipeline definition to JSON to feed a tool that only accepts JSON.
  • Extract a single nested field from a long response with a JSONPath expression.
  • Minify a JSON fixture to cut bytes off a bundle or a network payload.

JSON Tools: frequently asked questions

Is my JSON uploaded when I use these tools?
No. Every tool in this hub parses and rewrites JSON in JavaScript inside your browser tab. Nothing is transmitted to Delimiter.live, which is what makes them safe for production payloads and internal exports. Closing the tab discards the data.
Why does the validator reject my file when it has comments?
Comments are not part of the JSON specification. Formats that allow them — JSONC, JSON5, and most config files that look like JSON — are supersets. Strip the comments first, or convert from YAML, which does support them.
What is the difference between a JSON formatter and a JSON validator?
A formatter rewrites valid JSON with consistent indentation so it is readable. A validator only reports whether the input parses and, if not, where it breaks. The formatter has to parse the input too, so it fails on invalid JSON as well — the validator simply gives you a clearer error report.
How big a JSON file can these tools handle?
Files up to roughly 10 MB are comfortable on a modern laptop. Beyond that the browser tab may pause for a few seconds while parsing, because the whole document has to be held in memory at once. There is no server-side limit because there is no server involved.
What happens to nested objects when I convert JSON to CSV?
They are flattened into dot-separated column headers such as user.address.city, so nothing is silently dropped. Arrays can either be flattened the same way or written into a single cell as inline JSON, depending on the option you choose.
All tools →

Last reviewed 7 August 2026.