Sound family first
Names feel coherent when nearby cultures reuse related consonants, vowels, and endings instead of sounding randomly sampled.
Guide
A practical breakdown of how fantasy names stay readable, evocative, and setting-specific.
Definition
Fantasy names work when sound, role, and setting all point in the same direction. The best ones are readable enough to survive dialogue and memorable enough to imply culture, geography, or status without needing a lore dump.
Names feel coherent when nearby cultures reuse related consonants, vowels, and endings instead of sounding randomly sampled.
Heroes, cities, relics, and factions should not all use the same cadence because readers process them differently.
A name people can say and remember will usually outperform a more decorative one.
Patterns
Start with a broad naming lane to hear the setting voice, then split into specialist generators once you know whether the problem is a person, place, artifact, or faction.
Shared roots make capitals, regions, and family lines feel connected without making them identical.
Courtly names can carry more ceremony; frontier names usually work better when they are shorter and easier to say.
Common mistakes
If every noun reads like a jeweled capital, your world loses hierarchy fast.
Near-canon echoes break trust and make the setting feel derivative.
If players or readers stumble on every result, even beautiful lore loses momentum.
Use MythNym
Use the broad-entry naming workspace to establish world voice.
Move here when lineage and race-specific cadence matter.
Use a place-specific page once the naming problem becomes map-facing.
FAQ
Believable fantasy names sound like they belong to one culture, role, and setting logic instead of being random syllables with decorative spelling.
Start broad when you are still hearing out the world voice, then move into specialist pages once the naming lane is clear.
Usually yes, but it should branch into sub-patterns so cities, houses, and relics still feel distinct.