CSV mojibake usually comes from an encoding mismatch. Check UTF-8, legacy encodings, and Excel import behavior before saving over the original file.
Examples are prefilled, and supported operations run in the browser where possible.
Garbled CSV text is often an encoding mismatch rather than a broken file. This tool checks mojibake signals, rows, columns, and creates an Excel-friendly UTF-8 BOM copy.
name,city,note Mina,Seoul,Check whether Korean text breaks in Excel
name,city,note Sato,Tokyo,Check Japanese mojibake
No. It is mainly useful when Excel needs to open a UTF-8 CSV directly.
It checks the text available in the browser. If the source encoding is uncertain, test a small sample first.
The tool runs in the browser where possible, but use headers and a few sample rows for sensitive data.
These are the first rows and columns read with the detected delimiter. Check shifted columns or garbled values before exporting.
| Row | Column 1 | Column 2 | Column 3 |
|---|---|---|---|
| 1 | name | city | note |
| 2 | Mina | Seoul | Korean CSV sample |
| 3 | Sato | Tokyo | Japanese CSV sample |
Check whether the problem is encoding, delimiter/quote structure, or Excel export handling before replacing the original file.
Confirm that pasted CSV text or the selected sample file is available for analysis.
If mojibake appears, compare UTF-8, EUC-KR/CP949, and Shift-JIS candidates.
Use rows, columns, delimiter, and uneven-row signals to separate parsing issues from encoding issues.
For files opened directly in Excel, keep a separate UTF-8 BOM copy.
Parse the detected delimiter again, then save a UTF-8 BOM file that is easier to open in Excel and downstream tools.
Use CRLF for Excel handoff. Choose LF for API uploads or Unix-oriented data pipelines.