A CSV opens in one column in Excel when the file's separator does not match the list separator in your computer's regional settings. A comma-separated file opened on a system that expects semicolons puts every row into column A. You can fix it by importing the file with the right delimiter or by converting it to XLSX first.
The same mismatch between what the CSV contains and what Excel assumes causes four other common problems. This guide explains each one and gives you the quickest fix.
On this page
Key takeaways
- One-column CSVs are a delimiter problem: Excel uses your regional list separator, often a semicolon in Europe.
- Leading zeros and long numbers are lost because Excel reads them as numbers and keeps only 15 significant digits.
- Garbled accents such as é mean a UTF-8 file was read with the wrong encoding.
- Converting the CSV to XLSX first avoids all five problems in one step.
Steps shown in the video
- Click Choose CSV Files and select your CSV
- Your file is listed with its size
- Click Convert to Excel to create the workbook
- Download your .xlsx file
Find your CSV problem at a glance
| What you see | Cause | Quick fix |
|---|---|---|
| All data in column A | Delimiter does not match your regional list separator | Import with Data, From Text/CSV, or convert to XLSX |
| 02134 shows as 2134 | Excel reads codes as numbers | Import the column as Text, or convert to XLSX |
| 4111111111111111 shows as 4.11111E+15 | Excel stores 15 significant digits | Keep the column as Text |
| é instead of é | UTF-8 file read as another encoding | Import with UTF-8 (65001) selected |
| 1-2 becomes 2-Jan | Excel turns date-like text into dates | Import the column as Text |
Why does my CSV open in a single column?
Excel splits a CSV using the list separator defined in your operating system's regional settings. In the United States that separator is a comma. In much of Europe, where the comma is the decimal mark, it is a semicolon. When the file and the setting disagree, Excel finds no separators and leaves each line in one cell.
Fix it in Excel
- Open a blank workbook and go to Data, then From Text/CSV.
- Select your file. Excel shows a preview.
- Choose the correct Delimiter (comma, semicolon or tab) and click Load.
Fix it without Excel's import dialog
The CSV to Excel converter detects the delimiter from the file itself, so the same CSV produces the same columns on every computer, whatever its regional settings.
Why did Excel remove my leading zeros?
Excel treats 02134 as the number 2134, because numbers do not have leading zeros. ZIP codes, employee IDs, phone numbers and product codes all suffer from this. Once the file is saved again, the zeros are gone for good.
To keep them, import the file with Data, then From Text/CSV, choose Transform Data and set the column type to Text. Or convert the CSV to XLSX first: the converter keeps any value with a leading zero as text automatically.
Why do long numbers turn into 1.23E+15?
Excel stores numbers with 15 significant digits, a limit Microsoft lists in its Excel specifications and limits. A 16-digit card number or a 20-digit tracking code is rounded and shown in scientific notation. Changing the cell format afterwards does not bring the lost digits back.
Treat these values as text, not numbers. The converter does this for any value longer than 15 digits, so every digit survives.
Why are accents and symbols garbled?
Text such as é instead of é, or € instead of €, means the file was saved as UTF-8 but opened as an older encoding such as Windows-1252. Many systems export UTF-8 without the byte-order mark that tells Excel which encoding to use.
In the From Text/CSV dialog, set File Origin to 65001: Unicode (UTF-8). The converter reads files as UTF-8 by default, so names like Zoë or São Paulo come through correctly.
Why did some values turn into dates?
Excel converts anything that looks like a date. Sizes such as 1-2, fractions such as 3/4 and codes such as MAR1 can all become dates. The problem was common enough that the scientific committee that names human genes renamed several genes, such as MARCH1, to stop Excel from converting them.
Import the affected columns as Text, or convert to XLSX first. The converter leaves dates and date-like text exactly as written.
The one-step fix for all five problems
Each problem comes from Excel guessing while it opens the file. Converting the CSV into an XLSX workbook removes the guessing: the delimiter is detected from the file, and only safe values are turned into numbers. For a walkthrough, see how to convert CSV to Excel, and to decide which format to keep, read CSV vs XLSX.
CSV problems in Excel: FAQ
How do I stop Excel putting all CSV data in one column?
Import the file with Data, then From Text/CSV, and choose the correct delimiter. Or convert the CSV to XLSX with a tool that detects the delimiter automatically.
How do I open a CSV in Excel without losing leading zeros?
Import the column as Text in the From Text/CSV dialog, or convert the CSV to XLSX first with a converter that keeps zero-padded values as text.
Why does Excel show my number as 1.23E+15?
Excel keeps only 15 significant digits and shows long numbers in scientific notation. Store values such as card or tracking numbers as text.
Why do I see é instead of é in my CSV?
The file is UTF-8 but Excel read it with a different encoding. Choose 65001: Unicode (UTF-8) as the File Origin when importing.
Can I add a line to the CSV to tell Excel the delimiter?
Yes. Excel recognises a first line of sep=, (or sep=; for semicolons). Other programs will treat that line as data, so remove it before using the file elsewhere.
Stop Excel from guessing
Every one of these problems starts with Excel interpreting a plain text file. Import with explicit settings when you need to, or convert the CSV to XLSX once and share a workbook that opens correctly everywhere.
