Add at least one field
All generated data is fictional; any match with a real person, address or account is coincidental. Card numbers are test numbers that pass the Luhn check and cannot be used for payments.
Generates random full names with matching gender, written the way each country does: given name first in the US, Spain, Brazil, France, Germany and Russia (with patronymic-style surnames ending in -ov or -ova), family name first in Japan and Korea. Make up to 10,000 and export them as CSV, JSON or SQL.
How to use
- Start from a template (People, Names, Addresses, Accounts, Payments, Companies) or build your own list of fields.
- Change a field’s type in its menu and rename the column next to it. Number and date fields get min/max or a date range; drag the handle to reorder.
- Set the number of rows (up to 10,000), the data locale and the seed.
- Pick JSON, CSV, SQL, XML or YAML. Switch to Table to check the values; tap a cell to copy it.
- Copy or download the full result. New data (or R) picks a new seed.
- The same seed, fields, locale and row count always give exactly the same output, so you can recreate a dataset later or share it with a teammate. Your fields and settings are saved in this browser.
- Each row is consistent: the email and username come from the row’s name, and the phone area code and postal code match the city. Emails use the reserved example.com, example.net and example.org domains, so nothing can reach a real inbox.
- Phone and postal formats follow each country: US numbers use the fictional 555-01xx range, German postcodes have five digits, Brazilian CEPs are 00000-000, Japanese postcodes 000-0000 and Russian postcodes have six digits.
- Card numbers use the test prefixes that payment sandboxes such as Stripe accept and pass the Luhn check, so they work in checkout forms in test mode. IBANs have valid check digits (and valid national check digits for France, Spain and Portugal). Japan and Russia don’t use IBAN, so those rows get German IBANs unless you pick a country.
- Large datasets are built in small steps so the page stays responsive. The code view shows the first 60 rows and the table the first 100; Copy and Download always include every row. CSV files are saved with a BOM so Excel opens accents and Japanese or Cyrillic text correctly.
- Everything is generated in your browser. Nothing is uploaded.
Realistic but safe
Every row hangs together: the email and username are built from that row’s name, and the phone area code and postal code match the city. Formats follow each country, so German postcodes have five digits, Brazilian CEPs look like 01310-100 and Japanese ones like 100-0001. Emails use the reserved example.com, example.net and example.org domains (RFC 2606) and US phone numbers the fictional 555-01xx range, so a test run can never email or call a real person.
Card numbers start with test prefixes that payment sandboxes accept and pass the Luhn checksum, and IBANs carry valid check digits under ISO 13616, so they get through form validation without belonging to anyone.
Reproducible with a seed
Generation is driven by a seeded random generator. The same seed, fields, locale and row count always produce the identical output, so you can write the seed into a test, rebuild a fixture after changing its format, or send a teammate a seed instead of a file. Press New data or R to roll a new seed.
Choosing a format
JSON suits API mocks and front-end prototypes, CSV opens in Excel or Google Sheets (saved with a UTF-8 BOM so accents and non-Latin scripts display correctly), SQL gives INSERT statements and an optional CREATE TABLE for MySQL, PostgreSQL, SQLite or SQL Server, and XML and YAML cover config-driven test suites. Large sets are built in small steps so the page stays responsive.
Frequently asked questions
Is the generated data real?
No. Names and streets are combined at random from lists, emails point to reserved example domains and phone numbers use fictional ranges where countries provide them. Any match with a real person is a coincidence.
Can I use the card numbers for payments?
No. They pass the Luhn check and use test prefixes, so they work in sandbox or test mode of payment providers, but they are not connected to any account and will be declined for real charges.
How do I get the same data again?
Keep the seed. With the same seed, fields, locale and row count, the generator produces byte-for-byte the same output on any device.
How many rows can I generate?
Up to 10,000 per run. The preview shows the first rows for speed, but Copy and Download always include every row.
Which countries are supported?
United States, Spain, Brazil, France, Germany, Japan, Russia and South Korea, plus a mixed option. Names, addresses, phone numbers and postal codes follow each country’s format.
Is it safe to use for GDPR-compliant testing?
Using synthetic data instead of copies of production data is a common way to keep personal data out of test environments. Everything is generated in your browser and nothing is uploaded.