Last Name Generator

Surnames from real census data

The surname pool here comes from US census records — thousands of actual last names ranked by frequency, not invented fantasy strings. That matters when you need names that feel statistically normal: a story set in present-day Ohio should not have everyone called Blackthorne, and a demo database reads truer when the surnames follow real-world distribution.

Use the letter filter to bias results toward a starting letter, or jump to the dedicated A-to-Z pages that list every surname in the pool by initial. Writers doing genealogy-flavored worldbuilding often generate a batch, pick the ones that fit the family, then hard-commit those as canon.

How the generator picks each name

Every click samples from the frequency-ranked census pool, so common surnames like Smith, Johnson, and Garcia appear far more often than rare ones. That is deliberate: it mirrors the real world, where roughly one in a hundred Americans is a Smith. If you need the opposite — unusual names only — filter to rarer initials like Q, X, or Z, or pull from the dedicated rare-surname pages.

Results are drawn independently, so duplicates in a batch are possible but uncommon in the default pool of a few thousand names. For a roster of thirty characters you can expect one or two repeats; regenerate the batch or lock in the names you like and reroll the rest. The generator runs entirely in your browser, which means batches of hundreds of names cost nothing and never send data anywhere.

Common uses for generated surnames

Character surnames are the classic case — minor characters, in-laws mentioned once, classmates on a roster. Test data is the other big one: developers seeding fake user tables need last names that pass a quick eyeball check, and real-frequency surnames do that better than lorem ipsum ever could. Newlyweds brainstorming name changes, RPG players naming dynasties, and teachers building example datasets round out the list.

Pen names and usernames are a quieter use case. A writer publishing under a common surname blends in; one publishing under a rare surname is easier to search for. Both are one click away here. Language learners also use the generator to practice declensions and name forms against realistic inputs instead of textbook placeholders.

Last names by letter, culture, and era

The A-to-Z index pages break the pool down by initial, which is the fastest route when you already know the first letter of the name you want. Some searches are more specific: Japanese surnames, Victorian-era surnames, and old-fashioned surname pages collect names that carry a particular cultural or period flavor. Mixing pools is fine too — a modern setting with immigration in its history can reasonably hold a Nguyen, an Okafor, and a Kowalski in the same town.

Era matters more than people think. A character born in 1890 should not be called a Jayden or a Madison-as-surname; a character born in 2010 can carry almost anything. The census data behind this generator spans decades of records, so the default mix leans modern. For period fiction, start from the era-specific pages and treat the general generator as filler for background names.

Privacy and practical notes

Generated names can coincide with real people, especially common ones. For fiction that is fine — nobody owns the name Smith. For anything that implies a real individual (a testimonial, a demo screenshot shown to clients, a database shipped to a third party), pair the surname with an unusual first name or add a disclaimer, and never attach a generated name to a real address, phone number, or email.

Everything runs locally: no accounts, no stored batches, no rate limits. Close the tab and the names are gone, which makes the tool safe for classroom use and quick to share. If you need names offline, copy a batch into a spreadsheet — the plain-text output pastes cleanly into a single column.

Building a family tree with generated surnames

Genealogy work runs into the same problem as fiction: at some point the records stop and you have to reason backward. A family tree with plausible surnames at every branch lets you test hypotheses, the maiden names of married-in ancestors, whether two lines could plausibly intermarry, how a name might have been anglicized at Ellis Island, without committing to anything. Generate a pool of surnames that match the region and era, pin them to the tree, and swap them out as real records surface.

The frequency data helps here more than you would expect. If your brick-wall ancestor had a top-ten surname, the odds are good that several unrelated families in the same county shared it, which is why searches drown in false positives. Rare surnames are easier to trace precisely because fewer people carried them. Generating from a filtered pool, say surnames starting with a rare letter, mimics that dynamic and is a decent gut-check on how searchable a name will be before you spend a weekend in census scans.

For adopted or blended families constructing a fuller tree for a child, generated surnames can mark unknown branches honestly. A clearly fictional placeholder beats a blank box, because a blank reads as an omission while a placeholder reads as work in progress.

Surnames in games, tabletop and video

Tabletop campaigns burn through NPCs fast. A session can introduce a dozen named characters, and the moment a player latches onto an innkeeper with no surname, that innkeeper needs a family, a history, and possibly a rival. A batch of generated surnames on hand means the innkeeper becomes Ingrid Halvorsen on the spot, and the party assumes she is Scandinavian, whether or not you planned it.

Video game developers use the same trick at scale. Procedurally generated populations, crowd systems, leaderboards, and fake multiplayer lobbies all need name lists that pass a squint test. Real-frequency surnames keep generated crowds from feeling like a keyboard mash. The usual approach: export a few thousand names, deduplicate, weight by frequency if the sim cares about demographics, and hard-exclude profanity strings before shipping.

For persistent online games, add one more step: filter out surnames that match your moderation blocklist, including borderline strings that combine with common first names into something offensive. Every live game learns this lesson the hard way once; generated lists make it repeatable.

Writing believable rosters and directories

