Skip to content
SUMILORASUMILORA

CSV to JSON

Developer tools

Paste CSV. The delimiter is detected, and problems are reported rather than silently absorbed.

Runs in your browser

Nothing is uploaded. The work happens on your own device, so your file or text never reaches us.

About this tool

Splitting on commas does not work

Real CSV files contain commas inside quoted fields, quotes escaped by doubling, and newlines inside a single value. Splitting a line on commas mangles every one of them — which is why so many online converters corrupt address columns.

This parses character by character with proper quote state, so "Smith, John" stays one field and a value containing a line break stays one value.

It also handles two things Excel does: a byte-order mark at the start of the file, which corrupts the first column name if left in, and semicolon delimiters, which Excel writes in locales where the comma is the decimal mark.

Problems are reported, not hidden

Ragged rows, an unterminated quoted field, a detected delimiter you did not expect — all of these appear as notes above the output.

A converter that silently pads a short row has made a decision about your data without telling you. Knowing that row 47 had three columns where the rest had five is usually the most useful thing the conversion can tell you.

Questions

Why does my CSV have semicolons?

Excel writes semicolons in locales where the comma is the decimal separator — most of continental Europe. It is detected automatically here.

What is the BOM at the start of my file?

A byte-order mark Excel adds when saving as "CSV UTF-8". Left in, it becomes part of the first column name and breaks lookups. It is stripped here.

Related tools