Fantasy Name Generator

Everything about the character is decided: hill dwarf, forge cleric, a tragic apprenticeship, an axe named after her grandmother. The sheet is filled to the last line except the first line — the name. The one you auditioned last night sounded like a dishwasher brand. The one from the novel you love is somebody else's, and everyone at the table knows it. Session is Monday.

The Fantasy Name Generator exists for that first line. Pick a race, pick a gender if you care, tap generate, and you get names built the way fantasy names are actually built — from syllable parts that sound elvish or dwarven or orcish on purpose, not from letters shaken in a bag. Copy the one that fits with a single tap, and get on with the tragic backstory.

This page documents the machine as much as it sells it: the morpheme system underneath, the linguistics that makes an elf name flow and a dwarf name clank, the combinatorics of how many names actually exist in there, and the etiquette of using them in fiction you intend to publish.

Random-letter generators produce noise: Xkzvith reads as a cat walking on a keyboard, not a person. Real fantasy names — the ones readers accept instantly — come from phonology, the sound system of a language. Tolkien built Quenya on Finnish bones and Sindarin on Welsh ones, and every fantasy tradition since has borrowed the insight: a fictional race needs a consistent sound, and names inherit it.

So the generator keeps a bank of syllable morphemes for each race — short word-parts vetted for that race's sound — split into positional slots. An elven name draws a flowing prefix, a vowel-rich connector and a lyrical suffix. A dwarven name draws hard-edged parts that collide into consonant clusters. Assembly is concatenation plus a rules pass, and the rules matter as much as the parts: no three consonants in a row for an elf, no double letters across a join, no name that accidentally ends in a curse word in the six languages we check.

The interface is a row of decisions and a generate button: race, gender, surname on or off, count. Every result can be copied with one tap, batches copy as a list, and nothing you generate is recorded anywhere — names are made fresh on your device every time.

The generator sits above this article. The standard run, for the Monday-morning crowd:

1. 1

   Choose the race

   Elf, dwarf, orc, halfling, human, plus tiefling and dragonborn. Race selects the morpheme bank, which is the single decision that shapes the output most.

2. 2

   Set gender if it matters

   Gender switches the suffix pool where traditions have them — elven -wen and -iel against -ion and -dir, for example. Neutral keeps both pools in play.

3. 3

   Decide on a surname

   Surnames are race-flavored too: dwarven lineage names like Ironfist derivatives, halfling toponymics like Underhill and Burrows, human occupational and patronymic forms.

4. 4

   Generate and audition

   Tap for a batch, read them aloud — auditioning names out loud is not optional, since a name you cannot pronounce will irritate you for a hundred sessions.

5. 5

   Copy the keeper

   One tap copies the winner. Generate again for a spouse, a rival, or the grandmother the axe is named after.

The whole ceremony takes under two minutes, which is roughly the attention span the name field deserves before the backstory starts calling.

Elven names sound the way they do because of open syllables. A syllable ending in a vowel — ae, li, ron — resonates; one ending in a consonant stops. The elven banks favor the resonant kind, heavy in the liquid consonants l and r and the soft fricatives v and th, with vowel-heavy connectors between. The result follows the phonotactics — the permissible-sound-sequence rules — that Tolkien established for Quenya, a language deliberately modeled on Finnish, which is famously vowel-rich and open-syllabled.

An assembly looks like this: the prefix Aer- (noble, bright), the connector -il- and the suffix -wen (maiden) yield Aerilwen — three morphemes, four syllables, every one open, and the stress lands naturally on the second. Swap the connector for -uvi- and you get Aeruviwen; swap the suffix for -las (leaf) and the name goes masculine. The engine is doing concatenation, but the banks are doing linguistics, which is why the output reads as a language rather than as letters.

Dwarven names are the elven system run in reverse: closed syllables, stops like k, t and g, and consonant clusters that land like a hammer. This too comes from a real tradition — Tolkien took the dwarf names in The Hobbit, Gandalf included, from the Dvergatal, the tally of dwarves in the Völuspá poem of the medieval Icelandic Poetic Edda. Durin, Dvalin and Bifur are a thousand years old. The dwarven banks here echo that register — Dur-, Bal-, -grim, -dun — without reusing the actual historical names.

Orcish adds the growl: velar and uvular consonants, z and kh and gr, short vowels, and the apostrophe used as a real phoneme — a glottal stop, the throat-closing consonant that Arabic writes with hamza and Hawaiian with the ʻokina. Ghorzug reads as a name you can bite. The engine caps apostrophes at one per name, a rule earned the hard way: early versions occasionally produced orc names that were more punctuation than orc.

Halfling and human names do different work. Halfling given names are cozy and diminutive — Bilo, Merry, Tessa — and the surnames are toponymic, drawn from landscape features: Underhill, Burrows, Applewood. Human names mix the real-world Germanic, Latinate and Romance patterns, because humans in fantasy are deliberately the familiar reference race: Aldric, Serena, Marlowe. A fantasy world feels believable when its humans have names you could almost find in a phone book and its other races clearly do not.

The surname system copies the way real European family names actually arose, because fantasy readers absorbed those patterns without ever studying them and recognize them instantly. Occupational names — Smith, Fletcher, Weaver — named the family trade. Patronymics — Johnson, Anderson, Svensson — named the father. Toponymics — Hill, Underhill, Brook — named the place. Human surnames in the generator mix all three, so a batch reads like a believable village rather than a random syllable dump.

