JSON to CSV

Turn a JSON array of objects into downloadable CSV.

How JSON to CSV works

JSON is how programs and APIs hand you data, but almost nobody wants to read a wall of braces when they could open a spreadsheet. CSV is the format Excel, Google Sheets, and countless import screens accept, laid out as tidy rows and columns. This tool takes a JSON array of objects and flattens it into CSV, pulling the field names into a header row and each object into a line beneath it, so structured data becomes something you can open, sort, and share.

Paste a JSON array where each item is an object, and the tool works out the columns from the keys and writes one row per object. The result is downloadable CSV, ready to open in a spreadsheet or hand to a tool that only imports tabular files. You do not have to name the columns yourself, they come straight from the JSON keys, and every row lines up under the right heading.

There are a couple of things to keep in mind about the shape of your data. CSV is flat, so a nested object or array inside a field does not have a natural column, and it is either stringified or best flattened before conversion for a clean table. If different objects have different keys, the tool gathers the full set of columns so no field is lost, leaving blanks where a given row simply did not have that value. Values with commas or quotes are escaped properly so the file stays valid.

Pick this over writing export code when you have JSON in hand and someone just needs a spreadsheet, and over manually retyping data into cells, which is both tedious and error-prone. It turns a developer's data into a business colleague's format in one step.

It fits jobs like handing an API response to a non-technical teammate, loading records into a spreadsheet for filtering and pivot tables, preparing a JSON export for a system that only ingests CSV, and creating a quick backup of data in a format anything can read years from now. Bridging JSON and spreadsheets is a routine need across teams.

The conversion is done in your browser, so your JSON never leaves your device, there is no sign-up, and it is free. The only ceiling is your device's own memory, which handles the sized arrays most exports produce without any trouble.

Frequently asked questions

My JSON has nested objects. How are they handled?

CSV has no real place for nesting, so a nested object or array is typically written into a single cell as text rather than its own columns. For a cleaner table, flatten the structure so each value has its own top-level key before converting.

What if my objects don't all have the same keys?

The tool collects every key that appears across the array so no field is dropped, then leaves a cell blank for any row that lacks that key. This keeps the header complete even when your records are uneven.

Does the JSON have to be an array?

Yes, the expected input is an array of objects, since each object maps to a row. A single object can be wrapped in an array, and a bare value or deeply irregular structure will not map cleanly onto rows and columns.

How are commas inside a value kept from breaking the file?

Any value containing a comma, quote, or line break is wrapped in double quotes and its internal quotes are escaped, following standard CSV rules. That is what keeps the columns aligned when you open the file.

Will the column order match my key order?

Columns generally follow the order the keys first appear in your data. If you need a specific arrangement, ordering the keys in your JSON before converting is the most reliable way to control it.

Can I open the result directly in Excel?

Yes, the output is standard CSV that Excel and Google Sheets both open natively. If you specifically need the .xlsx format rather than CSV, a dedicated CSV to Excel tool is the better fit.

Related tools

Polished Pixels. All tools. About. Contact. Every tool runs in your browser and your files are never uploaded.