CSV Sample Files for Testing Parsers and Spreadsheet Imports

Good CSV test data needs more than name,email. Real CSV files contain commas inside values, quotes, blank cells, embedded line breaks, non-ASCII characters, odd delimiters and IDs that look numeric but must stay text.

Use these small samples to test parsers, spreadsheet imports, ETL scripts and CSV repair tools.

Basic comma-delimited CSV

id,name,email
1,Ada Lovelace,ada@example.com
2,Grace Hopper,grace@example.com
3,Katherine Johnson,katherine@example.com

Expected result: 3 rows, 3 columns.

Quoted commas

id,name,address
1,Ada Lovelace,"12 Example Street, London"
2,Grace Hopper,"44 Navy Road, Arlington"

Expected result: the address column should not split at the comma inside quotes.

Escaped quotes

id,quote
1,"She said ""hello"" and left."
2,"A quoted field can contain ""double quotes""."

Expected result: doubled quotes become literal quotes inside the value.

Embedded line breaks

id,notes
1,"First line
second line"
2,"Single line"

Expected result: 2 data rows, not 3. A parser that splits only on newline will break this.

Semicolon-delimited CSV

name;country;amount
Ada;France;12,50
Linus;Germany;9,99
Grace;Spain;42,00

Expected result: delimiter is semicolon. This is common in European Excel exports.

Convert it with the semicolon to comma CSV guide or the delimiter converter.

Leading zeros

customer_id,zip_code,total
000123,02108,42.50
000124,94105,19.99

Expected result: customer_id and zip_code should remain text. Excel may turn them into numbers unless you import carefully. See how to keep leading zeros in CSV imports.

UTF-8 characters

name,city,note
Chloe,Montreal,cafe order
Jose,Sao Paulo,naive facade
Miyuki,Tokyo,10 EUR

This sample is ASCII-safe for copying, but real encoding tests should include accented characters and currency symbols from your own source system. If Excel shows café, use the CSV encoding converter.

Blank cells and missing values

id,name,phone,email
1,Ada,,ada@example.com
2,,555-0100,
3,Grace,555-0101,grace@example.com

Expected result: empty fields remain empty fields. They should not shift later columns left.

Inconsistent columns

id,name,email
1,Ada,ada@example.com
2,Grace
3,Katherine,katherine@example.com,extra

Expected result: a strict parser should report row length problems. A repair tool may pad row 2 and flag the extra value in row 3.

Unescaped quote problem

id,notes
1,Ada said "hello" yesterday
2,Grace said "ship it"

Expected result: many parsers tolerate this, but strict CSV requires quotes inside quoted fields to be escaped. Use this to test repair behavior, not as a good export format.

Testing checklist

When testing a CSV tool, verify:

• quoted commas stay in one cell
• escaped quotes are preserved
• embedded newlines do not create fake rows
• blank cells do not shift columns
• non-comma delimiters are detected or configurable
• leading zeros stay as text when needed
• malformed rows are reported clearly

For a broken file, try the CSV repair tool. For a delimiter-only problem, use the comma-delimited converter. For character problems, fix encoding first.