JSON to CSV Converter
Convert JSON data into clean, spreadsheet-ready CSV format instantly. Handles arrays, objects, and missing fields automatically.
How to Convert JSON to CSV
JSON is the standard format for APIs and web data, but spreadsheets and CRMs expect CSV. Manually converting between them is tedious and error-prone, especially when objects have different fields or nested structures.
Our free JSON to CSV converter handles this automatically. Paste a JSON array of objects, and the tool extracts all unique keys as column headers, then maps each object to a row. Missing fields become empty cells, and values containing commas or quotes are properly escaped per CSV standards.
Common use cases: exporting API responses to Excel, converting database query results for analysis, transforming web-scraped JSON data into importable lists, and preparing data for tools that only accept CSV. Everything runs in your browser for complete privacy.
A Worked Example, and the Cases That Trip People Up
Suppose an API returns a list of orders. Each order has an id, a customer object with name and email, and an items array. Paste that JSON into the converter and you get one row per order with the nested customer fields flattened into customer.name and customer.email columns. The items array becomes a single cell containing the array as text, because a spreadsheet row cannot hold a list. If you need one row per item instead, convert the items array on its own and add the order id to each item first; that is a reshape, not a conversion, and the tool deliberately does not guess which shape you want.
Things the converter handles for you
- Missing keys. If some objects lack a field, the column still appears and the cell is left empty, so every row has the same number of columns and the file opens cleanly.
- Commas, quotes and line breaks inside values. Cells that contain them are quoted and escaped according to the CSV standard, which is where most hand-rolled conversions break.
- Numbers that look like IDs. Long digit strings are written as text so a spreadsheet does not turn
00012345into12345or a 17-digit ID into scientific notation. Our guide on leading zeros explains the spreadsheet side of that problem. - Dates. Written exactly as they appear in the JSON. Standardising them is a separate step; the CSV Cleaner and the date-format guide cover it.
Things to check after converting
Open the result in the tool it is destined for and confirm the import reads the right number of rows. Compare that count to the number of objects in the JSON. Look at the last row and the longest cell, which is where quoting problems show up. If the JSON was an object of objects rather than an array, the converter uses the keys as a first column; check that is what you wanted. Everything runs in your browser and nothing is uploaded, so you can safely test with the real export; just do not paste it anywhere else.