CSV encoding fixer

Repairs broken characters like "José" in a CSV, so names and companies read right again.

CSV or Excel, up to 200,000 rows
Runs in your browser. The file never leaves your device.CSV or Excel, up to 200,000 rows

Next

Email me this report
A short summary of this run: the counts and settings, never your rows. Your file stays in your browser.
The counts from this runThe settings you usedNo file, no rows, no saved link
One email with the report. No sequence, no sales call.
Ken cleans every list you import, then verifies it.
Import once. Ken dedupes, formats and verifies every address, and keeps the flags with each lead.
Start free - 1,000 credits, no card

What the CSV encoding fixer does

It repairs text that was saved in one character encoding and opened in another. "José" becomes José, "Müller" becomes Müller and "don’t" becomes don't. It detects the encoding the file was read in, reverses the damage cell by cell, and saves the result as UTF-8.

The file is repaired in your browser and never uploaded.

How to read the result

The preview shows the cells that changed, before and after. A count tells you how many cells were repaired. Cells with the replacement character, a question mark in a diamond, are left as they are, because the original letter was lost when the file was saved and cannot be recovered from the file.

How to use it

Drop the file, check the preview on a few names you know, and download as UTF-8. To open the result in Excel without breaking it again, import it through Data > From Text/CSV and choose UTF-8 rather than double-clicking it.

For cells with the replacement character, go back to the source and export again as UTF-8.

Why it matters for cold email

A name is the most personal thing in a cold email. "Hi José," tells the reader nobody looked at the list, and it hits hardest on international lists, where accented names are the norm. Sending tools rarely catch it, because to them the broken text is just text.

Questions

Why does my CSV show characters like é, ü and ’?
The file was saved as UTF-8 and opened as Windows-1252 or Latin-1. UTF-8 stores é as two bytes, and the other encoding shows each byte as its own character, so é turns into é. The text is not lost, it is misread, which is why it can be repaired.
How do I open a UTF-8 CSV in Excel without breaking accents?
Use Data > From Text/CSV and pick 65001: Unicode (UTF-8) as the file origin. Or save the file with a UTF-8 byte order mark, and Excel reads it as UTF-8 when you double-click it.
What is a byte order mark?
Three invisible bytes, EF BB BF, at the start of a file that tell programs it is UTF-8. Excel looks for them. Many other tools ignore them, and a few show them as a stray character in the first column name, so add one only when the file is meant for Excel.
Can it fix question marks or the � character?
No. Those mean the character was replaced when the file was saved in an encoding that could not hold it, so the original letter is no longer in the file. The tool leaves those cells as they are, so export again from the source as UTF-8.
What encoding should a CSV use?
UTF-8. It holds every alphabet, and modern CRMs and sending tools expect it on import. RFC 4180, the CSV spec, carries the character set only as a charset parameter on the media type, not inside the file, so the program opening a CSV has to guess. A wrong guess is where broken characters come from.

More in CSV tools

14 tools.