JSON to CSV converter

Updated 28 September 2026

To convert JSON to CSV, drop a .json file that holds a list of objects. Each object turns into a row, each key turns into a column, and you download a comma-separated file encoded as UTF-8.

The structure we expect

The input should be an array of flat records, which is the shape most APIs and exports already produce. For example: [{"sku": "A1", "stock": 4}, {"sku": "B7", "stock": 0}]. Columns follow the order in which their keys first show up. A lone object, not wrapped in a list, becomes a one-row table.

Sometimes the records sit inside a wrapper, such as an "items" property around the list. Reduce the file to the bare array first, either by cutting the list out with a text editor or by requesting the plain list from the API.

Records with different fields

Real data is rarely uniform, and that causes no trouble here. The column set is the union of every key across all the objects, so a record that lacks a field stays blank in that column. Responses where optional fields appear in some records and not in others convert with no preparation at all.

Nested values

A CSV is a flat grid. It has no room for an object inside an object, or for a list. We store such a value in the cell as compact JSON text, for example {"zip": "10001"} or ["S", "M"], so nothing is lost and it can be parsed again later. For analysis in a spreadsheet, flatten those fields beforehand, turning "shipping": {"zip": "10001"} into "shipping_zip": "10001".

Opening the result

The file uses commas and UTF-8, which most spreadsheet programs open directly. Numbers are written as plain values, and your spreadsheet decides how to interpret them. Excel set up for some European regions expects semicolons, so everything can land in one column there. In that case, convert the file with CSV to Excel and open the .xlsx workbook instead.

Daily dumps and batches

If an API hands over a new file every day, convert several at once. Without an account, a batch holds up to 5 files of up to 50 MB each, within 20 server jobs a day. A free account raises that to 10 files and 50 jobs, and Pro takes 500 files of up to 500 MB with no daily allowance. Download the CSVs one by one or in a single ZIP.

The conversion runs on our servers in Germany, not in your browser. Uploads travel encrypted, and we delete them automatically within two hours.

How to turn JSON into a table

1. Drop one or more .json files onto the page.
2. Click Convert to CSV.
3. Save the CSV files separately or as one ZIP, then open them in a spreadsheet.