CSV to JSON

Reading CSV correctly

CSV looks trivial until a field contains a comma, a quote or a line break. RFC 4180 handles those by wrapping the field in double quotes and doubling any quote inside: "Smith, ""Jr.""". Splitting lines on commas breaks such files; this converter implements the full rules, so addresses, notes and descriptions come through intact.

The first row is used as the keys of each object. With detect types on, 42, 3.14, true, false and null become JSON numbers, booleans and null; values like 007 or 01310-100 stay strings, so ZIP codes and IDs keep their leading zeros.

Worked example

sku,name,price,in_stock
A-001,"Mug, large",12.5,true
B-002,"Poster ""Blue""",8,false

becomes an array of two objects: {"sku": "A-001", "name": "Mug, large", "price": 12.5, "in_stock": true} and {"sku": "B-002", "name": "Poster \"Blue\"", "price": 8, "in_stock": false}.

The page reads the text in one pass with an RFC 4180 parser: quoted fields can contain the delimiter, quotes (written twice) and line breaks, and records may end with CRLF or LF. The first record becomes the header unless you turn that off, in which case each row becomes an array. With type detection, a cell that is exactly a JSON number, true, false or null is converted; anything else, including numbers with leading zeros or decimal commas, stays a string. Use JSON to CSV for the reverse. Everything runs in this tab.