JSON to CSV — Free, in Your Browser
The reverse of the pipeline: an API response, a log export, a config file — JSON in, spreadsheet out.
CSV ↔ JSON Converter
Both directions — 100% local
Why convert JSON to CSV
The reverse of the pipeline: an API response, a log export, a config file — JSON in, spreadsheet out. Pasting production JSON into a web form means exposing exactly the rows you were trying to analyse. Here the serialisation is local, with correct CSV quoting so values containing commas, quotes or newlines survive the trip into Excel or Sheets.
The header row is built from the union of keys across all objects, in first-seen order, so slightly inconsistent records (a field missing from some rows) still land in one tidy table with the gaps left empty.
How to do it (3 steps)
- Paste your JSON array — parsed locally.
- Check the column order and the row count.
- Copy or download the CSV.
Technical note
Nested objects and arrays are serialised as compact JSON strings inside their cell — the pragmatic choice, since CSV has no depth. Cells are double-quoted whenever they contain a comma, quote, or newline, with internal quotes doubled, which is the RFC 4180 form every serious parser accepts. If your source JSON is a single object (not an array), it is treated as one row.
The mistake worth avoiding
The common mistake is feeding it an array of objects with nested objects, then being surprised that a column contains a chunk of JSON text. That is the correct behaviour — CSV is flat, and nesting has to go somewhere — but it means the spreadsheet column is not human-readable until you parse it again. If the data you actually want is one field inside the nesting, extract that field first and convert the flattened list; the CSV will be far more useful.
FAQ
- Is my JSON uploaded? No — everything is processed in your browser.
- How are nested values handled? They are written as compact JSON text inside the cell, so no information is lost and the CSV stays one level flat.
- What if some rows are missing a field? The column still appears (union of all keys) and the missing value is an empty cell.
- Will Excel open the CSV correctly? For plain ASCII data, yes. For UTF-8 data with non-English characters, older Windows Excel builds may misread it without a UTF-8 BOM. If you see mojibake, open the CSV in a text editor and re-save it as UTF-8 with BOM.