CSV Encoder & Delimiter Fixer

About CSV Encoder & Delimiter Fixer

CSV/TSV Encoder & Delimiter Fixer is a comprehensive tool for repairing and converting CSV file formats. Change delimiters (comma to semicolon, tab to pipe, etc.), add or remove a UTF-8 BOM for Excel, normalize quotes and escapes per RFC 4180, convert line endings, and validate column-count consistency before a database or spreadsheet import—all processed locally in your browser.

What is CSV Encoder used for?

CSV Encoder fixes common CSV formatting problems: changing delimiters (e.g., converting European semicolon-separated files to standard comma-separated), repairing encoding issues (UTF-8 vs Latin1), adding or removing BOM (Byte Order Mark), normalizing line endings (Windows CRLF vs Unix LF), and fixing malformed quotes or escape characters.

What is BOM and when should I use it?

BOM (Byte Order Mark) is a special character sequence at the start of UTF-8 files. Some applications (especially Microsoft Excel) require UTF-8 BOM to correctly display non-ASCII characters (accents, Chinese, Arabic, etc.). Enable 'Add BOM' if you're creating CSV files for Excel with international characters.

How do I fix Excel CSV delimiter issues?

Excel in different regions uses different default delimiters: English Excel uses commas, European Excel uses semicolons. If your CSV file shows all data in one column, the delimiter is wrong. Use this tool to auto-detect the input delimiter and convert it to your Excel's expected format.

What does 'Fix malformed quotes' do?

This option repairs common quoting errors: unescaped quotes inside fields, missing closing quotes, and inconsistent quote usage. It ensures all fields with special characters (quotes, commas, line breaks) are properly quoted and escaped according to RFC 4180 CSV standards.

What encodings does this tool handle?

Input is read as UTF-8 (the modern standard) and output is always UTF-8. You can choose UTF-8 without a BOM, or UTF-8 with a BOM that is applied only to the downloaded file. The BOM is the byte sequence Excel looks for to display accented or non-Latin characters correctly. Legacy single-byte encodings such as Latin1 or Windows-1252 are not transcoded here; re-save those files as UTF-8 first.

How do I validate column counts before a database import?

Click Convert & Fix and read the Structure Validation report. It shows the header column count and scans every data row for a mismatched field count. A single ragged row—one extra or missing delimiter—shifts every later column and breaks a DB load or pivot. The report gives a PASS/FAIL verdict and lists the exact offending row numbers and their column counts so you can fix the source before it pollutes a pipeline.

Why does Excel show garbled characters (mojibake) in my CSV?

Excel assumes the system code page when a UTF-8 file has no BOM, so accents and non-Latin text turn into mojibake like 'é'. Select 'UTF-8 with BOM' and download: the tool prepends the BOM only at download time so Excel auto-detects UTF-8, while Copy Output stays BOM-free for pasting into databases or scripts.

Can I convert a TSV (tab-separated) file to CSV?

Yes. Set the input delimiter to Tab (or leave it on Auto-detect) and the output delimiter to Comma, then Convert & Fix. The tool splits on real tab characters and re-emits comma-separated, RFC 4180-quoted output. Reverse the delimiters to go from CSV back to TSV.

Is my data secure?

Absolutely. All CSV processing happens locally in your browser. Your files and data never leave your device, ensuring complete privacy for sensitive information like customer data, financial records, or proprietary datasets.