Sample CSV Files for Testing

Sample CSV files — sometimes called dummy CSVs or test data files — are placeholder datasets used whenever you need real-looking data without using real records. The most common use cases are testing file import workflows (validating column mapping, type inference, and error handling), seeding databases during development, checking how a spreadsheet application renders different data structures, and providing example fixtures in documentation or API tutorials.

Data engineers use them to test ETL pipelines, QA teams use them in automated import test suites, and developers use them to validate data-processing logic before connecting to production data sources.

All three are character encodings — they define how text characters are stored as bytes on disk. UTF-8 is the modern web standard and handles virtually every language and symbol. It is the correct default for almost all modern tools.

UTF-8 with BOM adds a three-byte marker (EF BB BF) at the start of the file. Some older Windows tools — particularly Microsoft Excel when opening a CSV by double-clicking — require the BOM to correctly identify the encoding and avoid garbling special characters. If your CSV looks correct in a text editor but shows question marks or boxes in Excel, try the BOM variant.

Latin-1 (ISO-8859-1) is a legacy single-byte encoding that covers Western European languages. It cannot represent characters outside that set (no Chinese, Arabic, emoji, etc.). Use it when testing systems that only accept Latin-1 input, or when reproducing a legacy data source that was created with this encoding.

Comma is the default and works with virtually every tool. Use a semicolon when your data contains currency values formatted with commas (common in European locales, where Excel also defaults to semicolons). Use a tab to produce a TSV file, which is standard in bioinformatics and many data science tools; tab-delimited files handle address and description fields without quoting since those fields rarely contain literal tab characters. Use a pipe when your data contains both commas and quotes heavily — it is a common choice for log exports and EDI-adjacent formats.

Open the Custom Generator, choose your dataset type, and set Include Blank Cells to Sparse (around 5% empty fields) or Messy (around 20%). The generator will randomly blank out fields so your import handler has to deal with missing values — useful for checking that your code handles null, empty string, and absent columns gracefully, and that required-field validation fires correctly.

Yes. Every file is generated entirely in your browser using plain JavaScript — no data is sent to any server, no files are stored remotely, and no account is required. All names, emails, addresses, and financial figures are synthetic and randomly generated each time. There is no real personal information, no valid payment card numbers, and no real account credentials — just realistic-looking placeholder data that follows the structural patterns of each dataset type.

RFC 4180 is the informal standard that defines how CSV files should be structured. The key rules it specifies are: fields that contain commas, double-quotes, or line breaks must be enclosed in double-quote characters; a double-quote appearing inside a quoted field must be escaped by preceding it with another double-quote; and each record should end with a CRLF line break. The files generated here follow these rules, which means they will be correctly parsed by any compliant CSV library — including Python's csv module, Node's csv-parse, R's read.csv, and pandas read_csv.

Yes. The By Row Count tab covers the most common sizes: 10, 100, 500, 1,000, 5,000, 10,000, and 50,000 rows. For any other row count, use the Custom Generator and type in any number between 1 and 50,000. The file is built in your browser and downloads immediately — large files (10K+ rows) typically generate in under a second.

Do not double-click the file. Instead, open Excel, go to Data → Get External Data → From Text/CSV (or Get Data → From File → From Text/CSV in newer versions) and use the import wizard to specify the encoding manually. If you need the file to just work on double-click, download the UTF-8 with BOM variant from the Encoding tab — Excel uses the BOM as a signal to apply UTF-8 encoding automatically, which prevents most character corruption issues.