Loading the interactive tool… It runs in your browser — if it doesn't appear, enable JavaScript.
Both directions of the spreadsheet-to-code bridge: CSV becomes a JSON array of objects (first row as keys) or arrays, and JSON arrays flatten back to CSV with headers derived from the keys. The parser does CSV properly — quoted fields, commas inside quotes, escaped quotes, multi-line values — which is exactly where naïve split-on-comma scripts corrupt data.
Conversion runs locally. Spreadsheets are usually customer lists, financials, exports — precisely the data that shouldn't transit a random website's server.
Frequently asked questions
Why does my CSV break other converters but work here?
Usually quoted fields containing commas ("Arlington, VA") or line breaks. RFC 4180 defines how quoting works, this parser implements it, and split(",") does not.
How are missing values handled going JSON → CSV?
The header row is the union of all keys across objects; objects missing a key get an empty cell. Nested objects are serialized as JSON strings rather than silently dropped.
Does it handle semicolon-separated files from Excel?
Yes — European Excel exports (semicolons) and tab-separated files are detected automatically from the first row.