CSV structure & imports · 6 min read

CSV Opens in One Column in Excel? Fix Comma or Semicolon Imports

If a CSV file opens in one column in Excel, the file separator and the import settings may not agree. This guide shows two repairs: import the original file with an explicit delimiter, or split intact text already in column A. The worked example includes a comma inside a description and a semicolon inside quotes, so you can check more than whether columns appeared.

JHSOFT editorialUpdated September 9, 2026

WORKED EXAMPLESynthetic data

sku;description;price
00123;"Mug, blue";12.50
00456;"Plate; small";8.00

Choose semicolon as the delimiter. The result has three columns and two data records. Descriptions remain Mug, blue and Plate; small; IDs remain 00123 and 00456. Numeric prices may display as 12.5 and 8 unless formatted to two decimal places.

Download the sample ↓Open the CSV checker →

Identify the separator in the original file

Open a copy in a plain-text editor and compare the header with two or three records. In this example, semicolons separate sku, description, and price. The comma in Mug, blue belongs to a description. Plate; small also contains a semicolon, but its surrounding quotes keep that punctuation inside one field.

Do not choose a separator simply because it appears most often. A long address or product description can contain more commas than the actual field separators. Look for a choice that produces the intended headers and keeps complete descriptions together.

The semicolon-delimited record becomes sku 00123, description Mug, blue, and price 12.50. — Illustrated example. Synthetic parsing diagram. The comma is part of the description.

Fix 1: Import CSV with the correct delimiter

The following route is for desktop Excel versions with the Text/CSV import command. Menu names can differ by version. Work in a fresh workbook so an unsuccessful preview does not replace a cleaned table.

Choose Data > From Text/CSV, select the original file, and inspect the preview.
Set Delimiter to Semicolon. Confirm that the preview has three fields and that Plate; small stays together.
If Data Type Detection is available, choose the option that does not detect types, then select Transform Data.
In Power Query, keep sku and description as Text. If an automatic Changed Type step already converted sku, remove that step before assigning the intended types.
Convert price to a decimal number using the source convention, then choose Close & Load. Save the working workbook as .xlsx.

Fix 2: Split column A with Text to Columns

Use this route only when each cell still contains one complete record with its punctuation intact. Make a copy first. If a quoted field contains a line break, records have already been split across worksheet rows, or an identifier has changed, use the original-file import instead.

Keep the source column and choose an empty destination with room for all three output columns. Review the preview before accepting it; splitting into occupied cells can replace data.

Select the cells in column A that contain the complete records. Open Data > Text to Columns, select Delimited, and continue.
Clear the other delimiter choices and select Semicolon for this sample. For a comma-separated source, select Comma instead. Keep consecutive delimiters separate when they represent empty fields.
Use the double quote as the text qualifier. Check that the preview keeps Plate; small in one description column rather than making an extra field.
In the final step, select the sku preview column and choose Text. Choose an empty destination such as D1, then finish. Check numeric prices against the source decimal convention.
Verify the two exact IDs and both descriptions. If the preview or output differs from the sample, return to Fix 1 using the untouched file.

Match the repair to the symptom

A delimiter selection solves a boundary problem. If the preview has the right columns but altered values, move on to type or encoding checks. Separating these checks makes it easier to identify which setting produced each change.

What you see	What to inspect	Next action
Everything in one column	Actual separator in raw text	Select that delimiter during import
Descriptions split across columns	Quotes and punctuation	Check the exporter and text qualifier
Columns correct; 00123 became 123	Identifier conversion	Reimport sku as Text
Columns correct; accents damaged	File encoding	Choose the correct file origin
Only some records misalign	Malformed or inconsistent records	Check field counts before loading

Keep punctuation while changing the delimiter

Replacing every semicolon with a comma changes the description Plate; small to Plate, small. That is a content edit, even if the resulting file still opens. If another system requires comma-separated CSV, use a CSV-aware export that reads fields first and then writes the new separator.

The output below is a separate, equivalent comma-delimited representation. Its last description needs no outer quotes because the semicolon is ordinary data under the new delimiter. The first description still needs quotes because it contains a comma.

Equivalent comma-delimited output

sku,description,price
00123,"Mug, blue",12.50
00456,Plate; small,8.00

A delimiter conversion preserves the comma in Mug, blue and the semicolon in Plate; small. — Illustrated example. Synthetic comparison of field values before and after a CSV-aware conversion.

Check the loaded result against the source

Confirm two data records, three columns, and the exact two SKUs. Inspect both descriptions, including punctuation. Compare prices numerically: 12.50 plus 8.00 is 20.50. A total alone is insufficient because a damaged description or missing zero would not change that total.

If the file includes thousands of records, sample the first and last records plus several with quotes or punctuation. Keep the source file alongside the workbook. It gives you a reference if a later refresh changes import settings.

Use the checker as a pre-import inspection

To inspect the downloadable sample in Column Harbor, load or paste its text, select Semicolon in the delimiter control, and run the check. Expect three columns and two data records. A leading-zero warning is expected for the two SKUs; it identifies an import risk rather than a broken file.

The checker inspects UTF-8 text and selected structural or value risks. It does not convert separators, repair records, or change Excel settings. Use its preview to check the field boundaries, then apply the import settings in Excel.

Common questions

Why is Excel not separating a CSV into columns?

A common cause is a delimiter mismatch: the file uses semicolons while the opening workflow expects commas, or the reverse. Inspect the raw header and choose that separator in the import preview. If the whole record is enclosed in one pair of CSV quotes, it may actually represent one field; do not strip every quote without checking the export.

Do I have to change the Windows list separator?

No. For a single CSV, choose its delimiter in the import dialog. A system-wide list-separator change can affect other applications and exports. A file-specific import also makes the setting easier to repeat.

Why did Text to Columns remove leading zeros?

The split column may have been interpreted as numbers. Choose Text for identifier columns before finishing. If a value has already become 123, changing its format afterward cannot tell you whether the original was 00123; return to the original CSV.

Does renaming .csv to .xlsx fix one-column data?

No. A filename extension does not rewrite the file format. Import the delimited text correctly, then save an actual Excel workbook if you need an XLSX file.

Sources & method

Examples and diagrams use synthetic data. Application instructions follow the linked documentation; available menus and options can vary. Our sample checks do not establish behavior in every Excel or Google Sheets version. Read our AI-assisted editorial method.

Browse all field guides →