Fix inconsistent CSV column counts
Header says 5 columns, some rows have 4, one row has 7 — and your import tool gives up. We pad the short rows, flag the over-long ones, and tell you exactly which line numbers to look at.
Columns aligned
Before
A,B 1,2,3 4
After
A,B 1,2 4,
Drop your CSV file here
or click to browse
The "column count" fix will be auto-detected.
What is this and why does it matter?
A proper CSV file should have the same number of columns in every row. But real-world files often have rows with missing values at the end, or rows with extra data that shifts everything over. This causes imports to fail and data to land in the wrong columns.
CSV First Aid figures out how many columns your file should have by looking at the most common row length. Rows that are too short get filled in with empty cells; rows that are too long are flagged for your review.
This fix runs after other corrections, so the column count reflects the actual shape of your cleaned data.
How it works
- 1Drop your CSV. We count the columns in every row to find inconsistencies.
- 2Rows with too few or too many columns are flagged with their position.
- 3Apply → short rows are filled in, and every row has the same number of columns. Download.
FAQ
How is the 'expected' column count determined?
It's the mode (most frequent value) of all row lengths. If 95% of rows have 10 columns and 5% have 9, the expected count is 10.
What happens to rows with too many columns?
Extra columns are preserved (not truncated) to avoid data loss. They're flagged in the fix report so you can review them.
My header has more columns than data rows. What happens?
If the header row is the widest, it becomes the expected count and shorter data rows are padded to match. This is a common pattern when optional trailing columns exist.