Use synthetic data, not customer data
Test fixtures should never expose real personal information. These records are invented locally and intended for development, UI demonstrations, database seeding and QA.
01 · Configure
Shape your dataset
02 · Select fields
What should each record contain?
03 · Result
Generated output
Configure fields and generate a dataset.JSON, NDJSON, CSV, TSV or SQL
JSON suits APIs, NDJSON works well for streaming imports, CSV and TSV open in spreadsheets, and SQL creates a multi-row INSERT statement using your safe table name.
Realistic does not mean valid
Generated emails, addresses and identities are fictional and should not be used for verification, identity checks, payments, communication or production analytics.
Fake data generator FAQ
Is the generated data unique?
UUIDs are generated independently, but other random fields may occasionally repeat. Add a UUID field when each row requires a practical unique identifier.
Does this data belong to real people?
No. Values are assembled randomly from local sample pools. Coincidental resemblance is possible, so use them only as test data.
Is anything uploaded?
Dataset generation and exports run in your browser. One usage event is recorded only when you press Generate.