Why this happens
Row length mismatches happen whenever the parser sees more or fewer separators than expected on a line. Sometimes that is because a text field contains an unquoted comma. Sometimes a value that should be blank was omitted entirely, collapsing the row from six fields to five. In other cases the real cause is a broken quote in the previous line, which changes how the parser counts the next line.
The root cause matters because “expected 5, found 6” does not always mean the reported row literally contains one extra business value. It only means the parser split the row into six fields. Your job is to determine whether that happened because of delimiter misuse, missing quoting, or an earlier row that left the parser in the wrong state.
A row length mismatch example
This file is supposed to contain four columns per row, but two records break that rule in different ways.
id,name,city,notes 1,Ana,Boston,"Paid in full" 2,Ben,Chicago,Priority, follow up 3,Cam,Denver 4,Dee,Houston,"Renewal due"
Row two contains an extra comma inside unquoted text, creating a fifth field. Row three is missing the fourth field entirely and should include an empty placeholder if the notes value is blank.
What a corrected version looks like
id,name,city,notes 1,Ana,Boston,"Paid in full" 2,Ben,Chicago,"Priority, follow up" 3,Cam,Denver, 4,Dee,Houston,"Renewal due"
The repaired file restores the expected four-column schema without changing the meaning of the data.
Step by step: diagnose and repair
Step 1. Confirm the expected number of columns from the header
Do not start with the bad row. Start with the schema. Count the header fields and inspect a few known-good rows so you know what a normal record looks like.
Step 2. Locate the first mismatched row and compare it with a healthy one
Check whether the suspicious line has an extra delimiter, a missing placeholder cell, or a quote pattern that would change how separators are interpreted.
Step 3. Inspect the row before it if quotes are involved
A missing closing quote on the previous line can make the parser miscount the current line. This is why line numbers in mismatch errors sometimes feel off by one.
Step 4. Repair the row according to intent, not just the count
If a comma belongs inside the text, quote the field. If the value is genuinely empty, add an empty placeholder. Do not simply delete characters until the count matches.
Step 5. Revalidate the whole file
Once the first mismatch is fixed, scan the rest of the file for repeated patterns. Row width problems often come from the same export bug appearing on multiple rows.
How to fix it manually
The manual repair depends on the pattern. Extra fields are usually fixed by quoting text that contains the delimiter or by removing a trailing delimiter that created a phantom blank column. Missing fields are usually fixed by adding an empty placeholder so the row width stays consistent with the header.
Use a plain text editor or validator rather than relying on a spreadsheet grid. A spreadsheet may show four visible cells even when the exported CSV has five delimiters or a broken quote sequence. Raw text makes the true row boundaries easier to reason about.
If the file keeps failing on different rows, broaden the investigation to broken quotes and wrong delimiters. Both issues commonly masquerade as row length mismatches.
How CSVDoctor fixes this automatically
CSVDoctor is built for this exact failure mode. It estimates the expected column count, flags the rows that deviate, and shows how the parser is splitting each suspicious line. That immediately tells you whether the problem is an extra separator, a missing value, or a quote bug spilling into the next row.
Instead of counting commas by hand through a large export, you can isolate the mismatched rows, generate a cleaner file, and retest quickly. Use CSVDoctor to locate row width errors automatically and export a repaired CSV for the next import attempt.
Open CSVDoctor to inspect the CSV in your browser, repair the structural defects, and download a cleaner file for the next import or review.
What not to do
Do not force the row to “fit” by deleting a random comma or adding a random blank cell without understanding the intended data. A row count that matches the header is not enough if you moved the values into the wrong columns. The safe repair always preserves meaning first and column count second.
Related fixes and next checks
If your mismatch came from a quote bug, the dedicated guide on broken quotes shows the repair rules in more detail. If the mismatch only appears in Excel, compare the delimiter behavior with Excel CSV fixes before changing the raw data.
FAQ
What causes “expected 5 columns, found 6”?
Usually an extra delimiter inside unquoted text, but it can also be caused by a quote problem on the same row or the row above it.
How do I represent a blank value in CSV?
Leave the field empty but keep the delimiter position, such as Cam,Denver, when the last column is blank.
Can a trailing comma create a row length mismatch?
Yes. A trailing delimiter can create an extra empty field and push the row over the expected column count.
Why does the parser blame the wrong row sometimes?
Because a broken quote or multiline field on one line can affect how the next line is counted.