Excel shows é instead of é – here’s the fix

You open a CSV in Excel and see é instead of é? That’s almost always the encoding. There are two fixes: repair the file or import it the right way.

Works with text and these files:

  • CSV
  • TXT
  • JSON
  • XML
  • SRT
  • VTT
  • SMI
  • TSV
  • MD
  • HTML
  • SQL
  • LOG

For example Excel exports, database dumps, subtitles or website code.

Repair

  1. Drop a file or paste text
  2. It gets repaired automatically
  3. Copy or download
or simply drag a file here

Why does Excel show é instead of é?

When you double-click a CSV, Excel reads it with your system’s character table – on most Western Windows systems that’s Windows-1252. If the file is UTF-8 without a BOM, an invisible marker at the start of the file, accented letters are shown incorrectly.

A CSV export from an online shop, opened in Excel with a double-click

Before

Product,Price
Crème brûlée,£4.99
Jalapeño dip,£2.45
Café latte,£3.10

After

Product,Price
Crème brûlée,£4.99
Jalapeño dip,£2.45
Café latte,£3.10

Fix 1: Repair the file and save it with a BOM

  1. Drag the CSV file into the box above.
  2. Keep Save with BOM switched on – it’s preselected for CSV files.
  3. Download the repaired file and open it in Excel with a double-click.

If you already saved the file in Excel while the characters were shown wrong, the error is now part of the file itself. Mojibuster repairs that as well – more on repairing CSV files.

The file never leaves your computer. That matters when it holds customer data – see fixing CRM exports without uploading them.

Fix 2: Import the CSV into Excel correctly

  1. Open a blank workbook and choose Data → From Text/CSV.
  2. Select the CSV file.
  3. Set File Origin to 65001: Unicode (UTF-8).
  4. Check the preview and click Load.

When saving from Excel

In “Save As”, choose CSV UTF-8 (Comma delimited). The plain “CSV (Comma delimited)” format saves in Windows-1252 – other programs then often show accented letters as � (what `?` and `�` mean). CSV files written by scripts need a BOM too: see Python and pandas and PowerShell.

Everything ends up in one column?

If every row lands in column A, the encoding isn’t the problem – the delimiter is. Excel uses the list separator of your regional settings: a comma in the US and UK, a semicolon in most of continental Europe. A CSV exported from a German or French system therefore often splits on semicolons. Import it via Data → From Text/CSV and pick Semicolon as the delimiter; set the encoding to UTF-8 in the same dialog.

Mojibuster deliberately leaves delimiters alone – otherwise a program that expects the file exactly as it is could no longer read it.

Frequently asked questions

Where do I change the character set in Excel?

Double-clicking a CSV never asks – Excel uses the system character set. To choose it, open the file via Data → From Text/CSV and set File Origin to 65001: Unicode (UTF-8). All patterns like é, ö and ü are listed under é instead of é.

Why does this only happen with some CSV files?

It depends on how the file was saved. Excel opens Windows-1252 files and UTF-8 files with a BOM correctly, but not UTF-8 without a BOM.

I already saved the broken file – is it lost?

No. The broken characters are now stored as é in the file, and é can be restored from that. Just drop the file into Mojibuster.

Does this apply to Excel for Mac too?

Yes. Excel for Mac often doesn’t recognize UTF-8 CSV files without a BOM either. So save the repaired file with a BOM.

What is a BOM?

The byte order mark is three invisible bytes at the start of a file. They tell programs like Excel: this file is UTF-8.

Excel shows € instead of € – is that the same error?

Yes. The euro sign takes three bytes in UTF-8, so three wrong characters appear. Mojibuster repairs it just like accented letters. The same goes for “ and ’ – see broken quotes and apostrophes.

More guides