Spreadsheets export CSV and APIs speak JSON, so the gap between them has to be crossed constantly — a column of records exported from a report and needed as a request body, or a response that has to land in a spreadsheet someone else will read. This converter goes both ways and handles the parts of CSV that trip up a naive split on commas: quoted fields, commas and line breaks inside them, and doubled quotes. It can also read values as their real types, so a column of numbers arrives as numbers rather than strings. The whole conversion runs in your browser, which matters because exported spreadsheets are usually full of customer data.
No. The file is read and parsed by your browser inside the page. Nothing is sent over the network, which is worth knowing when the export contains names, emails or order records.
Yes. The parser follows RFC 4180: a field wrapped in double quotes can contain the delimiter, line breaks, and doubled quotes to mean a literal quote character. That is exactly what a spreadsheet writes when a cell holds an address or a sentence.
They are not — type conversion deliberately leaves them alone. A value like 01234 is not a valid plain number, so it stays a string. Turn type conversion off entirely if you want every value to remain text.
An empty header becomes column1, column2 and so on, and a repeated name gets a numbered suffix. Without that, later columns would silently overwrite earlier ones, because a JSON object cannot hold the same key twice.
Only shallowly. CSV is a flat grid, so a nested object or array is written as JSON text inside its cell rather than spread across columns. Flatten the structure first if you need each field in its own column.