Realistic mock data, without touching production
Every project hits the same wall: the feature is built but the database is empty, and demos of empty screens convince nobody. Hand-inventing test rows is slow, and copy-pasting production data into dev environments is a privacy incident waiting for its date.
The answer is generated data that looks real: plausible names, emails, addresses, companies, prices and dates in the shape your schema needs. Describe the fields, pick a row count, and export straight to JSON, CSV or SQL INSERT statements.
Open the free Mock Data Generator — no signup, runs entirely in your browser.
How to use it
- Add fields from 20 types across Person, Address, Business and Generic groups.
- Set the row count — up to 1,000 rows per run.
- Export as JSON, CSV or SQL inserts with your own table name.
Why this one
- 20 field types: names, usernames, emails, phones, job titles, addresses, companies, prices, UUIDs, dates and more.
- Three export formats — JSON array, properly quoted CSV, and SQL INSERTs with escaped literals.
- Cryptographically secure randomness — no predictable PRNG sequences.
- Custom SQL table name, validated against injection.
Frequently asked questions
Why not just copy production data into staging?
Because production data contains real people's personal information. GDPR and most privacy regimes treat a staging database leak exactly like a production leak. Realistic fake data carries zero of that risk.
Can I seed a database directly with the output?
Yes — pick SQL export, set your table name, and you get INSERT statements with properly escaped string literals, ready to run against your dev database.
Is the data random enough for load testing?
Values are drawn with crypto.getRandomValues, so there are no repeating PRNG patterns. Note the data is realistic-looking but not relational — foreign-key consistency across tables is on you.