Random name generator
Generate random first, last, or full names in bulk — handy for test data, characters, and mockups.
Names for testing and mockups
Pick whether you want full names, first names only, or surnames only, optionally lean masculine or feminine, set the quantity, and generate. Copy the whole list with one tap. It's built for the moments you need realistic-looking people without using anyone's real identity — seeding a database, filling a design with believable content, or naming characters.
Why fake names beat "Test User"
Designers and developers reach for placeholder names constantly, and varied realistic ones reveal problems that "Test User 1, Test User 2" hide. Real names differ in length, so they show whether a layout handles a short "Bo Li" and a long "Alexandra Fairweather-Montgomery" gracefully. They make a prototype feel real in a demo, and they populate a test database with data that behaves like the real thing when you sort, search or paginate it.
Made-up, not real people
The names are assembled from common first names and surnames, so any full name you get is a random combination rather than a specific real person — which is exactly what you want for safe, privacy-respecting test data. Generate as many as you need; it all runs in your browser. To round out a realistic test record, pair it with the random number generator for IDs and ages, or the password generator for credentials.
Use fake data, not real people
It is tempting to seed a test database or fill a mockup with names of colleagues, customers or friends. It is also a genuinely bad habit. Real names in non-production systems tend to leak — into screenshots, into shared demo environments, into support tickets and bug reports — and personal data in a test system is still personal data under GDPR and similar regimes.
Generated names sidestep that entirely. Any resemblance to a real person is coincidence, and there is no identity to protect, breach or delete on request.
Why realistic names surface real bugs
Placeholder data that is too tidy hides problems. "Test User" is one word, short, and pure ASCII, so it passes every layout and validation check trivially. Varied names break things in useful ways before your users do:
- Length. Long surnames reveal fixed-width columns, truncation and broken table layouts.
- Punctuation. Apostrophes and hyphens in names like O'Brien and Sainte-Marie expose escaping bugs and over-strict validation.
- Word count. A naive "split on space, take the last part" surname rule fails on names with more than two parts.
- Sorting. A varied list shows immediately whether sorting is by first or last name, and how it handles case.
The broader lesson is that many assumptions programmers make about names are wrong — that everyone has exactly two, that they fit in 32 characters, that they never change. Realistic test data makes those assumptions fail early and cheaply.
Getting a usable set
Set the quantity and copy the whole list in one tap, then paste it into a seed script, a spreadsheet or a design tool. For a database seed, generating a few hundred at once gives enough variety that pagination, search and sorting all get a real workout rather than passing on five rows.
The masculine and feminine options are there for when a mockup needs a specific presentation, but for general test data leaving it unset gives a broader mix — and a mix is usually the more honest test. To turn the results into URL-friendly identifiers, the slug generator converts a name to a clean handle, and the lorem ipsum generator covers the body text that usually goes alongside.