Most worldbuilding advice about names stops at “make it sound consistent.” That is true and almost useless, because consistency is the output, not the method. The practical problem is different: you are three hours into a session, a player has asked the innkeeper’s name, and the six names you already used this evening were Thalendor, Kaelith, Vaeryn, Sylvaris, Aethren and Maelor. They are consistent. They are also indistinguishable, and your table has stopped hearing them.
This is a guide to a naming system rather than a list of names. It is built around one idea: a name’s job is not to sound fantastical, it is to be told apart from the other names in the same scene. Everything below serves that.
Rule 1: names compete with each other, not with reality
A name is never judged alone. It is judged against the other names in earshot. Two NPCs called Maelor and Maelis in the same tavern will merge into one person in your players’ heads by next week, no matter how good each name is in isolation. Before you use a name, run the confusion check: does it share a first syllable, a syllable count and a vowel shape with anyone already in the scene? If yes, change one of the three. That single habit fixes more naming problems than any amount of etymology.
The practical version at the table: keep a running list of every name you have spoken this session. Not a lore document — a scrap of paper. You are not checking for lore consistency, you are checking for collisions.
Rule 2: give every culture a sound budget
Pick three or four sounds a culture uses heavily and two it never uses. That is the whole language design most tables need. Dwarven names lean on hard stops and doubled consonants and refuse soft sibilants; elven names run on liquids and open vowels and refuse hard stops. You can hear the difference between a dwarf name and an elf name before you know what either means, and that is the point — the sound is doing the exposition so you do not have to.
The trick that makes this feel deep rather than arbitrary: apply the budget to place names as well as people. A region whose towns are Grimmsdeep and Karrokgate cannot plausibly produce a hero called Lysavelle unless you intend the mismatch to mean something. When it does mean something — an outsider, a conquered people, an assumed identity — the mismatch becomes the best piece of worldbuilding on the page.
Rule 3: two-part names carry a fact
The most useful naming grammar in fantasy is the compound: one concrete noun plus one action, texture or landscape word. It is why gnome clan names like Bellowsbright and Ratchetbloom work instantly — each one smuggles in a fact about where the family comes from and what they do. The same grammar builds settlements. A town called Saltmarch tells you the sea is near and the ground is bad. A town called Coldharbour tells you a story with an ending.
Worked example. You need a mining village in three seconds. Take a resource word (slate), take a landscape word (hollow), collide them: Slatehollow. The innkeeper is Berrick Slatehollow if he is local, or something completely different if he is not — and now your players know something about him for free. Our town name generator runs this grammar at speed when you need twenty of them, and the city names list shows the same rule at larger scale.
Rule 4: names should tell you how the world is organised
Naming conventions are political. Who has a surname? In most pre-modern settings, not everyone — and the moment a peasant does have one, you have said something about the economy. Are people named for a parent, a patron, a guild, a birthplace, or a debt? Pick one per culture and be strict about it. A kingdom where nobles carry place-names and commoners carry trade-names has a class system that never needs to be explained in dialogue. The kingdom names list is a good place to see how far a naming convention alone can imply a state.
The same logic runs downward. Tavern names are the cheapest culture-building in the game: a district full of The Gilded Hart and The King’s Rest is not the same district as one full of The Broken Oar and The Last Copper, and your players will read the difference without being told.
Rule 5: the say-it-out-loud test beats every other test
Write the name, then say it in an actual sentence of dialogue — not the name alone, the name inside a line someone would speak. “Take it up with Xhal’zerith.” If you hesitate, cut a syllable or an apostrophe. Apostrophes in particular are the most over-used tool in fantasy naming and almost never survive contact with a table; they add no sound, only doubt about where the stress falls.
The corollary: every recurring character needs a short form. Players will invent one whether or not you do, and the one they invent is usually worse. Decide in advance that Thalendor is Thal to his friends, and you have kept control of the name and gained a relationship marker at the same time.
Rule 6: name the thing the party will remember, not the thing that seems important
Prep instinct says to name the duchies, the gods and the ancient war. Play reality says your party will remember the goat. Spend your best names on the things they touch: the tavern they slept in, the guard who let them through, the sword they argued over. A named object is a plot hook that costs one word. An unnamed duchy costs nothing to leave blank until it matters.
A five-minute pre-session routine
- Six spare people. Three short names, three long, no shared first syllables. Genderless enough to reassign on the fly.
- Three spare places. Built with the noun-plus-landscape rule so each one implies terrain.
- Two spare businesses. One respectable, one not.
- One name you love and have not used. Save it for whoever turns out to matter.
- The collision list. A blank line at the top of your notes where every spoken name goes.
That is the entire system. Sound budget, compound grammar, a convention that implies structure, the say-it-aloud test, and a collision check. Everything else — the lists, the generators, the etymology rabbit holes — is fuel for those five habits rather than a substitute for them.
If you want the fuel: the full directory of name generators covers races, places, creatures and organisations, and the OC name ideas post applies the same thinking outside a D&D setting, for original characters in any genre.