← Back to Blog

CSV File Won't Open in Excel? 7 Fixes That Work

Excel shows errors, crashes, or displays gibberish when you try to open a CSV file? Here are 7 proven solutions to fix common CSV import issues.

March 19, 20266 min read

Common CSV Import Errors in Excel

  • "File format and extension don't match"
  • All data appears in one column
  • Special characters show as gibberish (encoding issues)
  • Excel freezes or crashes
  • "File too large to open"
  • Numbers stored as text
  • Dates formatted incorrectly

Here's how to fix each one:

Fix 1: Use "Import Data" Instead of Double-Clicking

Double-clicking a CSV file in Windows often causes Excel to guess wrong about delimiters and encoding. Import manually instead:

  1. Open Excel (blank workbook)
  2. Go to Data → Get Data → From File → From Text/CSV
  3. Select your CSV file
  4. Preview the data and adjust settings (delimiter, encoding)
  5. Click Load

This gives you control over how Excel interprets the file instead of relying on auto-detection.

Fix 2: Check the Delimiter (Comma vs Semicolon)

Not all "CSV" files use commas. Some use semicolons, tabs, or pipes (|). If all your data appears in one column, the delimiter is wrong.

How to change delimiter:

  1. Use Data → Get Data → From Text/CSV (method above)
  2. In the preview window, change Delimiter from "Comma" to "Semicolon" or "Tab"
  3. Check if columns appear correctly

Why this happens: European Excel versions often use semicolons because commas are used as decimal separators (e.g., 1,50 instead of 1.50).

Fix 3: Fix Encoding Issues (UTF-8 vs Windows-1252)

If special characters (é, ñ, ü, Chinese/Arabic text) show as �� or random symbols, it's an encoding problem.

Solution:

  1. Import via Data → Get Data → From Text/CSV
  2. In the preview window, change File Origin to:
    • 65001: Unicode (UTF-8) - for most modern files
    • 1252: Western European - for older Windows files
  3. Check if special characters display correctly

If you don't see your encoding, try opening the CSV in Notepad, then Save As → Encoding: UTF-8.

Fix 4: File Is Too Large for Excel

Excel has a hard limit of 1,048,576 rows. If your CSV has more rows, Excel will:

  • Silently truncate data (data loss!)
  • Show "file too large" error
  • Crash or freeze

Solutions:

  • Use a CSV viewer instead (handles multi-million row files)
  • Import into a database (SQLite, PostgreSQL)
  • Split the file into smaller chunks
  • Use Power Query to filter before loading

Fix 5: Numbers Stored as Text

CSV files store everything as text. Excel usually auto-converts numbers, but sometimes fails. Signs:

  • Green triangle in top-left corner of cells
  • SUM() formulas return 0
  • Sorting doesn't work correctly (1, 10, 2 instead of 1, 2, 10)

Quick fix:

  1. Select the column
  2. Click the warning icon that appears
  3. Choose "Convert to Number"

Alternative: Use Power Query's "Transform → Data Type → Whole Number" before loading.

Fix 6: Dates Import Incorrectly

Date formats vary by region. A CSV might have "03/04/2026" which could mean:

  • March 4, 2026 (US format: MM/DD/YYYY)
  • April 3, 2026 (EU format: DD/MM/YYYY)

Fix:

  1. Import via Power Query
  2. Select date column
  3. Transform → Data Type → Date
  4. If still wrong, use Transform → Parse → choose correct format

Fix 7: Use a Different CSV Viewer

If Excel keeps failing, it might not be the right tool. CSV viewers are built specifically for this:

  • Readable CSV - web-based, handles most files instantly
  • Modern CSV - desktop app for huge files
  • Notepad++ - view raw data to debug issues

Viewers won't auto-convert or "fix" data—you see exactly what's in the file, which helps diagnose problems.

Prevention Tips

Before importing CSVs:

  • Open in a text editor first to check delimiter and encoding
  • Check file size (if >50 MB, use a CSV viewer instead)
  • Use Power Query instead of double-clicking
  • Save a backup before making changes

Still Not Working?

If these fixes don't help, the CSV file itself might be corrupted:

  • Re-export from the source system
  • Open in a text editor to check for malformed rows
  • Try a different CSV viewer to confirm Excel is the problem

Skip Excel, Use Readable CSV

No encoding issues, no delimiter guessing, no crashes. Just drop your CSV file and view clean, correctly-formatted data instantly.

Try Readable CSV