Convert a JSON array of objects to CSV for Excel and Google Sheets — RFC 4180 quoting, nested objects flattened into dotted columns, comma/semicolon/tab delimiters.
Show calculation steps
Processed privately in your browser — nothing you paste is uploaded, logged or stored.
From API response to spreadsheet
The fastest route from JSON to analysis is usually a spreadsheet. This converter maps an array of objects to CSV — one row per element, columns from the union of keys — with nested objects flattened into dotted columns (address.city) and full RFC 4180 quoting so commas, quotes and line breaks inside values cannot break the table. Delimiter options cover the Excel-locale semicolon and tabs.
Worked example
[
{ "name": "Asha", "role": "Editor, senior", "address": { "city": "Pune" } },
{ "name": "Ravi", "role": "Writer", "address": { "city": "Delhi" } }
]becomes:
name,role,address.city
Asha,"Editor, senior",Pune
Ravi,Writer,DelhiWhen to use it
- Getting API data into Excel, Google Sheets or a BI tool.
- Preparing import files for CRMs and databases.
- Chaining after the Query Filter to export exactly the records you need.
Limitations to know
- CSV is flat and untyped — everything becomes text, and arrays inside rows are inlined as JSON strings. For structured columns from deep arrays, reshape first with the JSON Flattener.
- Leading zeros: spreadsheets may reinterpret “007” as 7 on import — an Excel behavior, not a CSV one; import the column as text.
Common errors and fixes
- Excel shows one column — switch the delimiter to semicolon (regional settings) and re-download.
- “The array is empty” — no rows to export; check you pasted the records array, not a wrapper object.
How to use the JSON to CSV Converter
- Paste a JSON array of objects — one object per row.
- Pick the delimiter (comma, semicolon for many Excel locales, or tab).
- Keep "flatten nested objects" on to turn user.city-style paths into columns.
- Click "Convert to CSV" and download the file for Excel or Sheets.
Frequently asked questions
How does nested JSON become flat CSV columns?
Nested objects are flattened into dotted column names — address.city, address.pin — using the same logic as the JSON Flattener. CSV is inherently flat, so this is the standard way to keep every value addressable.
Why does Excel put everything in one column?
Regional settings: in many locales Excel expects semicolons, not commas. Switch the delimiter option to semicolon and re-download — that fixes it in almost every case.
How are commas and quotes inside values handled?
Per RFC 4180: fields containing the delimiter, quotes or line breaks are wrapped in double quotes, and inner quotes are doubled (""). Spreadsheet apps read this correctly — no manual escaping needed.
What if objects have different keys?
Columns are the union of all keys across rows; missing values are empty cells. Nothing is dropped, and no placeholder values are invented.
