CSV & JSON Converter

Convert between CSV and JSON. Parsed locally in your browser.

Result will appear here...

Convert CSV to JSON and back with proper handling of quoted fields, embedded commas and custom delimiters — the cases where a naive split on comma produces silently wrong data.

Why splitting on commas fails

CSV allows a field to be wrapped in double quotes, and inside those quotes a comma is data rather than a separator. A naive split turns one address field into three broken columns, and the row silently shifts.

Quotes inside a quoted field are escaped by doubling them, so a value containing a literal quote appears as three quotes in the file. Parsers that do not handle this produce output that looks plausible and is wrong, which is worse than an error.

Encoding is the other trap

Excel on a Chinese or Western European locale commonly writes CSV in a local encoding rather than UTF-8, and often adds a byte-order mark at the start. Read that file as UTF-8 and every accented character becomes mojibake, and the first column name gains an invisible character that breaks lookups.

If a header looks correct but a field reference fails, check for a BOM. It is invisible in most editors and present in most files exported from Excel.

CSV has no types

Everything in a CSV file is text. A column of numbers becomes JSON numbers only if the converter guesses, and that guess is where leading zeros disappear from postcodes and long identifiers lose precision.

For anything where the exact string matters — phone numbers, account numbers, zero-padded codes — keep the value as a string. This is also why large integers should stay strings in JSON.

Frequently asked questions

Does it handle semicolon or tab delimiters?
Yes. European Excel exports often use semicolons because the comma is the decimal separator there. Select the delimiter before converting.
What happens with nested JSON output?
A flat CSV has no nesting, so the output is a flat array of objects. Use dot notation in the header if you want the converter to build nested keys.
Is my data uploaded?
No. Parsing runs in the page. This matters for customer exports, which usually contain personal data.