CSVFixLab
Row Width

Find CSV rows with the wrong number of columns

Compare each parsed data row with the header width and locate the rows that can shift or break an import.

Find CSV rows with the wrong number of columns
Use the header as the expected width and list every non-empty row that differs.
Local browser processing
Drop a CSV file hereor choose a file from your device
Auto mode confirms UTF-8 exactly. If the file is not UTF-8, choose its source encoding before downloading a repair.
Analyzing…
—

CSV report

Health score reflects checks on this page; it does not guarantee import acceptance.

—data rows
—columns
—delimiter
—encoding

What a column-count mismatch means

If the header has three fields, each normal data row should also parse into three fields. A row with two or four fields is evidence that something about that record differs from the table structure. The cause can be missing data, an unquoted delimiter inside a value, an extra delimiter, or a quote problem.

Why “just add a comma” is not a repair strategy

The parser can prove that the width is wrong, but it cannot prove which business field is missing. In a row such as A-102,Green Shirt, the absent third field might be price — or the second field might contain a delimiter that was supposed to be quoted. Both possibilities produce different correct files.

A reproducible example

The header defines three columns. One row has two fields and another has four.

Problem CSV
sku,name,price
A-100,Blue Shirt,19.99
A-101,Red Shirt
A-102,Green Shirt,18.00,EXTRA

What the checker can prove from the file

  • The second data row has fewer fields than the header.
  • The third data row has more fields than the header.
  • A quote or delimiter issue can create the same symptom, so nearby parser errors matter.
Safe next action

Return to the source record and determine the intended values and field boundaries for each reported row.

Do not guess

Do not fill missing fields with zero, blank text, the previous row, or another guessed value just to satisfy the expected width.

Reproduce the behavior

Column mismatch lab caseA fixture with both too-few and too-many field examples.

Read the underlying rule

Column count mismatch guide →CSV quoting guide →

A practical debugging order

  1. Read the row number and expected/actual field count.
  2. Check whether the same row or nearby row also has a quote parser error.
  3. Inspect values containing the current delimiter.
  4. Compare the record with the original system, not only the exported CSV.
  5. Correct the source and re-run the checker until the row width is consistent.

What counts as success

A consistent width is necessary for a rectangular CSV table, but it is not sufficient for a successful import. Required values and platform-specific validation still need to be checked separately.