Fix weird characters (é, ’) in a CSV file

Characters such as é, ü or ’ appear when a UTF-8 file is read as if it were in an older Windows encoding. Sometimes the file is fine and only Excel shows it wrong; sometimes the garbled text was saved back into the file. The tool tells the two apart, repairs garbled text and saves a clean UTF-8 file.

Wording and rules verified on

Fixed in your browser – your file never leaves your device.

Files over 50 rows: 1 credit each ($0.75–$1 depending on pack), no subscription · See prices

Several files? Select or drop them together to fix them all at once.

No file handy? Try a broken sample

Sample files with typical import errors, loaded in your browser. Fixing and downloading them is free.

Why it happens

UTF-8 stores é as two bytes. A program that assumes Windows-1252 shows those two bytes as two characters: Ã and ©. Excel does this when you double-click a UTF-8 CSV that has no byte-order mark (BOM).

If you save the file after that, the garbled characters become the real content, and saving it the same way again makes it worse (é turns into é). The opposite also happens: a Windows-1250 or 1252 file read as UTF-8 shows � instead of letters.

  • é → é, è → è, ü → ü, ö → ö, ä → ä
  • ’ → ’, “ → “, – → –
  • ł → Å‚, ś → Å›, ż → ż

How to fix it manually

Excel

  1. Don't double-click the file. Use Data → From Text/CSV, choose "65001: Unicode (UTF-8)" as the file origin and load it.
  2. Save with "CSV UTF-8 (Comma delimited)". Excel then adds a BOM and opens the file correctly next time.

Notepad++

  1. If the text looks right in Notepad++, use Encoding → Convert to UTF-8.
  2. If it already shows é, converting won't help: the bytes themselves are wrong and need repairing.

Before and after

Before
Name,Material
Café crème mug,Öko cotton
After
Name,Material
Café crème mug,Öko cotton

Text that was saved after being read in the wrong encoding, repaired back to the original letters.

Fix it automatically

  • Detects the encoding: UTF-8, UTF-16, Windows-1250, 1251 or 1252, GBK.
  • Repairs text garbled once or twice (é and é).
  • Shows every repaired cell before and after.
  • Saves as UTF-8, with an optional BOM so Excel opens it correctly, or as Windows-1250 if your importer needs it.

Checking and the preview are free. Downloads are free up to 50 rows; a larger file costs 1 credit.

Choose a file

The file is read and repaired inside your browser. Nothing is uploaded: only the row count and the platform are ever sent to us, so supplier prices and customer data stay private.

Frequently asked questions

Why does the file look fine in Google Sheets but not in Excel?

Sheets reads UTF-8 correctly; Excel needs a BOM or the Data → From Text/CSV import. The file itself is fine, so just download it with the BOM switched on.

Can it repair � (a question mark in a diamond)?

No. That character means the original letter was lost: the file was read in the wrong encoding and saved. Go back to the original export.

Is my file uploaded anywhere?

No. The file is read, checked and fixed in your browser. For a paid download only the row count, the platform and a fingerprint of the file (SHA-256) are sent, so you aren't charged twice for the same file.

How much does it cost?

Checking a file and previewing the fixes is free. Downloading the fixed file is free up to 50 rows. A larger file costs 1 credit, and for 24 hours you can download the same file again in another format or encoding at no extra cost. No subscription needed; agencies that fix files every month can choose Pro: 300 files a month for $19.