The other races get their own logic. Dwarven surnames are compound craft-and-material names assembled from morpheme pairs — Stoneforge, Ironbrook, Grimhammer — because dwarven identity is hereditary trade. Elven house names compound nature morphemes into epithets: Mithlas, grey leaf; Aelrindal, roughly silver-song. Halfling toponymics are literal and cozy — Underhill, Burrows, Applewood — a family that named itself after its front yard. Every surname in the deck is generated from race-appropriate parts by the same concatenation engine, so a surname and a given name from the same race never clash phonetically.

The household batch is the quiet GM favorite: generate a family with one shared surname and four distinct given names, and the players meet a household instead of four strangers. Session prep in fifteen seconds, and the names hold together under scrutiny, which is the difference between a village and a lineup.

Generators rarely publish their combination math, which is a shame because the numbers are the fun part. Slot counts times slot counts, per race:

Surnames multiply the space further — roughly 378 elven surname combinations from 21 prefixes and 18 suffixes, comparable for the other races — and gender variants split or merge suffix pools without shrinking the total. Add it up and the engine can assemble more than a quarter million distinct full names. You will meet your favorites long before you exhaust the space, and two players tapping the same race will essentially never draw the same name.

The number that matters more than the total is the quality rate: what fraction of raw combinations survive the join rules and the vetting pass. For the elven bank it is about 94 percent — almost every assembly is usable. The orcish bank runs closer to 88 percent, mostly because glottal-stop placement misfires more often than liquid consonants do. A smaller bank with a high survival rate beats an enormous bank that needs ten taps per keeper, which is the whole design argument in one sentence.

The question every novelist eventually asks: can I put this name in something I sell? Yes. The generator claims no ownership of its output and attaches no license — the names are yours. Two caveats come with the freedom, and both are about collisions. First, the space of short plausible fantasy names is finite and heavily trafficked: a generated Thalor may coincide with a minor character in somebody's 2014 web serial, and no tool on earth can promise otherwise. Second, names that front commercial products — a game title, a book series name — live in trademark territory, and a trademark search is a lawyer's job, not a name generator's.

Canon safety is built in the other direction: the banks cannot produce Tolkien's names or Wizards of the Coast's, because those names are not in the banks. Legolas is unreachable; Aerilwen is not. Players sometimes ask for the real thing — a Drizzt, a Galadriel — and the answer is that famous names are famous precisely because a specific author chose them, and borrowing them puts someone else's character sheet in your game. The generator's whole value is giving you names that feel canon-adjacent without being canon.

Where the generator is deliberately narrow, and where it will disappoint you if you expect otherwise.

• Five core races plus two D&D additions, not infinity. Gothic vampire names, sci-fi alien names and Lovecraftian unpronounceables are different banks for different tools, and pretending one engine covers every genre is how generators end up embarrassing themselves.
• No meaning lookups. The morphemes carry loose meanings internally — grey, leaf, steady — but the generator does not promise that Thalaion means anything in a real or fictional language. If your worldbuilding needs a translation layer, that layer is your notebook.
• Diacritics are a toggle, not a default. Éowyn-style accents are gorgeous in print and annoying in a Zoom game where nobody can type them; the engine adds them only when asked.
• Batches are independent draws, so rare repeats within one batch are mathematically possible and occasionally hilarious. Tap again.
• Cross-race hybrids draw from both banks unevenly — half-elf names lean elven because elven phonology dominates human phonology, not by lore but by sound weight. Purists should generate two names and weld them by hand.

Dungeons and Dragons players are the center of gravity — character creation is a weekly ritual for millions, and the name field is its most procrastinated line. Game masters generate in bulk: a village needs forty names, a dwarven clan needs a lineage, and the tavern keeper needs a name before the players ask for it. The batch mode with copy-as-list exists because a GM with a session in two hours has no time to tap forty times.

Novelists use it more deliberately — a bank of names in the right register, auditioned aloud, then curated by hand into the story's cast. The good ones treat the generator as an auditioning service rather than an oracle: a hundred candidates, five keepers, and the final choice made by a human who knows the character. Indie game developers do the same for NPC rosters, where a hundred villagers need names that all sound like one culture without any of them colliding.

The quieter audience is the naming-curious: worldbuilders who never run a game and never finish a novel but enjoy generating elf names on a lunch break the way other people enjoy crosswords. This is a legitimate use and the generator respects it — there is no wrong way to tap a button.

Three sources for a fantasy name, compared without mercy.

The honest workflow combines all three: generate for raw material, consult lists for inspiration about style, and make the final call yourself. When the campaign needs more than a name — stats, backstory scaffolding, dice — the DnD Character Generator and DnD Dice Roller finish the sheet.

Collected from search queries, session-zero conversations and one memorable email thread about apostrophe ethics.

The generator shares a shelf with the site's other naming tools, and the links below are the ones that actually chain.

• Character Name Generator — contemporary-fiction names when the story leaves the shire for the real world.
• Business Name Generator — for naming the tavern, the shop or the startup your character founds afterward.
• Domain Name Generator — for when the campaign wiki becomes an actual website, as eventually happens.

A privacy note sized to the stakes: a name generator has almost no privacy surface — no essay text, no business address, nothing sensitive in a list of elf syllables — so the honest statement is proportionate. The engine runs entirely in your browser, generated names are not stored, and there is no account to attach them to. Audition a thousand names on a slow afternoon; the only record is your clipboard history.

In short: race-aware morpheme banks, join rules that keep the phonology honest, a quarter-million-name combination space, one-tap copy and batches for GMs — free, instant and running entirely on your device. Choose the race, tap generate, read the candidates aloud, and give your dwarf a name the grandmother-axe can be proud of.