Fantasy Names

How to Name a Fantasy Character

Most naming advice tells you to be evocative. That is not a method. This is the one I actually use, in the order I use it.

By Luca Urti · 9 min read · updated

Start with what the name records, not how it sounds

The single most common mistake is choosing a name because it sounds good and then reverse-engineering a justification. It produces names that are decorative and interchangeable, which is why so many fantasy casts read as a list of syllables with jobs attached.

Real names almost always record something. They record a circumstance of birth, a hope, a trade, a place, a parent, a god, a debt, or an insult that stuck. Even names whose meaning has been forgotten had one once, and the forgetting is itself a fact about the culture.

So before you generate anything, answer one question: what does this person's family want recorded? A blacksmith's daughter in a town that has just survived a siege is not named the same way as a courtier's third son in a dynasty that has held power for two centuries. The answer narrows your options enormously, which is the point — an unlimited choice is why naming stalls.

This is why every name on this site ships with a meaning. You are meant to choose the meaning first and take whatever sound comes attached to it, not the other way round.

Say it out loud, three times, at speed

A name that works on the page and collapses in the mouth is a bad name, and you will not find out until session four when everyone at the table has started calling your carefully constructed archmage Bob.

The test is simple and non-negotiable. Say the full name aloud three times in a row, quickly, as if you were interrupting someone. If it degrades into a mumble, if you stumble on the same cluster twice, or if you find yourself instinctively shortening it, the name has failed. Not because it is ugly, but because you will be saying it a hundred times and the version that survives will be the one your mouth prefers, not the one you chose.

This applies to prose too, more than writers expect. Readers subvocalise. A name with an awkward consonant cluster costs the reader a fraction of a second every single time it appears, and across a novel that adds up to a book that feels like harder work than it is.

The corollary: decide the short form yourself. There will be one. If you do not choose it, your table will, and they will choose the funniest option available.

Keep your cast phonetically distinct

Here is a failure I have watched happen at a dozen tables. The GM has four NPCs called Aeliana, Aerith, Alenna and Elandra. Each name is fine. Together they are unusable, because players cannot tell them apart, and a plot that depends on knowing which one betrayed the party is now a plot about a spreadsheet.

Apply two rules to any cast. First, no two significant characters share a first letter. Second, vary the syllable count — if everyone has three syllables, everyone sounds the same regardless of the letters. A cast of Bren, Aeliana, Thornak and Sil is instantly navigable; a cast of Aeliana, Elandra, Ilyana and Aliera is not.

This matters most for the characters your audience must track and least for background colour. A crowded market can be full of similar-sounding names; that is what a real culture sounds like. Your four named suspects cannot be.

A quick audit: write your cast list in a column and read only the first two letters of each name. If you see a repeat among the characters who matter, change one.

Let the name disagree with the character

A name that matches its bearer perfectly is a label. A name that contradicts them is a question.

A gentle healer named for a storm implies a family that expected something else, and a childhood spent being asked about it. A brutal mercenary whose name means "small mercy" implies either a joke or a tragedy, and you get to choose which, later, when it is most useful. Neither costs you a word of exposition; the tension is doing the work.

This is the reason to read the meaning attached to a generated result rather than skimming past it. When you find a name whose meaning is slightly wrong for the character you had in mind, that is usually the best name on the list. Take it and ask why the parents chose it.

Use it sparingly, though. If every name in your setting is ironic, the irony stops registering and you are back to decoration.

Match the naming register to the character's class position

Naming conventions are not evenly distributed within a society. In most real cultures, elaborate names, multiple names, inherited names and formal address are markers of status, and the people at the bottom of a hierarchy frequently have one short name and no surname at all.

You can use this without writing a word about class. Give your aristocracy three-part names with an inherited element, your professionals two-part names, and your labourers one name plus a place or trade. A reader who never consciously notices the pattern will still correctly guess a new character's standing the moment they are introduced.

It also gives you an immediate way to signal social movement. A character who has acquired a second name recently, and uses it slightly too often, has just told you their whole story.

Know when to stop

Naming is a task that expands to fill whatever time you give it, and the returns fall off a cliff after about ninety seconds. A serviceable name chosen quickly and used confidently beats a perfect name that arrived after twenty minutes of deliberation, because the twenty minutes came out of the session.

The working rule I use: generate a batch, pick the first one that does not actively annoy me, and commit. If it turns out to be wrong, I change it between sessions — nobody has ever objected. The cost of changing a name in week two is approximately zero, and the cost of stalling the table is not.

For prose the deadline is different but the principle holds. Name the character, write the scene, and let the name earn or lose its place through use. You will know by chapter three, and by then you will have three chapters.

A checklist you can actually use mid-session

When a player asks the innkeeper's name and you have four seconds, run this: pick a meaning that fits the room, take the name attached to it, check it does not start with the same letter as anyone else present, say it once out loud, and commit.

That is the whole method compressed. Everything above is what you do when you have time; this is what you do when you do not. It produces names that are consistent with your world because the meaning came first, and consistency is most of what makes a setting feel real.

Write it down immediately. The single most common naming failure is not a bad name — it is a good name that the GM cannot remember three weeks later, when a player asks after the innkeeper by name and gets a blank look.

Keep reading