How to Name a Fantasy Character (and Whole Races)

A fantasy name carries a "texture" independent of its meaning — soft consonants read as graceful, hard consonants read as harsh. This guide covers choosing a phonetic register on purpose, why a stray apostrophe usually signals under-designed naming, matching a name's style to who's doing the naming in-story, and building a whole race's names as one consistent system.

"Sounds cool" is where most fantasy naming advice stops. It's not enough — a name also has to be sayable, memorable, and consistent with everything else in your world. Here's how to actually build one, and how to build a whole race's worth at once.

By Rodrigo Chame — independent creator, builder of Nameryn's worldbuilding name engine. Published July 13, 2026.

Every name has a phonetic register — decide yours on purpose

Say a name out loud and it carries a "texture" independent of what it means: soft liquid consonants (l, m, n, r, v) and open vowels read as graceful or ethereal. Hard stops and guttural clusters (k, g, kh, gr-, dr-, thr-) read as harsh, ancient, or threatening. This isn't a coincidence or a cliché to avoid — it's how human ears actually parse unfamiliar words. The effect is well documented in linguistics as sound symbolism, most famously the "bouba/kiki" effect, where people across cultures and languages consistently match certain sounds to round shapes and others to spiky ones — and every well-built fantasy language leans on the same effect deliberately. The mistake isn't using a register. It's not deciding which one you're using, so your "elegant forest elder" ends up with the same consonant clusters as your "swamp-dwelling brute," and readers lose a free signal you could have given them for nothing.

Pick a register per culture, not per character. A whole people should share a recognizable sound, the way real-world naming traditions do — you can tell a lot about where a name comes from before you know what it means.

The apostrophe trap

An apostrophe dropped into a name to make it "look more fantasy" is the single most common tell of an under-designed conlang. In real (and well-constructed fictional) languages, an apostrophe marks something specific — a glottal stop, a dropped syllable, a boundary between two root words that would otherwise blur together. If you can't say what your apostrophe represents, cut it. A name doesn't get more exotic by adding punctuation; it gets harder to type, harder to say, and — paradoxically — more generic, because "name with a random apostrophe in it" is its own overused pattern at this point, not a mark of originality.

Say it in your head, not just out loud

Most readers never voice character names — they subvocalize a rough shape and move on. That changes the bar: a name can be technically pronounceable and still fail if it takes real effort to parse silently on the page. Long unbroken consonant runs, three vowels stacked in a row, or a string that could plausibly be misread as three different words are all things a reader has to stop and solve, even silently, and every one of those stops is friction between them and your story. Read your shortlist as if you're skimming, not performing it — that's closer to how it'll actually be encountered.

Match the name to who's doing the naming

A name should reflect its origin, not just its vibe. A farmhand raised in a small village and a court-born mage-noble should not sound like they were named by the same convention, even if they're the same species — one was named by parents using everyday, grounded words, the other inherited a name built for prestige and lineage. This is a cheap, high-value trick: it lets readers infer a character's background from their name alone, before a single line of exposition, the same way a reader instinctively reads something about a real person from whether they go by "Rob" or "Robert Alistair Whitfield III."

Build a race's names as a system, not a pile of one-offs

The difference between a fantasy race that feels designed and one that feels like a grab-bag of "cool names I thought of" is almost always structural, not aesthetic. Pick 2–3 recurring building blocks — a handful of characteristic openings, a handful of characteristic endings — and construct every name in that culture from the same small kit. This does two things at once: it makes the names memorable as a set (readers start recognizing "oh, that's an X name" the same way they recognize a real-world naming pattern), and it makes it much easier for you to generate consistent new names later without breaking the pattern by accident.

This is exactly the approach behind Nameryn's fantasy name generator — lyrical, forest, ancient, high-fantasy, and dark are each built from their own small, consistent syllable kit rather than one giant shared word list, and the dedicated elf, DnD, dragon, demon, vampire, and witch generators each get their own register for the same reason. If you're naming a whole race yourself, that's the move: build the kit first, then generate from it, rather than inventing each name from scratch and hoping they end up feeling related.

A quick pre-flight checklist

  • Does this name's texture match the character's culture and role, not just "sound fantasy" in general?
  • Can a reader parse it silently on the page without stumbling?
  • If there's an apostrophe or unusual spelling, do you know what it represents?
  • Does it share a recognizable building block with other names from the same culture, or does it feel like it wandered in from somewhere else?
  • Say it out loud once, to yourself, cold — does the stress land somewhere natural, or do you have to think about how to say it?

Related