FileExamples
CSV.csv · Invalid

Invalid CSV File

Download a free invalid CSV file containing common structural problems found in real-world CSV data. Includes inconsistent column counts, unescaped quotes within fields, mixed delimiters (commas and semicolons), missing headers, and fields with unescaped newlines. Use it to test how your CSV parser, data pipeline, or spreadsheet application handles malformed tabular data.

What Is Broken

Multiple CSV format violations: rows with different column counts, double quotes not properly escaped (" vs ""), mixed delimiters within the same file, a BOM (byte order mark) in a non-UTF-8 context, and fields containing raw newlines without proper quoting.

Broken Example

name,email,age,city
Alice,alice@example.com,29,New York
Bob,bob@example.com,34
Carol,"carol@example.com,41,"San Francisco"
Dave;"dave@example.com";28;"London"
Eve,eve@"example".com,33,Berlin

Why It Matters

CSV is the most common data exchange format, yet there is no single standard — RFC 4180 is a guideline, not universally followed. Real-world CSV files from Excel, Google Sheets, legacy systems, and manual exports frequently contain these issues.

Expected Parser / Validator Behavior

Robust CSV parsers should detect inconsistent column counts and either skip or flag problematic rows. Quote-aware parsers should handle escaped quotes correctly. Most parsers should report warnings for structural issues rather than silently corrupting data.

Related Validators & Tools

Frequently Asked Questions

What CSV errors does this file contain?

Inconsistent column counts, unescaped quotes, mixed delimiters (comma and semicolon), and fields with quotes in unexpected positions.

Is there a CSV standard?

RFC 4180 defines a common format, but many real-world tools produce non-compliant CSV. Testing with broken files ensures your parser handles real-world data.