JSON to CSV
The reverse of our CSV converter: paste an array of JSON objects and get CSV with the columns detected from your keys, proper quoting for commas and quotes inside values, and a delimiter of your choice.
100% private — everything runs in your browser, nothing is ever uploaded.
What this tool does
An API returns an array of objects and a colleague asks for it as a spreadsheet. Copying JSON into Excel does not work, and writing a converter for a one-off report is a distraction. This tool takes an array of JSON objects, detects the column names from the keys, quotes values properly so commas and double quotes inside a field survive, and produces CSV with a delimiter of your choice — comma, semicolon or tab. It is the reverse of the CSV to JSON converter on this site, so the two can be used to round-trip data through a quick edit: convert to CSV, tidy a column, convert back. It is meant for modest datasets that a person needs to open in a spreadsheet, not as an ETL pipeline for very large exports.
How to use it in three steps
- Paste a JSON array where each element is an object with the same or similar keys. Nested objects should be flattened first if you want each field in its own column.
- Choose the delimiter. Comma suits most spreadsheet imports, semicolon suits many European locales, and tab is useful when values contain commas.
- Press Convert, then copy the CSV or download it. Open it once in your spreadsheet to confirm that quoted fields landed in a single cell. Open the downloaded CSV in a spreadsheet once to confirm that quoted commas stayed inside a single cell.
Questions people ask
What happens when objects have different keys?
The column set is taken from the keys present in the data, and missing values are left empty so every row keeps the same shape. Review the header row before importing into a system with a strict schema.
Why did a value get split into two cells?
That usually means the delimiter you chose appears inside an unquoted value. The tool quotes such fields automatically; if a downstream system strips quotes, switch to tab or semicolon as the delimiter.
Can it handle nested objects or arrays?
Nested structures do not map cleanly to flat spreadsheet columns. Flatten them into simple key-value fields before converting, or keep the JSON for anything that needs the original structure.
What if my array contains dates or boolean values?
Simple values are written as their text representation, so true becomes the word true and a date string stays exactly as supplied. If a target spreadsheet needs a particular date format, format that column after import rather than expecting the converter to guess it.
Privacy: JSON is parsed and written out as CSV entirely inside this browser tab, so API responses containing customer records, prices or internal fields never leave your device or touch a server.
How to use it
- Paste a JSON array — each element should be an object with the same or similar keys.
- Choose the delimiter: comma, semicolon or tab.
- Press Convert, then copy the CSV or download it.
Why it stays private
API responses often contain customer data, tokens or internal identifiers. The conversion is pure text processing inside your tab — the JSON is never transmitted.
Questions
What if my objects have different keys?
The column set is the union of every key found, in order of first appearance. Objects missing a key simply get an empty cell, so nothing is lost or misaligned.
How are commas and quotes inside values handled?
Properly. Any value containing the delimiter, a quote or a newline is wrapped in double quotes, and internal quotes are doubled — exactly what Excel and Google Sheets expect.
Can I paste nested JSON?
Flatten it first. Nested objects and arrays are stringified into their cell as JSON, which is honest but ugly — most people pre-flatten with a map() before converting.