How to do it
- Open the editor and drop your .tsv file onto it, or paste the rows straight from wherever you copied them.
- Check the cells and the review panel. A comma, quote or line break inside a value affects quoting; the export dialog shows the effective quoted-field mode and any required conversion.
- Choose Export, pick CSV, and set the line ending you need — LF for anything Unix-shaped, CRLF if a Windows tool is going to read it.
- Save. The file is written by your browser; it never travels.
What usually goes wrong
Commas inside cells
A product name like "Mug, ceramic" is one cell in a TSV and two in a naive CSV. The export quotes it instead, and doubles any quote character already inside.
Excel and the byte order mark
Excel reads a UTF-8 CSV as Latin-1 unless the file starts with a byte order mark, which is how accented characters become mojibake. If Excel is the destination, leave the mark on.
The trailing newline
Some parsers treat a final empty line as an extra empty row. The export keeps whatever the original had, and lets you change it deliberately.
Semicolon- and pipe-separated input can be detected, but CSV output always uses commas. The export dialog declares this delimiter conversion. TSV downloads use UTF-8 and tabs; CSV downloads use UTF-8 and commas. Review the effective record line endings, BOM and final line break in the export dialog. Quotes are rebuilt, and mixed record endings become uniform. Unsafe output is blocked; explicit quoting conversion is offered when it preserves the table, and ambiguous input requires confirmation.