From API response to spreadsheet — and back
JSON is how machines exchange data; CSV is how people analyze it. Nearly every export path from code to a spreadsheet — Excel, Google Sheets, Numbers — runs through CSV, and nearly every path from a spreadsheet into a script runs back through JSON. This tool converts both directions and handles the two things that usually break naive converters:
- Nested objects are flattened using dot notation:
{"contact": {"city": "Berlin"}}becomes acontact.citycolumn, so no data silently disappears. - Quoting and escaping follow the CSV standard (RFC 4180) — commas, quotes and line breaks inside values survive the round trip, and converting CSV back to JSON restores proper types for numbers and booleans.
Exports frequently contain customer lists, revenue figures and other data you don't want on a third-party server. Like every LocalConvert tool, this converter runs entirely in your browser tab — paste, convert, copy or download, and nothing is transmitted.
Frequently asked questions
What JSON shape does CSV conversion expect?
An array of objects — the standard shape of API list responses. A single object is treated as a one-row array. Deeply nested objects are flattened into dot-separated column names.
How are arrays inside objects handled?
Arrays of primitives are written as JSON strings in a single cell (for example
"[1,2,3]") so nothing is lost. If you need one row per array element, restructure the data first.Will Excel open the result correctly?
Yes — the output uses comma separators and standard quoting, which Excel, Google Sheets and LibreOffice all understand. If your locale's Excel expects semicolons, use "Data → From Text/CSV" and pick the comma delimiter.