What JSON shape does it expect?

An array of flat objects, for example [{"name":"Ada","city":"London"}]. The converter collects the union of all keys to build the header row and fills missing values with blanks.

How are commas and quotes inside values handled?

Fields that contain the delimiter, a quote or a line break are wrapped in double quotes and embedded quotes are doubled, following the RFC 4180 CSV standard.

No. The conversion runs entirely in your browser with JavaScript — your data is never sent to a server or stored.

What if my objects have different keys?

The converter scans every object and builds the header from the union of all keys it finds, in first-seen order. Objects missing a given key leave that cell blank, so the table stays rectangular.

How are nested objects and arrays handled?

A value that is itself an object or array is written as its JSON string into that cell (then quoted if needed). For a fully flat CSV, flatten nested structures into top-level keys before converting.

Can I open the result directly in Excel?

Yes. Use the comma delimiter for most setups, or semicolon if your regional Excel uses it. Copy the CSV into a .csv file, or paste with the tab delimiter straight into a spreadsheet cell.

What if I paste a single object instead of an array?

A single JSON object is treated as a one-row table — its keys become the header and its values become the single data row.

JSON to CSV Converter

Convert JSON to CSV in your browser

This tool flattens a JSON array of objects into clean CSV with a header row, ready for Excel, Google Sheets, a database import or a BI tool. It is built for developers exporting API responses and for anyone who needs spreadsheet-shaped data out of a JSON file without a script.

How it works

The tool parses your JSON, then scans every object to collect the union of all keys in first-seen order — that becomes the header row, so objects with differing fields still line up. Each object is then emitted as a row in header order, leaving a blank cell where a key is missing. Every field is escaped per the RFC 4180 standard: any value containing the delimiter, a double quote, or a line break is wrapped in quotes, and embedded quotes are doubled. Nested objects and arrays are serialised back to JSON text inside their cell.

Example

This JSON:

[
  { "name": "Ada", "city": "London" },
  { "name": "Bao", "city": "Hanoi", "role": "Designer" }
]

becomes (note the third column added from the second object, and the blank cell):

name,city,role
Ada,London,
Bao,Hanoi,Designer

The whole conversion happens locally in your browser — nothing is uploaded, so it is safe for sensitive exports.