Mock Data Generator
Build a schema, generate synthetic rows, and download CSV, TSV, JSON, NDJSON, SQL, XML, HTML or Excel. Generate up to 100,000 rows in memory, or 5 million with supported streaming formats and browsers. No sign-up is required.
What This Mock Data Generator Does Differently
Most "random data" sites hand you a column of unrelated values: a first name from one row, an email belonging to somebody else, a postcode from a different country entirely. That is fine until you actually load the file into a staging database and your joins, validators and display logic start behaving in ways real data never would. This generator builds a coherent identity for every row first — person, address, employer — and then fills your columns from it. The email is derived from the name in the same row. The postal code format matches the selected country. Rearranging your columns does not break any of it.
Reproducible output is the headline feature
A seed repeats the pseudo-random sequence for the same schema and settings. Reproducing a file also requires the same date anchor, export format, and generator version; a seed alone is not a cross-browser, all-format byte-identity guarantee. Keep the schema and pinned share link with a fixture, and verify the resulting file when exact bytes matter.
Date-derived fields also depend on a time anchor. Without a restored anchor, a seeded run uses midnight UTC of the current day, so output can change on another day. Copy share link pins that anchor. Explicit date bounds stabilize those fields, but do not fix unrelated format metadata or future implementation changes.
Everything runs in your browser
No account or API key is required. Row generation is local, and CSV, JSON and SQL can work after the required page code has loaded. The first XLSX export requires a network connection to load JSZip from a CDN unless it is already cached; shared page features may also use the network. A share link contains the schema and settings, so avoid real personal information or confidential schema details.
Field types available
- Identity — row number, UUID v4, Mongo-style ObjectId, and prefixed sequential IDs like
EMP-00042with configurable start and padding. - People — first / last / full name, gender, date of birth, age, email, username, local and international phone numbers, avatar URL.
- Locations — street address, city, state or region with its code, postal code, country, country code, full one-line address, latitude, longitude and timezone.
- Internet — domain, URL, slug, IPv4, IPv6, MAC address, user agent, weighted HTTP status codes and MIME types.
- Business — company name, job title, department, product name, product category, SKU, price and currency code.
- Dates and numbers — dates, timestamps, ISO 8601, Unix epoch, times, integers, decimals with configurable precision, booleans in four styles, and percentages.
- Custom — pick from your own comma-separated list, build values from a pattern such as
DEV-@@##-####, or pin a fixed constant.
Output formats and what they are good for
- CSV / TSV — RFC 4180 compliant, with configurable delimiter, optional UTF-8 BOM for Excel, and correct quoting whenever a value contains the delimiter, a quote or a line break.
- JSON — numbers stay numbers, booleans stay booleans and blank cells become
null, so the file loads cleanly into a typed language without a post-processing step. - NDJSON — one object per line, which is what BigQuery, Elasticsearch bulk import and most log pipelines expect.
- SQL — a
CREATE TABLEwith sensible per-column types plus batched multi-rowINSERTstatements, quoted for MySQL, PostgreSQL, SQLite or SQL Server. - XML — configurable root and record element names, with column names coerced into legal XML element names and control characters stripped.
- HTML — a standalone styled table you can open directly or paste into a document.
- Excel (XLSX) — a real spreadsheet with a bold frozen header row, auto-sized columns, and numbers written as genuine numeric cells so
SUMworks without converting anything.
What people use generated datasets for
The presets above exist because the same handful of jobs keep coming up. All of them need plausible rows; if what you actually need is a file of a particular size, use the Sample File Generator instead.
- Power BI and Tableau dashboards — building a report before the real warehouse exists. The Orders preset in XLSX gives you dates, categories, quantities and prices, which is enough to exercise slicers, measures and a date hierarchy.
- Excel practice — learning pivot tables,
VLOOKUP,XLOOKUPor Power Query needs a sheet with enough rows to be interesting. Genuine numeric cells meanSUMandAVERAGEwork without a text-to-columns detour first. - Seeding a development database — the SQL output ships a
CREATE TABLEplus batched inserts for MySQL, PostgreSQL, SQLite or SQL Server, so a fresh environment fills up in one paste. It is also the quickest way to get a table worth practising joins and aggregates against. - Load and performance testing — 100,000 rows in memory, or millions streamed to disk, to find where an importer, a data grid or a missing index actually gives way.
- Demos and screenshots — showing a product without putting a real customer's name and email address in a slide deck.
Why generated CSVs are a security problem (and how this one is not)
Spreadsheet software treats any cell beginning with =, +, - or @ as a formula. A CSV containing =cmd|'/c calc'!A1 can therefore trigger a command prompt when somebody opens it in Excel — the well-documented CSV injection class of attack. Test data ends up in exactly the places where this bites: shared with QA, attached to tickets, imported into admin dashboards. This tool prefixes any such cell with an apostrophe by default, which forces the value to be treated as text and renders it inert. You can disable the guard with the checkbox above when you specifically want to test how your own importer handles those characters.
Generating very large datasets
Up to 100,000 rows the file is assembled in memory and handed to the browser as a normal download. Beyond that, tick Stream straight to disk: the generator writes CSV, TSV, JSON or NDJSON in chunks through the File System Access API and never holds the full dataset in RAM, which is what makes multi-million-row files possible in a tab. Streaming needs a Chromium browser (Chrome, Edge, Opera, Brave or Arc); Safari and Firefox have not shipped the API, and fall back to the in-memory limit.
Limitations worth knowing
- In-memory cap: 100,000 rows. Above this you must stream, or the tab risks running out of memory.
- Streaming cap: 5,000,000 rows, and only for CSV, TSV, JSON and NDJSON. SQL, XML, HTML and XLSX need the whole dataset to build a valid document and cannot be streamed.
- Excel is practical to about 50,000 rows. The format itself allows 1,048,576, but building that much XML in a browser tab is slow — use CSV for very large spreadsheets and let Excel import it.
- Maximum 40 columns.
- Three locales — United States, United Kingdom and India. Names, cities, regions, postcode shapes and phone formats change with the selection; everything is Latin script.
- Card numbers are synthetic. They carry a valid Luhn check digit so payment forms accept them for validation testing, but they are not issued and will always fail real authorization.
- Values are not guaranteed unique. Random fields will repeat across large datasets by design. Use Row number or Prefixed ID when you need a genuine primary key.
- Seeded runs anchor to midnight UTC. Columns with an open-ended date range would otherwise drift with the clock. Share links pin the anchor; explicit To dates avoid the question entirely.
- Avatar URLs point to a third-party placeholder service and are generated as text only — nothing is fetched by this page.
- Dates use UTC throughout, so output does not shift with your local timezone.
Privacy
Rows are generated locally. Share links encode the schema and options in the URL, so review column names, fixed values, and other supplied content before sharing. Synthetic generation does not automatically remove privacy-law obligations, especially if options contain real personal data.
Frequently Asked Questions
SUM and Power Query work straight away. For a Power BI report, 10,000 order rows is usually enough to exercise slicers and a date hierarchy. Above roughly 50,000 rows, switch to CSV and let Excel or Power BI import it — building that much spreadsheet XML in a browser tab gets slow.CREATE TABLE with a sensible type per column followed by batched multi-row INSERT statements. Turn the CREATE TABLE off if the table already exists.=, +, - or @ as a formula, so a leading apostrophe forces it to be read as plain text instead. Uncheck the guard if you are deliberately testing how your own importer handles those characters.SUM and sorting work immediately with no "convert to number" prompt. It opens in Excel, LibreOffice, Google Sheets and Numbers, and is validated in testing against strict OOXML parsers.