My JSON is one object, not an array. Will it work?

Yes — a single object becomes a one-row CSV. What cannot be converted is an array of bare values like [1, 2, 3], because there are no field names to make columns from.

What happens to nested arrays?

An array of simple values is joined with semicolons into a single cell. An array of objects is expanded into indexed columns such as items[0].name, which keeps the data but can produce a very wide table.

Why do some rows have empty cells?

Because those records did not contain that field. The tool builds columns from every key it sees anywhere in the data, so a field present in only some records leaves the rest blank rather than shifting the columns.

Excel is showing everything in one column.

That is a delimiter mismatch. Try semicolon-separated output, or use Excel's Data → From Text import and pick the delimiter there.

JSON to CSV

Flatten an array of objects into a spreadsheet-ready CSV.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about JSON to CSV

Questions about what this tool does, which option to pick, or what it can and cannot handle.

This is the one part of the site that uses a server. The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong; the tool itself is not guessing.

About the JSON to CSV

Spreadsheets do not read JSON, and half the people who need to look at an API response live in a spreadsheet. This tool flattens an array of objects into a CSV you can open in Excel, Numbers, Google Sheets or anything else that reads a table.

Two decisions make the difference between a usable CSV and a useless one, and the tool gets both right. The first is nesting: a value like “{"user": {"name": "Ada"}}” has no natural column, so by default it becomes a “user.name” column rather than a cell containing raw JSON. The second is ragged data. Real API responses are not uniform — the fifth record has a field the first four lacked. Rather than taking the columns from the first row, the tool collects the union of every key across every row, so no data is silently dropped off the right-hand edge.

You can choose the delimiter, which matters more than it should. Comma is standard, but Excel in a locale that uses the comma as a decimal separator expects semicolons, and a tab-separated file is the safest thing to paste directly into a sheet.

Quoting and escaping follow RFC 4180, so values containing commas, quotes or newlines survive the round trip.

How to use it

1Paste an array of JSON objects — the shape most APIs return for a list.
2Pick a delimiter: comma for a standard CSV, semicolon for European Excel, tab for pasting straight into a spreadsheet.
3Leave “Flatten nested objects” on unless you want nested values written as raw JSON in the cell.
4Download the result, then open it in your spreadsheet application.

Questions

My JSON is one object, not an array. Will it work?: Yes — a single object becomes a one-row CSV. What cannot be converted is an array of bare values like [1, 2, 3], because there are no field names to make columns from.
What happens to nested arrays?: An array of simple values is joined with semicolons into a single cell. An array of objects is expanded into indexed columns such as items[0].name, which keeps the data but can produce a very wide table.
Why do some rows have empty cells?: Because those records did not contain that field. The tool builds columns from every key it sees anywhere in the data, so a field present in only some records leaves the rest blank rather than shifting the columns.
Excel is showing everything in one column.: That is a delimiter mismatch. Try semicolon-separated output, or use Excel's Data → From Text import and pick the delimiter there.