Invalid CSV Example: Unescaped Comma Breaks Column Count
Check that every non-empty CSV row has the same number of comma-separated fields as the first row.
🔒 Processed entirely in your browser — nothing you enter here is ever uploaded.
The result appears on this page after you run the tool. Nothing you enter is uploaded.
Result
About this tool
This page opens the CSV validator preloaded with a contacts export where one row has a city value of "Chicago, IL" written without quotes, while an earlier row correctly quotes "Portland, OR". The validator runs on load, so the failure shown below is a live, real check, not a staged screenshot.
This is one of the most common ways real CSV files break: a comma that belongs inside a single field — a city and state, a product description, an address — gets typed without wrapping the whole value in quotes. The parser then reads that comma as a new column separator, so the row ends up with one more column than the header defines, and most import tools either reject the file outright or silently shift every value after it into the wrong column.
The result panel below points to the exact row where the count breaks, which is exactly what makes this bug hard to catch by eye in a large file: everything before it looks fine. The fix is always to wrap the offending field in double quotes, the same way the earlier "Portland, OR" row already does correctly.
Example. name,age followed by Ada,15 passes as Data syntax is valid! Total parsed rows: 2, Columns: 2. A second row of Ada alone fails with Expected 2 columns, found 1, on that line.
Limit. Quotes toggle a mode and are not an RFC 4180 escape. A blank line in the middle counts as a row. The page does not convert the CSV to a table or JSON.