How JSON becomes a table
CSV is a flat grid: one header row, then one row per record. JSON is a tree. Converting one to the other means deciding what a row is and what a column is, and this tool makes the same choices most spreadsheet imports expect.
Each object in the top-level array becomes one row. If you paste a single object, you get one row. If the array sits inside a wrapper such as {"data": [...]}, the tool uses that inner array when it is the only array of objects in the wrapper.
Columns are the union of all keys. Real API responses are ragged — one record has a note, another does not. Every key seen in any record gets a column, in order of first appearance, and missing values are left empty rather than shifting cells sideways.
Nested objects and arrays
| JSON value | CSV result |
|---|---|
"address": {"city": "London"} | Column address.city with value London |
"tags": ["math", "code"] | One cell: math; code |
"items": [{"sku": 1}, {"sku": 2}] | One cell containing the JSON text of the array |
null or a missing key | Empty cell |
true / false | true / false |
Nested objects are flattened with dot notation because that keeps one value per cell. Arrays of objects are deliberately not exploded into extra rows: doing that silently duplicates the parent record and breaks sums and counts. If you need one row per line item, convert that inner array on its own.
Quoting rules (RFC 4180)
CSV has no official standard, but RFC 4180 describes the format nearly every program accepts, and this tool follows it:
A field is wrapped in double quotes if it contains the delimiter, a double quote, or a line break. A double quote inside a quoted field is written twice. So the name Grace "Amazing" Hopper becomes "Grace ""Amazing"" Hopper", and rear admiral, USN becomes "rear admiral, USN". Rows end with CRLF.
Getting this wrong is the most common cause of a CSV that opens with its columns out of line.
Opening the file in Excel without mangled characters
Accented letters show as é. Excel assumes a legacy code page unless the file starts with a UTF-8 byte order mark. Leave “Add UTF-8 BOM” selected and names such as José or Müller display correctly.
Everything lands in column A. In locales that use a comma as the decimal separator, Excel expects a semicolon between fields. Switch the delimiter to semicolon.
Long numbers turn into 1.23E+15 and leading zeros vanish. That is Excel reinterpreting the cell, not a fault in the file. Import through Data → From Text/CSV and set the column type to Text for IDs, phone numbers and ZIP codes.
Cells starting with = + - or @. Spreadsheets treat these as formulas. If the JSON came from an untrusted source, review such cells before opening the file — this is known as CSV injection.
Limits
The conversion runs in your browser's memory, so files up to a few tens of megabytes are fine and nothing is uploaded. Very large numbers beyond 253 lose precision when JSON is parsed in JavaScript; keep such IDs as strings in the source data. If the input does not parse, check it first with the JSON formatter, which points to the line with the error.
Frequently asked questions
How do I convert JSON to CSV?
Paste a JSON array of objects, choose a delimiter and press Convert. Each object becomes a row and each key becomes a column; then copy the result or download it as a .csv file.
How are nested objects handled?
They are flattened using dot notation. An address object with a city key becomes a column named address.city.
What if my objects have different keys?
Every key that appears in any object gets its own column. Objects that lack that key have an empty cell in that column.
Why does Excel show strange characters in my CSV?
Excel does not assume UTF-8 unless the file begins with a byte order mark. Download with the UTF-8 BOM option enabled and accented characters display correctly.
Is my data sent to a server?
No. Parsing and conversion happen in your browser. The JSON never leaves your device.