Converting JSON
Paste the JSON
An array of objects is the usual input. A single object also works and becomes one row.
Choose flattening
Flatten nested objects into columns is on by default: {"contact": {"email": ...}} becomes a contact.email column. Turn it off to keep each nested value as a JSON string in one cell.
Pick a separator
Comma suits most spreadsheets in English. Semicolon is common where the comma is the decimal mark; tab and pipe are also offered.
Check the note and save
The note shows the number of rows and the column names found. Copy the CSV or download data.csv. If the JSON is not valid, the error says where parsing stopped.
Two records with different fields
Real JSON is rarely uniform. Here the first business has a nested contact object and a list of tags, and the second has a rating the first lacks.
The CSV has one column for every key found anywhere: business, town, contact.email, contact.phone, tags and rating. The tags array is joined into one cell as pottery; workshops. Cells for keys a record does not have are left empty rather than filled with a placeholder.
[
{"business": "Kiln & Co Pottery", "town": "Frome",
"contact": {"email": "[email protected]", "phone": "01632 960410"},
"tags": ["pottery", "workshops"]},
{"business": "Marlow Print Works", "town": "Bath", "rating": 4.6}
]business,town,contact.email,contact.phone,tags,rating Kiln & Co Pottery,Frome,[email protected],01632 960410,pottery; workshops, Marlow Print Works,Bath,,,,4.6
Terms in the options
- Flattening
- Turning nested objects into top-level columns by joining the key names with a dot, so a value two levels deep gets a column like contact.email.
- Array of objects
- JSON that starts with [ and holds a list of { } records. Each record becomes one CSV row.
- Separator
- The character between values in each row. Comma is standard; semicolon avoids clashes with decimal commas.
Getting JSON into the hands of a sales team
Plenty of tools that collect or enrich business data hand results over as JSON, which is ideal for code and awkward for everyone else. Converting to CSV makes the same data sortable and filterable in a spreadsheet, so whoever is planning the outreach can see which records have an email, which town each is in and what was found.
Deeply nested data turns into many columns. A list of objects, such as opening hours with a day and a time each, is spread across numbered columns like hours.0.day, hours.0.open, hours.1.day and so on. That keeps one row per record but can make a very wide sheet, so remove the fields you do not need from the JSON before converting.
Questions people ask
How do I convert nested JSON to CSV?
Leave Flatten nested objects into columns ticked. Every nested key becomes its own column, named with the path to it, such as contact.email or address.postcode. Records that do not have a given key get an empty cell, so all rows line up under the same headers in the spreadsheet.
What happens to arrays inside the JSON?
A simple list of values, such as tags or categories, is joined into one cell with semicolons between the items. A list of objects is flattened into numbered columns instead, for example hours.0.day and hours.1.day. Either way you keep one row per record; split or reshape in your spreadsheet afterwards if you need to.
Why do I get a JSON error?
The text is not valid JSON, and the message gives the position where reading stopped. Common causes are a missing comma between records, a trailing comma before ] or }, single quotes instead of double quotes, or only part of a response being copied. Fix that spot and the CSV appears.
Will the CSV open correctly in Excel?
Yes for most data. Choose the separator your Excel expects: comma in UK and US settings, semicolon in many European ones. If accented names look garbled after a double-click, use Excel's import from text option and pick UTF-8, or convert straight to .xlsx with the JSON to Excel tool.
Where your data goes
Your JSON is parsed and flattened by your own browser. No part of it, nor the CSV, is sent across the network.
Checked against the tool on