CSV import fails or data shifts because some rows have too many or too few columns
Last reviewed 2026-09-19
A CSV needs every row to have the same number of fields. When a text value contains an unquoted comma or a line break, that row splits into extra columns and every value after it shifts sideways. Some importers stop with an error, others quietly load the wrong data.
Messages you might see
- “Expected 5 fields, saw 6”
- “Row has too many columns / data shifted one column to the right”
- “Import stops or mis-aligns at row N”
Why it happens
- A comma or newline inside a text field that was not wrapped in quotes.
- Quotes inside a value that were not escaped by doubling them.
- Rows cut short by a truncated export or a manual edit.
Try this first (free, no tool needed)
- Sort or filter by an obviously numeric column: rows with shifted data show text where a number should be.
- Open the file in a text editor and look at the first row with the wrong count; the cause is usually visible.
- Re-export from the source with the option to quote all text fields, if it has one.
If that didn't work
These tools run in your browser. Your file is read and repaired on your own device and is never uploaded.
Messy CSV Aligner
Fixes CSV exports where some rows have too few or too many columns, the kind of file that makes a spreadsheet import silently corrupt data. Check the result on a few of the rows it changed, since a merged extra column can be a real ambiguity in the source.
Open Messy CSV AlignerCommon questions
Can it always tell where the extra comma belongs?
Not always. When the source is ambiguous, review the rows it reports and compare with the original.
Is my file uploaded anywhere?
No. The tool runs as a program inside your own browser, so the file is read and repaired on your device and never sent to a server.