What this is useful for
Mock data comes up constantly in day-to-day development and QA work: seeding a local database before the real data pipeline exists, populating a UI mockup so a design doesn't look empty, or generating fixtures for automated tests that shouldn't depend on production data. This generator runs entirely in your browser — nothing is sent to a server, so it's safe to use even for schemas that mirror sensitive production fields.
Frequently asked questions
Is the generated data actually realistic, or just random strings?
Names, companies, and job titles are pulled from real-world-style pools (not procedurally garbled text), so they read naturally in a UI or test report. Emails and addresses are constructed from those same names/cities to stay internally consistent within each row.
Does this send my schema or data anywhere?
No. Everything — field selection, generation, and rendering — happens client-side in your browser. Nothing is logged or transmitted, which makes it safe to prototype schemas that resemble real production fields.
Can I generate more than 200 rows?
The cap is set at 200 to keep the page responsive, since generation and rendering both happen in-browser. For larger datasets, generate in batches of 200 and combine them, or use a dedicated seeding library in your test framework for bulk needs.
Why is the UUID not a "real" UUID v4?
The ID field is generated using the browser's cryptographically-random UUID function where available, which does follow the standard UUID v4 format — it's just generated locally rather than fetched from a service.