Why a fake data generator?
Instead of typing "John Smith john@test.com" a hundred times by hand, generate 1 to 1000 rows of realistic names, addresses and numbers in one second.
The data is fake and safe - none of the generated "John Smiths" exists, none of the credit cards will work in a real shop. But they look real, so your app, database or Figma mockup looks normal.
Pick a locale (Polish, US, UK, German) and get matching names, postal codes, phone formats. Pick fields - just name and email, or everything from VAT ID to IBAN. Pick a format - table, CSV, JSON, SQL INSERT, TypeScript objects.
How to use it
- Set how many rows you want - 1 to 1000.
- Pick a locale - this drives names, addresses, phone format, postal code shape.
- Tick the fields you need - first name, email, phone, IBAN, VAT ID, credit card (Luhn-valid), UUID, IP, hex color, lorem text.
- Pick an output format - table to preview, CSV for Excel, JSON for APIs, SQL INSERT for DBs, TypeScript objects for code.
- Optionally type a seed - same seed twice gives identical data (handy for deterministic tests).
- Click "Copy all" or "Download", or copy a single column with the button on the table header.
When this is useful
Typical situations for developers, testers, designers:
- Database seeding - your new project needs 200 users, 50 companies, 1000 orders. Generate SQL INSERT, run on a local DB. No need to write a seed script from scratch.
- E2E tests (Playwright, Cypress) - the login test wants 10 users with different emails. With a seed you get the same data every run - tests stay deterministic.
- Figma mockups - a client asks "what does a list of 50 customers look like?". Paste the generated CSV into the table and it looks like a real database, not "Test 1, Test 2, Test 3".
- App demos - a sales meeting needs a "populated" system. Generate, import, everything looks alive.
- Mock APIs - a frontend dev needs a JSON of 100 users before the backend is ready. Generate, drop into mock API, and ship.
- Load testing - 10 000 rows generated in batches of 1000 hammered into the DB show whether your pagination holds up.
- Employee training - a new hire is learning the CRM. You can't show them real customer data (GDPR). Load generated data instead - looks real, fully legal.
- Anonymisation before sharing a bug report - your production bug screenshot has 5 real surnames. Generate 5 fake ones, swap them in before sending to support.
Related tools: for a custom schema use the test data schema builder, for placeholder text use themed lorem ipsum.
Questions and answers
100% random. First names come from common-name lists per country (e.g. "John Smith" in US), but combinations are randomised. Addresses, phones, IBANs, VAT IDs - all generated on the fly. The odds of any single record matching a real person are vanishingly small.