A directory page in a novel, a school yearbook, a phone book prop, a company staff list on an about page for a demo site, all of these need many surnames that feel like they belong together. The failure mode is subtle: hand-written lists skew toward famous names and personal acquaintances, so a fictional small town ends up sounding like a writers room. Frequency-ranked generation avoids that bias and produces distributions that look right in aggregate.

The craft move is to generate three batches and use different ones for different social strata. Long-resident families get common regional surnames; newcomers get a broader mix; a single family with an unusual name can anchor a plot point precisely because it stands out against the common ones. Readers notice contrast, not frequency tables, but the contrast only works if the background is statistically normal.

For demo databases and screenshots, the same principle applies with a compliance angle: use generated surnames with clearly fictional first names, and skip real phone numbers and addresses. A realistic-looking directory is a feature; a realistic-looking directory that could be mistaken for a real one is a liability.

What surnames say about language and migration

Surnames are fossils of language. English ones split into predictable strata: patronymics like Johnson and Richardson, trades like Smith, Baker, and Fletcher, places like Hill and Wood, and nicknames like Fox and Little. Once you can read those patterns, a surname list becomes a snapshot of who was in a place and when. The trade names cluster from the medieval period when guilds fixed them; the patronymics froze when parishes started keeping records.

Migration shows up as an overlay. Spanish surnames spread through the US Southwest long before it was the US; Vietnamese and Korean surnames arrived in concentrated waves after the 1970s and show sharp regional spikes; Irish names carry two waves, the famine migrations of the 1840s and the modern tech boom. If your fiction or simulation cares about a specific American region, matching the surname mix to its actual immigration history is the kind of detail readers from that region notice and appreciate.

Anglicization is its own story. Immigration officers did not, as the legend goes, systematically butcher names at Ellis Island, but immigrants themselves often simplified spelling afterward so a schoolteacher could pronounce it. That is why Schwartz became Black in some lines, why there are ten ways to spell a name that was one name in the old country, and why a family tree can legitimately contain both spellings in the same generation. If your story spans a migration, using both spellings at the right generation is the kind of accuracy that makes genealogists put the book down and nod.

Hyphenated, double, and married surnames

Hyphenated surnames answered a naming problem that no single tradition solved: two people who both wanted to keep their names. The convention took off in the 1970s and 80s among professional couples, and it carries class and cultural signals that writers can use deliberately. A character with a hyphenated surname reads as from a family that made a specific choice in a specific decade; a character with two unhyphenated surnames reads as carrying a Latin naming tradition, where the pattern is first surname from one parent, second from the other, and both matter.

Generators mostly produce single surnames because that is what census data counts. To build a hyphenated or double name, generate two and join them, but keep the halves plausible as a pair: two common surnames read one way, a rare plus a common reads another, and two rares reads like a couple of academics. The order people choose, and which name goes first, has no rule but does have consequences for alphabetical sorting in a story directory, which is a genuinely practical concern for a character list you will maintain for a year of drafting.

Married-name plots are the other practical use. A story that needs a maiden-name reveal, a name change at a marriage that signals an identity shift, or two sisters who chose differently at the same wedding, can sketch those options from a generated pool faster than from a baby-names site that only does first names.

Checklist before you commit a name to the page

A short discipline before a generated surname becomes canon: read it aloud in a full sentence of dialogue, because some perfectly good names are awkward to say three times a chapter. Check the initials against the first name, since A. S. S. and F. A. T. are punchlines you did not write. Search the name plus your setting, a common surname plus a real small town can accidentally match an actual prominent family there, which matters for contemporary fiction set in real places.

For games and apps, run the name through your profanity and slur filters in both the name itself and the rendered combination with first names and usernames. For any published work, a quick search for the name plus your genre keeps you from reusing the surname of a famous character in the same genre, which readers will catch even when lawyers would not.

None of these checks take more than a minute per name, and together they are the difference between a generated list that reads as texture and one that reads as filler. The generator gives you statistically plausible raw material; the last mile of plausibility is judgment, and it is worth the minute.

Surnames for villains, heroes, and comedy

Genre fiction leans on surnames harder than literary fiction, and each genre has its own physics. A thriller villain benefits from a common, forgettable surname, the kind that hides in a phone book, because menace works better when it is ordinary. A fantasy villain can carry something stony or thorny, but the real skill is restraint: one hard consonant cluster does the work that three do badly. Comedy inverts everything, a fatally unfortunate surname, ideally real, is a tradition running from Dickens through modern sitcoms, and census data is full of legitimately funny real names to build from.

Heroes get the opposite treatment. A protagonist surname that is easy to say and easy to remember, two syllables, stress on the first, no ambiguous spelling, survives three books. If the series will spawn a fandom, the surname becomes a noun, a ship name, a hashtag, and awkward spellings metastasize into fan arguments about apostrophes. Test the name the way fans will use it: in a username, in a possessive, shouted as a greeting.

For ensembles, contrast is the whole game. A cast where every surname is Anglo-Saxon and one-syllable blurs together no matter how distinct the first names are; a cast with a realistic distribution, a Garcia next to a Nowak next to an Osei, reads like a real place without a word of description. The generator's frequency-weighted output does most of this automatically, which is exactly why frequency data beats name-your-baby lists for fiction.