# CSV Opens in One Column? Fix the Delimiter

- Author: FastBankConvert (https://fastbankconvert.com)
- Published: 2026-10-17
- Category: CSV, JSON and text output
- Canonical: https://fastbankconvert.com/blog/csv-opens-in-one-column

> When a CSV opens in one column in Excel: semicolon vs comma delimiters, regional list separators, and importing with the right setting.
When a CSV opens in one column in Excel, the file uses a different delimiter from the one your computer expects. Usually the file has semicolons and Excel looks for commas, or the reverse. Close it without saving, then import it through Data, From Text/CSV, and pick the delimiter the file actually uses in the preview.

## Why does a CSV open in one column in Excel?

A double-clicked CSV is split using your computer's default settings, not by reading the file. If the file's separator differs from the one Excel expects, Excel finds no separators at all and puts each whole line into column A. The data is intact; only the split failed.

[Microsoft's page on importing and exporting text files](https://support.microsoft.com/en-us/office/import-or-export-text-txt-or-csv-files-5250ac4c-663c-47ce-937b-339e391393ba) says that when Excel opens a .csv file, it uses the current default data format settings to interpret each column. There is no preview and no question about the delimiter. The guess is made for you.

You can confirm the cause in ten seconds. Click a cell in column A and look at the formula bar. If you see values with semicolons between them, like `2026-07-01;GROCERY MART;-42,10`, the file is semicolon-separated. If you see commas and the sheet still did not split, your Excel expects semicolons.

### What column A tells you

| What column A shows | Likely cause | Fix |
| --- | --- | --- |
| `date;payee;amount` with semicolons | File uses semicolons, Excel expects commas | Import with Semicolon as delimiter |
| `date,payee,amount` with commas | Excel expects semicolons because of regional settings | Import with Comma as delimiter |
| Values with wide gaps between them | File is tab-separated, saved as .csv | Import with Tab as delimiter |
| Each full line wrapped in quotes | The writer quoted whole lines, not fields | Remove the outer quotes in a text editor, then import |
| One very long line across the whole file | Line endings were lost or are unusual | Open in a text editor and fix the line breaks |
| Odd symbols like `é` along with the split failure | Encoding as well as delimiter is wrong | Import and set the file origin to UTF-8 |

Keep the file closed while you work out which row applies. Saving a CSV that opened in one column can write it back in a changed form.

## Semicolon CSV files and comma CSV files across regions

Semicolon CSV files exist because much of the world writes decimals with a comma. If 42,10 means forty-two and ten cents, a comma cannot also separate fields without quoting every amount. So spreadsheets set to those regions use semicolons as the separator, and their CSV files follow.

That gives two families of "CSV" file that look the same from the outside:

- **Comma family.** Fields separated by commas, decimals written with a point: `-42.10`. Common from US and UK systems.
- **Semicolon family.** Fields separated by semicolons, decimals written with a comma: `-42,10`. Common from systems set up for much of continental Europe and Latin America.

The formal CSV description, [RFC 4180](https://www.rfc-editor.org/rfc/rfc4180), describes comma separation only. Semicolon files are a widespread convention that falls outside it, which is why no program can be sure which family a file belongs to without looking inside.

The decimal mark travels with the separator, and that causes a second problem after the split is fixed. A semicolon file imported on a machine that expects decimal points will turn `-42,10` into text, or into the wrong number. The import steps below cover both settings at once.

Bank exports are a common source of the clash. A bank that serves several countries may write semicolon files for one market and comma files for another. Check the first line of any file whose origin you are unsure of.

## The Windows list separator behind a one-column CSV

On Windows, the character Excel uses to split a double-clicked CSV comes from the regional setting called the list separator. In regions that write decimal commas, the list separator is usually a semicolon. So the same file splits on one computer and lands in one column on a colleague's.

Microsoft's import and export page shows where the setting lives. In Windows 11, search for Region Settings, open the administrative language settings, choose Additional settings on the Formats tab, and look at the List separator box on the Numbers tab. The same page notes that when you save a workbook as CSV, Excel writes the list separator as the delimiter.

That second point explains files that arrive broken from colleagues. Someone in a decimal-comma region saves "CSV" from Excel, and the file has semicolons. It opens correctly on their machine and in one column on yours. Neither copy of Excel is wrong.

Excel's own options interact with this. Under File, Options, Advanced, the Use system separators box controls the decimal and thousands marks. Microsoft's page describes a trick of changing Excel's decimal separator to a comma to force semicolon output when saving. It works, but it changes how every number displays, so use it only if you know why you need it.

## Importing a one-column CSV with From Text/CSV

Import the file instead of opening it, and you choose the delimiter yourself. Open a blank workbook, go to Data, From Text/CSV, and pick the file. Excel shows a preview with a Delimiter box. Set it to the character you saw in column A, check that the columns split, then Load or Transform.

Step by step:

1. Close the one-column file without saving.
2. Open a new, blank workbook.
3. Choose Data, then From Text/CSV, and select the file.
4. In the preview, set **Delimiter** to Semicolon, Comma or Tab to match the file.
5. Set **File Origin** to 65001: Unicode (UTF-8) if names with accents look wrong.
6. If amounts use decimal commas and your machine expects points, choose **Transform Data**, select the amount column, and use Change Type, Using Locale, with a locale that writes decimal commas.
7. Choose **Close & Load**.

Microsoft's page offers an older route as well. Renaming a file from .csv to .txt makes Excel start the Text Import Wizard when you open it, and the wizard asks for the delimiter in its second step. It is a handy shortcut on machines where the legacy wizard is already enabled.

The import also stops the other silent changes that a double-click makes, such as reference numbers losing leading zeros. [Converting a CSV to Excel without changing the data](/blog/convert-csv-to-excel) goes through those column settings in detail.

## Can Text to Columns split a CSV that is already open?

Yes. If the file is already open in one column and you want to keep working, select column A and run Data, Text to Columns. Choose Delimited, tick the separator the file uses, and finish. Each line splits across the columns on the spot, without reopening the file.

[Microsoft's guide to the Convert Text to Columns Wizard](https://support.microsoft.com/en-us/office/split-text-into-different-columns-with-the-convert-text-to-columns-wizard-30b14928-5550-41f5-97ca-7a3e9c363ed7) gives the steps: select the column, choose Delimited, pick the delimiters, check the preview, choose a destination, and finish.

Text to Columns has two weaknesses next to a proper import:

- **Quoted fields.** A payee like `"SMITH; JONES"` in a semicolon file needs the text qualifier set to the double quote, or it splits in two. Check that box in the wizard.
- **Damage already done.** By the time the file is open, Excel may already have changed dates or numbers in column A. If a value looks altered, close the file and import it instead.

After either route, save the result as an Excel workbook, not back over the CSV. That keeps the original file as it was, and [what Excel keeps and drops when it saves as CSV](/blog/excel-save-as-csv) explains why a resaved CSV is rarely the same file.

## When changing the list separator for one CSV is a mistake

Changing the Windows list separator fixes the one file and quietly changes everything else. Microsoft's page warns that the setting is global and affects all applications. Every CSV you save afterwards uses the new separator, formulas may expect a different argument separator, and other programs read lists differently.

Leave the system setting alone when:

- **You only receive the odd file from another region.** Import that file with the right delimiter instead.
- **You share CSV files with others.** Your saved files would stop opening correctly for them.
- **The computer is managed or shared.** Other users and programs depend on the current value.

Change it only when most files you handle come from the other family and you never send CSV files back. Even then, write down the old value so you can restore it.

The same reasoning applies to converted files. A quick conversion is only useful if the output opens the way the next program expects, and [how to weigh speed against accuracy in PDF conversion](/blog/speed-vs-accuracy-in-pdf-conversion) covers checking a result before you rely on it.

## Tabs, stray quotes and other one-column CSV causes

Sometimes the delimiter is right and the file still lands in one column. The usual reasons are a tab-separated file named .csv, quotes wrapped around entire lines, or line breaks the file does not use as expected. A text editor shows each one at a glance.

What to look for:

- **Tabs in a .csv file.** Some exports write tab-separated text and give it a .csv extension. Import with Tab as the delimiter.
- **Whole lines in quotes.** A line like `"2026-07-01,GROCERY MART,-42.10"` is one quoted field to any CSV reader. Strip the outer quotes with find and replace, then import.
- **A title line.** A first line such as `Account statement` with no separators can confuse delimiter detection. Delete it, or start the import at the second row.
- **Missing line breaks.** A file saved with an unusual line ending can appear as one huge row. Open it in an editor that shows line endings and convert them.

FastBankConvert, the statement converter this blog belongs to, is built to offer Excel output beside CSV, and a workbook opens in columns with no delimiter question at all. It is getting ready to open, and [the FastBankConvert homepage](/) shows the formats it will offer.