From JSON records to a spreadsheet
Many APIs and exports give you data as a JSON array in which each item is an object with named fields. Spreadsheets such as Excel and Google Sheets, and many databases, prefer CSV (comma-separated values): one row per record, one column per field. This converter reads your array, collects every key that appears in any record to form the columns, and writes one line per object. Records that lack a field simply get an empty cell, so uneven data still lines up.
How nested data is handled
CSV is flat, but JSON can nest. The converter flattens nested objects by joining key names with a dot, so {"address":{"city":"London"}} becomes a column called address.city. Arrays are not split into extra columns, because their length differs between records. Instead each array is written into its cell as JSON text such as ["a","b"], which keeps the information intact. If you need one row per array item, reshape the data first. A single object (not wrapped in an array) is treated as a one-row table.
Quoting and delimiters
A cell is wrapped in double quotes when it contains the delimiter, a double quote or a line break, and any double quote inside it is doubled, as the CSV standard (RFC 4180) describes. That is why Grace, Jr. stays in one cell. Choose a semicolon if your spreadsheet uses a comma as the decimal mark, which is common in parts of Europe, or choose tab or pipe when your values contain many commas.
Opening the file safely
- Spreadsheet programs may interpret cells that begin with =, +, - or @ as formulas. If your data comes from an untrusted source, review such cells before opening the file.
- Excel may drop leading zeros from codes like 00123 or turn long numbers into scientific notation. Import the column as text if that matters.
- Download produces UTF-8 text. If accented characters look wrong, import the file and choose UTF-8 as the encoding.
Privacy
The conversion and the download are done by your browser. Your data is not uploaded anywhere.