Invalid CSV Example: Unclosed Quote in a Field
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 a notes field starts with an opening quote — "Requested a callback — that is never closed on the same line. The validator runs the instant the page loads, so the error shown below reflects a real, live check of this exact text.
An unclosed quote is a quieter failure mode than a stray comma: nothing visibly overflows, but the parser is left waiting for a matching closing quote that never arrives on that line, so it flags the field as malformed rather than guessing where it was meant to end. This typically happens when a value is copy-pasted from a source that includes a stray quotation mark, or when a field is truncated mid-export before the closing quote was written.
The result panel below identifies the exact row where the unmatched quote appears. Compare it against the unescaped-comma-csv preset linked here, which shows the other classic CSV failure — a comma that should have been quoted but wasn't, rather than a quote that was opened but never closed.
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.