CSV to JSON Converter

Example: a US order can store "currency": "USD" and "amount": 1234.56. JSON numbers use a dot and no thousands separator; write the date as "2026-10-11". Formatting preserves the stored value; it does not convert currencies or interpret local dates.

For exported data, record the units, date format and currency explicitly. A display value such as $1,234.56 needs a stated currency; 10/11/2026 needs a stated date convention. Check this tool’s output and required syntax before using it in another system.

Yes, completely free with no registration. All parsing happens locally in your browser.

Yes, as long as the field is quoted per RFC 4180. The parser correctly handles embedded commas, doubled quotes (""), and multi-line quoted fields - things that break naive split() approaches.

Yes. Turn off the "First row is the header" option and every row - including the first - is emitted as a plain array of strings.

Values that parse as finite numbers become JSON numbers, the exact strings true and false become booleans, and empty cells become null. Any other value stays a string. Disable the option to keep every value as a string.

Yes. Leave the delimiter on auto-detect (it counts candidate delimiters in the first line) or select semicolon or tab manually.

Each column is scanned: all-numeric → number, true/false → boolean, empty string → null, everything else → string. Type inference is per-column, not per-cell, so a column stays homogeneous - "007" in an ID column of strings remains a string, avoiding the classic spreadsheet leading-zero loss.

Yes - headerless mode names columns c1, c2, c3. This covers machine-generated exports where the schema lives elsewhere, and legacy files whose header row is actually the first data record.

RFC 4180 quoting is honored: a quoted field may contain commas, newlines, and doubled quotes, and the parser keeps them intact in the JSON string. Malformed rows (unbalanced quotes) are reported with line numbers instead of silently truncating the field.