Fake Name Generator

Realistic-looking but fully fake person names. Filters for origin, gender, and format — first, last, full.

Origin
Gender
Format
How many
Press Generate

Choose options above and hit Generate.

01 — Overview

How the Fake Name Generator works

Generate plausible first and last names from common name datasets across several cultures. Use for test fixtures, demo seeds, or mock user profiles. Names are recombined from public name-frequency lists; any resemblance to real people is coincidental.

02 — Use cases

When to use the Fake Name Generator

  1. 01

    Seed a database with 100 plausible-looking test users

  2. 02

    Mock a comment thread or social feed for a design demo

  3. 03

    Generate cast names for a fiction project

  4. 04

    Avoid using real customer names in screenshots

03 — Examples

Fake Name Generator examples

10 × full names, any origin

ex 01

Sara Lin · Diego Ramirez · Aoife Murphy · Yuki Tanaka · ...

Recombined first + last names from common-name datasets.

5 × Japanese, first only

ex 02

Yuki · Hiro · Sakura · Ren · Aki

First names sampled from a Japanese name list.

20 × surnames only

ex 03

Okafor · Lindqvist · Nakamura · Varga · Delgado · Mbeki · …

Useful when you already have first names and need plausible pairings.

10 × full names, Irish

ex 04

Aoife Murphy · Cillian Ó Braonáin · Saoirse Ní Dhomhnaill · …

Includes the Ó and Ní prefixes, which trip up name-parsing code.

04 — FAQ

Name — frequently asked questions

Are these real people?

No. First and last names are sampled independently from public name-frequency datasets and recombined randomly. Any match to a real person is coincidence.

Why are some origin lists smaller than others?

The tool uses curated lists of the most common names per origin. Smaller lists may repeat more often in large batches — generate more rounds to vary the output.

Can I get culturally-coherent first+last pairs?

Yes — picking an origin filter draws first and last names from the same list, so the pairing reads consistently. Mixing origins is also fine and reflects real-world demographics.

How should I store names in a database?

One field, called something like full_name, sized generously and accepting Unicode. Splitting into first and last breaks for a large share of the world's population — mononyms, patronymics, multiple surnames, and family-name-first ordering all fail the two-box model. Store what people type and ask separately for a display or sort name if you genuinely need one.

Why shouldn't I use real customer names in screenshots?

Because it's personal data, and screenshots outlive the context they were taken in — they end up in docs, decks, marketing pages, and support tickets. Generated names remove the question entirely, and they let you pick names that demonstrate the edge cases your real data probably doesn't contain.

Can I use these names in published fiction?

Yes. They're recombined from public frequency lists rather than copied from any individual, and names aren't copyrightable in any case. Any resemblance to a specific person is coincidence — worth a sanity check if you're naming a villain.

05 — Reference

Specs and further reading

The primary sources this tool follows. Where behaviour is defined by a specification, we link the specification rather than a summary of it.

07 — More

Tools that pair with Name

Last updated .