JSON to CSV moves values, not the whole workbook
Analysts turn API JSON into a sheet so they can filter it.
An array of objects becomes rows. Nested objects are flattened where the structure is simple.
Dates and extra sheets after JSON to CSV
Deep nesting does not fit one table. Check the CSV in a text editor before Excel touches the dates.
A related step, if you still need one, is CSV to JSON.
JSON to CSV without the extra promises
JSON to CSV sits on this site because JSON and CSV are not interchangeable, even when they look similar in a file list. Analysts turn API JSON into a sheet so they can filter it. Developers convert JSON when a payload must become a sheet, XML, or CSV. Mail merges, databases, and Google Sheets imports are typical CSV jobs.
An array of objects becomes rows. Nested objects are flattened where the structure is simple.
Read this about JSON before you upload
JSON is the text format APIs and web apps use. It can nest, which a single spreadsheet cannot. Nested lists of unknown length will not become one tidy sheet.
Keep the original payload until you have checked the shape of the output.
Read this about CSV before you send the download
The download has to be CSV, because that is the format the next step named. Mail merges, databases, and Google Sheets imports are typical CSV jobs. Almost every data tool can read a simple CSV.
Open the file in a text editor if Excel guesses types and strips leading zeros.
Keep, check, then delete
People lose time when they convert before they know which rule failed. Size, pixel dimensions, codec, font encoding, and layout are different rules. JSON to CSV only addresses the JSON to CSV step. Analysts turn API JSON into a sheet so they can filter it. An array of objects becomes rows. Nested objects are flattened where the structure is simple. Deep nesting does not fit one table. Check the CSV in a text editor before Excel touches the dates. The file stays in your browser and is not uploaded. The limit is 100 MB. Keep the original until the download has been opened in the program that will use it. Do the test with a short or simple file first when the real file is large. A one-page PDF, a single photo, or a one-minute clip will show you whether the output is the kind of file you needed. After that test looks right, run the real file once. Keep both the JSON original and the CSV download until the receiving person or the upload form accepts it. Spreadsheets break at quiet places: a second sheet, a date that changed, a leading zero that vanished, a comma inside a name. After JSON to CSV, open the result in a text editor as well as Excel. Excel guesses types and hides the delimiter. The workbook you calculated in is still the master.
Here is the decision for JSON to CSV. You start with JSON and you stop when a real program accepts CSV. A list of similar objects maps cleanly to rows. A comma inside a name splits one column into two unless the field is quoted. Extra sheets disappear. If those two sentences describe a tradeoff you do not want, do not convert. Renaming the extension by hand will not do this job. Running the tool twice on its own output will not do it either.
Deep nesting does not fit one table. Check the CSV in a text editor before Excel touches the dates.
A related step, if you still need one, is CSV to JSON.
Other jobs start from the homepage, where each tool is named for the conversion it actually does.