Plainjar
Back to all tools

— text & data —

Live

CSV / Excel fix

Repair broken CSVs with wrong delimiters or encoding.

runs entirely in your browser

Repair a CSV that was saved with the wrong delimiter or character encoding, so it opens back into clean columns.

Drop your file in or paste the text. The tool detects the delimiter and encoding for you, you can override either, and you download a clean CSV or an Excel file.

Your file is processed entirely in your browser and never uploaded. No account needed.

Frequently asked questions

What does this tool actually 'fix'?

Three things: encoding (UTF-8/ANSI/UTF-16 with or without BOM), separator (comma/semicolon/tab/pipe), and line endings (CRLF/LF). Those are the three reasons a CSV from one system doesn't open in another. The content stays the same, only the wrapping gets cleaned up.

Why does my comma CSV open wrong in Excel?

Dutch (and most EU) Excel uses semicolon as the default separator because the comma is the decimal point there. Open an 'international' CSV with commas and Excel treats everything as one column. This tool converts to semicolons + UTF-8 BOM, then it opens correctly straight away.

What's the difference between UTF-8 and UTF-8 with BOM?

BOM = Byte Order Mark, three invisible bytes at the start of the file (EF BB BF). For modern tools (Google Sheets, Python, Node) it makes no difference. For NL/EU Excel it does: without BOM Excel guesses CP1252 and é/ü/€ break. Default: leave it on unless your tooling specifically dislikes it.

Is my CSV uploaded anywhere?

No. Everything runs in your browser, encoding detection, parsing, and writing the new CSV or XLSX. No byte goes to our server. The XLSX library is loaded once from the jsDelivr CDN (small, ~75 KB) and then used locally.

— related tools —

Related tools

Text processing happens entirely in your browser. What you paste stays on your device.

CSV / Excel fix — Plainjar