Input
Waiting for input.
Output
CSV parsing follows RFC 4180 — quoted fields, escaped quotes and embedded newlines all round-trip.
CSV parsing follows RFC 4180 — quoted fields, escaped quotes and embedded newlines all round-trip.
Spreadsheets are still how most of the world looks at data. This converts an array of JSON objects into a CSV whose header is the union of every row's keys — so a field that only appears in later rows still gets a column — and converts CSV back to JSON, rebuilding nested objects from dot-notation headers. Quoting, escaped quotes and embedded newlines follow RFC 4180 in both directions.
JSON to a spreadsheet-ready CSV, and CSV back to JSON, with the direction detected automatically.
Nested objects become dot-notation columns, and rebuild into objects on the way back.
Columns cover every key in every row, so a field that appears late still gets one.
Commas, quotes and newlines inside values survive the round trip in both directions.
Nested objects flatten to dot-notation columns such as address.city, and convert back into nested objects on the way in. Arrays inside a row are kept as JSON text in the cell.
Yes. If accented or non-Latin characters look wrong, tick "Excel BOM" — that adds the byte-order mark Excel looks for.
Yes, in both directions: fields containing a delimiter, quote or newline are quoted and escaped per RFC 4180, and parsed back the same way.