CSV Not Opening Correctly in Excel — How to Fix It
You double-click a CSV and Excel puts everything in column A, shows garbled characters instead of accented letters, or turns your product codes into scientific notation. Here are the five most common causes and how to fix each one.
Problem 1: All data in one column
This happens when the file uses a semicolon, tab, or pipe as delimiter but Excel expects commas. It's extremely common with European exports.
Fix in Excel: don't double-click the file. Instead: Data → From Text/CSV → select the file → choose the correct delimiter in the preview.
Fix with CSV First Aid: drop the file, let it auto-detect the delimiter, then download as comma-separated CSV. Excel will open it correctly.
Problem 2: Garbled characters (accented characters show as garbled text)
Excel guesses the encoding when opening a CSV. If it guesses wrong (e.g., reads a Windows-1252 file as UTF-8 or vice versa), you get mojibake.
Fix in Excel: Data → From Text/CSV → File Origin dropdown → select the correct encoding (usually 65001: UTF-8 or 1252: Western European).
Fix with CSV First Aid: the tool auto-detects encoding and converts to UTF-8. Open the fixed file in Excel — it'll work because UTF-8 is the default.
Problem 3: Leading zeros stripped (ZIP codes, product codes)
Excel auto-converts text that looks like numbers. ZIP code 01234 becomes 1234. Long numbers become scientific notation (1.23E+15).
Fix in Excel: import via Text Import Wizard and set the column type to 'Text' instead of 'General'.
Note: CSV First Aid preserves all text as-is (no type conversion). The output CSV contains the original values. The issue is Excel's auto-detection, not the CSV itself.
Problem 4: Dates reformatted incorrectly
Excel converts date-like strings to its internal date format based on your locale. 01/02/2024 might become February 1 in the US or January 2 in Europe.
Fix with CSV First Aid: normalize dates to ISO 8601 (YYYY-MM-DD) before opening in Excel. ISO dates are unambiguous and Excel handles them correctly regardless of locale.
Problem 5: Extra blank rows or shifted columns
If rows appear shifted or blank rows appear, the file likely has quoting issues or inconsistent column counts.
Fix with CSV First Aid: the quote repair + column count normalizer + empty row remover fix all of these structural problems.
Skip the Text Import Wizard. Drop the file into CSV First Aid and get back a CSV Excel opens without fighting you.
Fix your CSV now →Related tools
Fix CSV encoding
Seeing é, ü, ö where you expected é, ü, ö? The file was saved in one encoding and read in another. We figure out which one, then convert to UTF-8 so Müller looks like Müller again.
Strip the UTF-8 BOM from your CSV
First column shows up as 'ID' instead of 'ID'? That's a UTF-8 BOM — three invisible bytes most export tools leave behind. We strip them and the header reads clean again.
CSV delimiter fixer
European exports use semicolons. Database dumps use tabs or pipes. Your import expects commas. We sniff out what the file actually uses and rewrite it to what your tool wants — comma, semicolon, tab, or pipe.
CSV date normalizer
One column with 01/03/2024, 2024-03-01, and 'March 1, 2024' mixed together is a column that can't be sorted. We rewrite everything to YYYY-MM-DD — unambiguous, sortable, safe for every database.