Every seeded database needs people in it, and user_1 through user_500 tells you nothing about how your interface behaves when a name is a single character or forty. This generator draws from common-usage name lists in eight locales and assembles them the way each locale actually orders them — given name first in Europe, family name first in Japan and China.
What you can control
- Choose exactly which columns you get: prefix, first, middle, last, suffix, or an assembled full name.
- Middle names render in full or as an initial, because forms disagree about which they want.
- Locale drives the whole record, so a
ja_JPname arrives as 佐藤 陽菜 and not as a transliteration. - Suffixes appear on roughly a quarter of records — often enough to hit your parser, rarely enough to look real.
What this is not
These are common given names and surnames recombined at random. A generated name occasionally matches a living person by coincidence, the same way two strangers share a name; nothing here is drawn from a real record.
Questions
Are these real people's names?
No. The tool holds lists of common given names and surnames and pairs them at random. There is no underlying person, address or account behind any row.
Can I get the same names again later?
Yes. Every result comes from the seed shown above the output. Keep the seed and you get an identical batch, which is what makes generated fixtures safe to commit next to a test.
Why do Japanese and Chinese names have no space?
Because that is how they are written. Family name comes first and the two parts run together, so a name-splitting routine that assumes a space will fail on them — which is usually worth finding out before production does.