# Fake Name Generator > Realistic-looking but fully fake person names. Filters for origin, gender, and format — first, last, full. - URL: https://generate.now/name - Category: identity - Price: free, no account required - AI-powered: no - Last updated: 2026-08-27 ## What it does 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. ## When to use it - Seed a database with 100 plausible-looking test users - Mock a comment thread or social feed for a design demo - Generate cast names for a fiction project - Avoid using real customer names in screenshots ## Examples ### 10 × full names, any origin ``` Sara Lin · Diego Ramirez · Aoife Murphy · Yuki Tanaka · ... ``` Recombined first + last names from common-name datasets. ### 5 × Japanese, first only ``` Yuki · Hiro · Sakura · Ren · Aki ``` First names sampled from a Japanese name list. ### 20 × surnames only ``` Okafor · Lindqvist · Nakamura · Varga · Delgado · Mbeki · … ``` Useful when you already have first names and need plausible pairings. ### 10 × full names, Irish ``` Aoife Murphy · Cillian Ó Braonáin · Saoirse Ní Dhomhnaill · … ``` Includes the Ó and Ní prefixes, which trip up name-parsing code. ## 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. ## References - [Personal names around the world](https://www.w3.org/International/questions/qa-personal-names) — W3C. Why fixed first-name/last-name fields break for much of the world's population. - [Falsehoods programmers believe about names](https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/) — Patrick McKenzie. The reference list of assumptions that break real name handling in production systems. ## Related tools - [Username Generator](https://generate.now/username): Themed usernames from a vibe — 'cyberpunk hacker, short', 'cozy gardener', '90s gamer'. AI-generated, length-controlled. - [Fake Address Generator](https://generate.now/address): Plausible postal addresses for test forms and demos. Per-country formats (US, UK, DE, FR, CA, JP, AU). - [Fake Email Generator](https://generate.now/email): Plausible test email addresses for demos, fixtures, and form testing. Bulk generation, never sends.