CSV troubleshooting
Why Is My CSV in One Column? Fix Delimiters and Shifted Data
A CSV usually opens in one column when the importing application expects a different delimiter, such as a comma instead of a semicolon. Data shifts into the wrong columns when delimiters, quotation marks, or line breaks inside a value are not encoded or parsed correctly. Keep the original file, inspect the delimiter and quoting pattern in a plain-text preview, import it using explicit settings, then verify the header count, row count, totals, and sample records before analysis. Do not “fix” a broken import by manually dragging cells into place.
Short answer
A CSV usually opens in one column when the importing application expects a different delimiter, such as a comma instead of a semicolon. Data shifts into the wrong columns when delimiters, quotation marks, or line breaks inside a value are not encoded or parsed correctly. Keep the original file, inspect the delimiter and quoting pattern in a plain-text preview, import it using explicit settings, then verify the header count, row count, totals, and sample records before analysis. Do not “fix” a broken import by manually dragging cells into place.
Upload
Bring the CSV you already use.
Understand
Start with the brief and evidence.
Act
Ask, edit, filter, and export.
Start with the likely cause
If every row appears in one spreadsheet column, the file and the importer probably disagree about the delimiter. If only some rows shift, look for an unquoted delimiter, an unmatched quotation mark, or a line break inside a field. These are parsing problems, not necessarily damaged data. Preserve the source file before changing anything.
Understand what separates CSV fields
“CSV” commonly means comma-separated values, but real exports may use commas, semicolons, tabs, or another delimiter. Regional spreadsheet settings sometimes favor semicolons because commas are used as decimal separators. A plain-text preview can reveal the pattern: ``text orderid;customer;amount 1001;Amina;125.50 `` Importing this file as comma-delimited would put each row into one column.
Distinguish a wrong delimiter from broken quoting
The symptoms point to different causes: Every row is in one column: the selected delimiter is probably wrong. Values shift after one particular field: that field may contain an unquoted delimiter. One record becomes two rows: a line break may exist inside an improperly quoted field. Several records merge together: a quotation mark may be unmatched. Headers look correct but numeric values are wrong: decimal or thousands separators may be interpreted using the wrong locale. Do not assume a character-encoding repair will fix a delimiter problem. Encoding controls how characters are decoded; delimiters and quotes control how fields are separated.
Inspect the raw file safely
Work on a copy and open it in a plain-text viewer that does not immediately split the data into cells. Check: Which character consistently separates the header fields? Are text fields containing that character enclosed in double quotes? Are double quotes inside a quoted value escaped correctly? Does each logical record end on one line, or are multiline fields intentionally quoted? Is the same delimiter used throughout the file? Do not paste sensitive customer or financial records into a public delimiter detector.
Import with explicit settings
Use the spreadsheet or analytics tool’s import flow instead of double-clicking the file. Choose the observed delimiter, confirm the text qualifier, set the expected character encoding, and preview the result before completing the import. If a locale uses decimal commas, do not globally replace commas. A blind replacement can alter legitimate text, amounts, or quoted values.
Validate the repaired import
Before building a dashboard or asking AI to analyze the file, compare the imported result with the source: Header count matches the intended number of fields. Every sampled row aligns under the correct headers. Row count matches the expected number of records. Key identifiers remain intact, including leading zeros. Numeric totals reconcile with a trusted source report. Blank values remain blank rather than becoming zero. Quoted addresses, notes, and product names remain whole. If one record still has a different field count, quarantine it for review instead of silently dropping it.
Export a corrected copy without losing the source
Keep the original file unchanged. Export a new, clearly named UTF-8 CSV only after the import is verified. Record the delimiter and any repair applied so another person can reproduce the result. For recurring exports, fix the source-system export settings or document the import configuration. Repeating manual cell repairs creates an avoidable audit risk.
Analyze only after the table structure is trustworthy
Once headers and rows align, use I.S.A.A.C to inspect the table, build adaptive views, ask questions about available fields, make reviewed light edits, and export a new copy. Do not claim that I.S.A.A.C automatically detects or repairs every delimiter, quote, or multiline-field problem unless those cases have been tested in the current production build.
Concrete examples
Example 1: A semicolon-delimited sales export
Raw file: ``text date;outlet;netsales 2026-07-27;KL-01;2450.00 ` The spreadsheet expects commas, so each line appears in column A. Selecting semicolon as the delimiter produces three fields. The reviewer then confirms that 2450.00` remains a number and reconciles it with the source sales report.
Example 2: A product name contains a comma
Broken row: ``text P-204,Notebook, ruled,12.90 ` If the intended fields are product ID, product name, and price, the name must be quoted: `text P-204,"Notebook, ruled",12.90 `` The quote keeps the comma inside the product-name field. The repair should be based on the export specification or source record, not a guess.
Example 3: A customer note contains a line break
A valid CSV can contain a multiline value when the whole field is correctly quoted. A parser that does not support the file’s quoting rules may treat the second line as a new customer record. Confirm parser support and compare the record count before removing line breaks.
Example 4: Decimal commas and semicolon delimiters
``text item;amount Service A;125,50 `` Here the semicolon separates fields and the comma represents the decimal convention. Replacing every comma with a field separator would corrupt the amount. The import needs both the correct delimiter and the correct numeric locale.
Examples are illustrative and are not customer results.
Common questions
Why does my CSV open in one column?
The importer is probably expecting a different delimiter from the one used in the file. Inspect the raw header, then import the file using the observed comma, semicolon, tab, or other separator.
Why do only some CSV rows shift into the wrong columns?
Those rows may contain an unquoted delimiter, an unmatched quotation mark, or a line break that the parser treats as the end of a record. Compare the affected rows with the source data before repairing them.
Is a semicolon-separated file still a CSV?
Many applications describe delimited text exports as CSV even when they use semicolons. The important step is to identify and consistently apply the actual delimiter.
How should a comma inside a CSV value be stored?
In a comma-delimited file, a value containing a comma should normally be enclosed in double quotes. Embedded double quotes also need the escaping convention expected by the CSV producer and parser. ---
Keep exploring
See what your own CSV is saying.
Try the browser workspace with a real file and keep the public guide open when you need help.
Start free