Sample datasets

a few realistic test files for the tools on this site · updated 19 May 2026

Every tool here works just as well with your own data, but sometimes you just want something to drop in and see what the output looks like. The files below are small, realistic, and cover the obvious edge cases — including one with intentionally stray tabs for testing the validator. Each link saves the file to your machine; nothing is uploaded anywhere when you then drop it into a tool.

Small starter files

ncbi-genes.tsv

Standard biological annotation for human gene variants including genomic coordinates and functional descriptions for genetic research applications.

1.2 KB · 17 rows × 7 columns · download ↓

iso-countries.tsv

Global country reference data containing ISO alpha codes, geographical regions, and current population estimates for internationalization testing.

2.1 KB · 30 rows × 6 columns · download ↓

citi-bike-trips.tsv

Sample trip records from a metropolitan bike sharing system including duration, timestamps, station names, and user categories.

1.8 KB · 20 rows × 7 columns · download ↓

Larger datasets

Bigger TSVs for benchmarking the viewer, conversions, and stats — including one file with intentionally stray tab characters to stress the column-count check.

ncbi-genes-50k.tsv

Fifty thousand gene records with chromosomes, start/end coordinates, strand, and species — a dense numeric TSV in the shape bioinformatics tools emit.

4.3 MB · 50,000 rows × 8 columns · download ↓

citi-bike-trips-100k.tsv

A hundred thousand bike-share trips with start/end stations and timestamps — wide enough to stress the viewer and tabular conversions.

8.5 MB · 100,000 rows × 8 columns · download ↓

events-10k-with-stray-tabs.tsv

Ten thousand event records with ~10% rows containing an extra stray tab in the context column — useful for testing escape handling and column-count validation.

507 KB · 10,000 rows × 6 columns (some malformed) · download ↓

How to use these

Click any card to download the file, then drop it on the input pane of whichever tool fits. The intentionally-broken files are useful for trying the validator — it should report specific line numbers and reasons.

Want one added?

If you have a real-world file you'd love to see as a sample (anonymised, of course), email [email protected] and I'll add it. The smaller and weirder the better — the goal is files that exercise the tools, not pretty demos.

— S., [email protected]