scriptiii
100% Client-Side

comma · semicolon · tab · pipe

CSV delimiter converter

Re-delimit a table without changing its data — quoting is recalculated for the new separator, not copied blindly.

0 characters

Conversion runs in this tab. Exports carry names and amounts, so nothing is uploaded.

Short answer: pick the delimiter the file uses, pick the one you need, and the fields are re-joined with quotes where they are required — nothing else is touched.

The three cases that break naive converters

When it is not just a delimiter problem

If the columns are shifted, the file may contain an unclosed quote — the notes say when rows have different field counts. Moving to a structure instead of a table? TheJSON ↔ CSV converter is the right tool.

Delimiter questions

Why does my European export use semicolons?

Because the comma is the decimal separator there. In a locale where 1299,50 means one thousand two hundred ninety-nine and a half, a comma cannot also separate columns — so Excel writes semicolons. Converting to a comma file for an Indian or US system is the usual fix.

Are quotes kept?

Only where they are still needed. A field is quoted when it contains the new delimiter, a newline or a quote character. A value like "Ravi; K" needs no quotes in a comma file, so they are removed rather than carried along.

Will this handle a field that contains a newline?

Yes — quoting is what makes a newline legal inside a field, and it is preserved. That is also why the row count can be lower than the number of lines you see in the textarea.

Is my file uploaded?

No. Parsing and re-emitting happen in this tab. Exports routinely contain customer names and amounts, so nothing is sent anywhere.

Related tools

JSON ↔ CSVMove between rows and objects.Markdown tableRows into a pipe table.YAML ↔ JSONThe same idea for config files.JSON formatterTidy the result.