Skip to content

JSON to CSV Converter - Convert JSON Arrays to CSV Online

Input must be a JSON array of objects, e.g. [{"name": "Alice", "age": 30}]

Switch to CSV → JSON
Input JSON
CSV Output

Convert JSON to CSV

Paste a JSON array of objects and get CSV with one row per object and one column per key. Copy it, or download it as a .csv file for Excel, Google Sheets or a database import. The conversion runs in your browser, so exports with personal or financial data are not uploaded.

Example

[
  { "id": 1, "user": { "name": "Ann", "tags": ["a", "b"] }, "note": "say \"hi\", ok" },
  { "id": 2, "extra": null }
]

converts to:

id,user.name,user.tags,note,extra
1,Ann,"[""a"",""b""]","say ""hi"", ok",
2,,,,

The nested user object became two dotted columns, the array was written as JSON text, the note with a comma and quotes was quoted, and the second row has empty cells for every key it lacks.

Options

  • Delimiter: comma, semicolon, tab or pipe. Use semicolons for Excel in locales that write decimals with a comma, such as most of Europe, or Excel will put everything in one column.
  • Nested objects: flatten to dotted columns, or keep each nested object as JSON text in one cell.

Large integers such as 12345678901234567890 are written exactly as in the input. Excel will still show them in scientific notation and drop digits after the 15th when it opens the file, so import ID columns as text there. To go the other way, use the CSV to JSON converter.

Related Tools

Frequently Asked Questions

What JSON does the converter accept?
An array of objects, where each object is one row: [{"name":"Ann","age":30},{"name":"Bob","age":25}]. A single object or an array of plain values is rejected. If your API wraps the list, as in {"data":[...]}, paste only the array.
How are nested objects and arrays handled?
By default nested objects are flattened into dotted column names, so {"user":{"name":"Ann"}} gives a user.name column. Choose "Keep as JSON text" to write each nested object into one cell as JSON instead. Arrays are always written as JSON text, such as ["a","b"], because there is no single right way to spread a list across columns.
What if my objects have different keys?
The header is every key found in any object, in the order they first appear. A row that lacks a key gets an empty cell. A null value also becomes an empty cell, so null and missing look the same in the CSV.
Why do accented characters look wrong when I open the file in Excel?
Excel on Windows often opens a CSV as the local legacy encoding instead of UTF-8, so é shows as é. Use Data > From Text/CSV and pick UTF-8 (65001), or open the file in Google Sheets or LibreOffice, which detect UTF-8 correctly.
How are commas and quotes inside values handled?
Per RFC 4180: a value containing the delimiter, a double quote or a line break is wrapped in double quotes, and quotes inside it are doubled. say "hi", ok is written as "say ""hi"", ok".