CSV Validator
Find ragged rows, wrong column counts and empty cells in a CSV — 100% in your browser, no upload
🔒 Your CSV is checked entirely in your browser — nothing is uploaded.
Rows that don't match the header
CSV Validator scans your CSV or TSV for rows that do not line up with the header. It parses the file using RFC 4180 rules, so quoted fields containing commas, escaped quotes and line breaks are counted correctly, then compares the column count of every row to the header row. Short rows with missing columns, long rows with extra columns, and blank required cells are all listed with the exact line number so you can jump straight to the problem.
Why ragged rows matter
A single row with the wrong number of columns can break an import, shift every value into the wrong field, or make a database load fail halfway through. Checking a file before you upload it prevents silent data corruption. Everything runs locally in your browser, so even confidential exports never leave your device.
Frequently asked questions
What counts as an invalid row?
A row is flagged when its number of columns does not match the header row, either too few for a short row or too many for a long row, or when it has the right number of columns but one of them is left blank. Each problem is reported with the line number where it occurs.
Does it handle quoted fields with commas and line breaks?
Yes. The parser follows RFC 4180, so a comma or newline inside a double-quoted field is treated as part of the value, not as a new column or row. Escaped double quotes are handled too, and the reported line numbers still point at the real line in your file. A quote RFC 4180 does not allow is reported with its line and character — one inside a value that is not quoted (an inch mark, 27"), a quoted value that starts after a space, or a quote that is never closed — because programs that import CSV read those in different ways.