CSV File Opens in One Column in Excel? Here's the Fix

6 min readPipeSheets Team

You double-click a CSV, Excel opens it, and every row's data is jammed into column A as one long comma-filled string. The file isn't broken, your data is fine. Excel is just reading it with the wrong separator. Here's why it happens, how to diagnose which separator your file actually uses, and four ways to fix it — plus how to stop it from happening every single week.

Why Excel Crams Everything Into One Column

When you double-click a CSV, Excel splits columns using the list separator from your operating system's regional settings, not necessarily the comma in the file. In North America that separator is usually a comma, but in many European locales it's a semicolon — because those locales use the comma as the decimal separator (1.234,56 instead of 1,234.56), so the comma can't also separate columns. If the file uses commas and your Excel expects semicolons (or vice versa), Excel never finds a separator it recognizes and dumps the whole row into one cell.

This is why the same file can look fine on a colleague's machine and broken on yours. Nothing about the file changed — your regional settings did the deciding. It also explains the classic symptom pattern: files from US tools (Stripe, Shopify, most SaaS exports) break on European-configured machines, and files from European ERPs or banks break on US-configured machines.

First: Check What Delimiter the File Actually Uses

Before applying a fix, spend ten seconds confirming what you're dealing with. Right-click the file and open it in Notepad, TextEdit, or VS Code. The first two lines tell you everything:

Comma-delimited (standard CSV):
name,email,total
Jane Doe,jane@example.com,42.00

Semicolon-delimited (common from European systems):
name;email;total
Jane Doe;jane@example.com;42,00

Tab-delimited (often exported as .csv anyway):
name	email	total
Jane Doe	jane@example.com	42.00

Whatever character sits between the values is your delimiter. Every fix below asks you to specify it, so knowing it up front saves a round of trial and error. If you see semicolons between values and commas inside the numbers, you have a European-format file — the delimiter and the decimal separator both differ from what a US-configured Excel expects.

Fix 1: Text to Columns (Quickest)

If the file is already open with everything in column A, you can split it in place:

Split column A with Text to Columns:

Click the column A header to select the whole column
Go to Data > Text to Columns
Choose Delimited and click Next
Tick the delimiter your file actually uses (Comma, Semicolon, or Tab) and untick the rest
Check the Data preview pane shows proper columns, then click Finish

Two caveats. First, this is a one-time fix for this one open file — the next export from the same system will open broken again. Second, Text to Columns runs Excel's type detection on every value it splits, which means it can strip leading zeros from ZIP codes and SKUs or reformat dates while it works. If your file contains identifiers or dates you care about, use Fix 2 instead, which lets you mark those columns as Text.

Fix 2: Import With Get Data (Most Reliable)

Instead of double-clicking the file, open a blank workbook and use Data > Get Data > From Text/CSV (on older Excel versions: Data > From Text). Excel shows a preview dialog where you can explicitly set the delimiter and the file's encoding before anything is imported. If the preview shows one column, change the Delimiter dropdown until the columns split correctly, then load.

This route avoids the regional-settings guesswork entirely and is the most dependable method for files from other systems. It also solves two problems at once: the same dialog handles files with the wrong encoding (accented characters showing as garbage), and clicking Transform Data before loading lets you set individual columns to Text so ZIP codes, phone numbers, and SKUs survive intact.

Fix 3: Set the Separator Inside the File

Excel honors a special hint on the first line of a CSV. Open the file in a plain text editor and add a separator declaration as the very first line, above the headers.

sep=,
name,email,total
Jane Doe,jane@example.com,42.00

# Use sep=; if your file is semicolon-delimited

With that line in place, double-clicking the file opens it correctly on any machine, regardless of regional settings. This is a handy trick when you're sending a CSV to colleagues in other countries and can't control their Excel configuration.

Heads up: the sep= line tells Excel how to split columns, but other tools (databases, Mailchimp, QuickBooks) will read it as a literal first data row. Remove it before importing the file anywhere other than Excel.

Fix 4: Change the System List Separator

If every CSV you touch is comma-delimited but your machine is set to a semicolon locale, you can change the setting itself. On Windows, open Control Panel > Region > Additional settings and change the List separator to a comma. On a Mac, Excel follows the decimal separator from System Settings > General > Language & Region — if the decimal separator is a comma, Excel expects semicolon-delimited CSVs.

Use this fix with care: it changes how every application on the machine parses and exports lists, and any local tool that legitimately produces semicolon files will now break in the opposite direction. It's the right fix only when your workflow is consistently comma-based and the locale default is the outlier.

What About Google Sheets?

Google Sheets sidesteps most of this. File > Import > Upload has a Separator type option — leave it on "Detect automatically" and Sheets usually gets commas, semicolons, and tabs right, or set it explicitly if it guesses wrong. If a one-column paste is your problem rather than a one-column file, Data > Split text to columns does the same job as Excel's Text to Columns. Importing into Sheets and re-downloading as CSV is also a quick way to convert a semicolon file to a standard comma file.

Edge Cases That Keep the Problem Coming Back

If the fixes above half-work, check for one of these:

Quoted fields with embedded commas: "Acme, Inc." should stay one cell — make sure you don't also tick Space or ignore the text qualifier, or company names split apart
European decimals colliding with the delimiter: in a comma-split file, 42,00 becomes two cells; the file needs to be semicolon-split (or the decimals converted) first
A .csv that's actually tab-delimited: some systems export tabs with a .csv extension; pick Tab as the delimiter
Mixed delimiters after manual edits: someone pasted semicolon rows into a comma file — normalize one delimiter across the whole file in a text editor before splitting
Encoding weirdness on top: if the split works but accented characters look like Ã©, that's a separate encoding problem, not a delimiter problem

Stop Fixing the Same File Every Week

Text to Columns is fine once. Doing it every Monday on the same export — then re-trimming spaces and re-fixing headers — is a chore worth automating. PipeSheets always exports a standard comma-delimited UTF-8 CSV, the format Excel, Google Sheets, and every import wizard handle cleanly. Run your export through a saved pipeline that trims whitespace, standardizes null placeholders, and normalizes headers, preview the result in your browser to confirm the columns are split correctly, and download a file that just opens right — no delimiter dance required.