Why Does My CSV Open in One Column?

If a CSV opens with every line packed into column A, the file is often fine: the spreadsheet simply did not split each line on the separator that the file actually uses. Confirm the separator before editing anything. If you need to decide whether the file should use commas or semicolons, use the CSV delimiter choice guide.

Nablyx processes one CSV locally in your browser without uploading it, up to 100 MB, and writes cleaned.csv as UTF-8 CSV with the selected output delimiter. The cleaner can rewrite separators while respecting quoted fields, but it cannot fix a genuinely one-field-per-row source or recover malformed data; the first-party cap and streaming evidence is recorded in docs/tool-audit/batch-a.md.

Read the header as plain text

Open the file in a text editor and inspect the first few lines. You are looking for the character that consistently sits between fields.

customer_id;name;city;note
C-21;Riley;Bristol;follow up Friday

If the semicolons are visible in column A after opening the file in a spreadsheet, the reader did not split on semicolons. If you see commas between every field, the same logic applies to commas. Tabs can produce a similar symptom while looking like wide spaces.

Quoted commas inside a field are not evidence that comma is the delimiter. Check several rows and look for the separator that repeats in the same field positions.

Decide whether to fix the import or the file

If this is your own one-off import, fixing the import is usually safest. Choose the actual delimiter in the spreadsheet's import dialog and leave the source file unchanged.

In Excel, use Data › From Text/CSV and select the delimiter shown in the file. In Google Sheets, use File › Import and choose the separator explicitly. This changes how the application reads the CSV; it does not rewrite the CSV.

If the file must be opened repeatedly by other people or by software that cannot be configured, a file-side fix can be more practical: re-save the CSV with the delimiter the receiving system expects, then verify a row that contains punctuation or quoted text.

Nablyx reads the CSV structure before writing the replacement delimiter. That avoids the common failure of a global find-and-replace: punctuation inside a quoted value remains data, while only the separators between fields are rewritten. The cleaner can detect comma, semicolon, tab, or pipe input and lets you choose the output separator separately.

One column can be a different problem

Do not treat every one-column view as a delimiter mismatch.

The diagnostic goal is simple: identify the character that actually separates fields, then make the reader use it. Choosing whether a CSV should use commas or semicolons in general is a separate design decision; it is not necessary to solve this symptom.

If the fields begin shifting after a particular row, diagnose the malformed CSV structure instead of changing the delimiter.

customer_id ; name ; email

1042 ;  Alex  ; alex@example.com
1043 ; Sam ; sam@example.com ;

customer_id,name,email
1042,Alex,alex@example.com
1043,Sam,sam@example.com