Valid CSV Example: Contacts Export
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 small, correctly formatted contacts export: a name, email and phone column across three rows. The validator runs the moment the page loads, so the pass result below is a real, live check of this exact data, not a canned screenshot.
A contacts export like this is one of the most common CSV shapes people work with — pulled from an email client, a CRM or a spreadsheet before importing it somewhere else. Every row here has exactly three comma-separated fields matching the header, which is the single rule that trips up most CSV files: as soon as one row has a different column count than the header, most import tools reject the whole file.
Use this as a reference for what a well-formed CSV looks like, then paste your own export into the textarea to check it the same way. If you want to see how the validator reports a broken file instead, the unescaped-comma and unclosed-quote presets linked below demonstrate two of the most common real-world CSV mistakes.
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.