Understanding Issues Opening CSV Files in Excel & How to Resolve Them

📘 Overview

Many users experience problems when opening CSV files in Microsoft Excel. In some cases, Excel does not correctly interpret UTF-8 encoded CSV files, causing characters with accents or symbols to display incorrectly (e.g., Ã, â, €, etc.).

This article explains why this happens, what UTF-8 means, and how you can work around the issue using simple steps—or by exporting the file in an Excel-friendly format.

🔤 What Is UTF-8?

UTF-8 (Unicode Transformation Format – 8-bit) is the most widely used character encoding on the internet.
It supports virtually every character in every language, including:

• Accented letters (é, ü, ñ)

• Non-Latin scripts (Arabic, Chinese, Cyrillic, etc.)

• Special symbols (€, £, —, ©)

Why UTF-8 Matters

When a CSV is encoded in UTF-8, it ensures the text can be displayed properly across different devices and applications—as long as the software reads UTF-8 correctly.

Where Excel Causes Problems

While most modern applications read UTF-8 perfectly, Excel has a known limitation:

• When you double-click to open a UTF-8 CSV, Excel often ignores the UTF-8 BOM (Byte Order Mark).

• As a result, Excel misinterprets the text using Windows-1252 encoding instead—this produces corrupted characters like:

  • é instead of é

  • – instead of —

  • € instead of €

Opening the same file in Notepad or other editors works correctly because those programs respect UTF-8.

⚠️ Common Excel Display Issues

When Excel misreads encoding, users typically see:

• Incorrect characters replacing accented letters

• Random symbols appearing throughout data

• Broken punctuation (e.g., “–” instead of “–”)

• CSV formulas displayed incorrectly

This happens before Excel ever reads the textual data—it’s an encoding interpretation issue.

🛠️ Workaround: Ensure Excel Opens the CSV in UTF-8

If you need to work with UTF-8 CSV files in Excel, here are the easiest fixes.

📝 Method 1: Use Notepad to Force UTF-8 BOM

1. Open the CSV in Notepad.

2. Go to File → Save (or Save As…)

3. Choose UTF-8 encoding if using Save As.

4. Save the file.

5. Open the newly saved CSV in Excel.

Why this works:
Notepad includes a UTF-8 BOM when saving, which Excel recognises—forcing it to use the correct Unicode encoding.

📥 Method 2: Use Excel’s "Import Text" Wizard

This method is more precise but less convenient.

1. Open Excel (blank workbook).

2. Go to Data → Get Data → From Text/CSV.

3. Select your CSV.

4. Excel asks for import options—choose File Origin: UTF-8.

This ensures Excel loads the file using the correct encoding.

💡 Method 3: Export an Excel-friendly CSV (Recommended)

If you're downloading reports from Scheduled Reports, you have two export options:

• Export As CSV → traditional CSV

• Export As Excel CSV → Excel-ready encoding

Choosing Excel CSV saves you time because the file is formatted specifically to avoid encoding issues within Excel.

🧠 Additional Tips

• Avoid opening CSV files by double-clicking—this is when Excel most often misinterprets encoding.

• When generating CSVs programmatically, consider specifying UTF-8 with BOM if the destination users primarily rely on Excel.