Why CSV mojibake happens
A CSV file contains bytes, but it usually does not declare how those bytes map to characters. Opening UTF-8 as Windows-1252—or Windows-1252 as UTF-8—creates mojibake. Re-saving the visibly garbled text can make the damage permanent.
Safe repair steps
- Keep an untouched copy of the original file.
- Detect the source encoding before editing text.
- Decode once using that encoding.
- Export as UTF-8 with a byte-order mark when Excel compatibility matters.
- Verify accented names and currency symbols before replacing the source.
What the free tool changes
The repair runs in your browser. It does not upload the CSV. Alongside encoding normalization, it can make headers unique, pad uneven rows, remove exact duplicate records, and neutralize formula-like spreadsheet cells. A downloadable JSON report records the changes.