How to Name a Fantasy Kingdom, Town or Tavern
Real places are named after rivers, hills, trades and forgotten founders. Borrow that logic and your fantasy map will feel old, lived-in and consistent.
Most fantasy maps fail the same way: every place sounds equally epic. "Dragonspire," "Shadowmere" and "Ironhold" sit next to each other, and nothing feels like it was named by actual people. Real places are named for mundane reasons: a river crossing, a hill, a market, a long-dead landowner. This guide shows how that works, how to apply it to kingdoms, towns and taverns, and how to keep a whole map consistent.
Start with why a place got its name
Almost every real place name began as a plain description. Someone needed to tell a neighbor where they were going, so they said "the ford by the ash trees" or "the farm of Wulf." Over centuries the sounds wore down and the meaning faded, but the pattern stayed.
That gives you a reliable method. Before you pick a sound, answer one question: what would the first people to settle here have called it, and why? The reasons usually fall into four buckets:
- Geography: a river, hill, forest, bay, pass or marsh.
- Trade or resource: salt, tin, wool, a market, a ferry, a mill.
- People: a founder, a tribe, a saint or a ruling family.
- Events: a battle, a miracle, a disaster, a treaty.
Place-name endings and what they usually mean
English place names are a handy model because their endings are so recognizable. These are the common ones, with their usual (not universal) origins:
| Ending | Usual meaning | Fantasy-style example |
|---|---|---|
-ford | A river crossing | Ashford, Redford |
-ton | A farm or settlement (from "tun") | Harrowton |
-bury / -burgh | A fortified place | Oakbury |
-ham | A homestead or village | Thornham |
-wick | A specialized farm or trading outpost | Saltwick |
-mouth | Where a river meets the sea | Eelmouth |
Real names are messier than this table, and some endings have several possible origins, so treat it as a flavor guide rather than a rulebook. Your world does not need to be England in disguise. The point is the technique: pick a small set of endings, give each one a meaning, and use them on purpose. Invent your own, such as -varn for "mountain pass" in a northern language, and the map will immediately feel like it has a history.
Kingdoms, towns and taverns need different names
Scale changes the rules.
Kingdoms
Kingdoms and countries are usually named after a people, a founder or a dominant landscape, and the name is often older than anything else on the map. They tend to be short and weighty. A name that sounds like a title works well: "the Marches," "the Reach," "Aldermark." If you want a starting list to react to, the fantasy kingdom name generator and the country name generator give you raw material to adapt.
Towns and villages
Towns are where the "boring" logic pays off. Use the geography-plus-ending formula: Ash + ford, Salt + wick. A random town name generator is a quick way to fill a map with believable filler, and you can then edit the results to match your regional rules.
Taverns and inns
Taverns are the opposite: they are named to be remembered, and they are often signs you could draw. Think object plus animal or object plus object, such as The Gilded Heron or The Crooked Lantern. A good tavern name hints at a story the owner might tell. Browse the tavern name generator for ideas, then tie one to your setting: a harbor inn might be The Drowned Anchor, a mountain lodge The Last Hearth.
Islands
Islands are often named by outsiders, such as sailors or mapmakers, rather than by residents. That gives you two layers: the name on the chart and the local name. The island name generator is a handy way to find a seafarer's label to start from.
Keep each region internally consistent
Consistency is the single biggest upgrade you can give a map. Real regions share naming habits because they share a language and history. Give each region:
- A sound palette: three or four recurring syllables or letter patterns.
- A handful of endings with fixed meanings.
- A naming source, such as saints, animals, clan names or colors.
Then let borders show history. Where two regions meet, mix their styles, or let one region's name for a place differ from the other's. That is how real maps end up with places that have two names. For a deeper method for inventing the underlying languages, see our guide to creating fantasy names.
A worked example: three places, one coast
Suppose your northern coast was settled by sea-farmers who speak a language where -wick means "harbor" and -fell means "high moor." Their palette is hard consonants: k, th, rn.
- Kingdom: Thornmark, "the border land of the thorn people," named after the hedges that marked their frontier.
- Port town: Saltwick, a harbor that grew around a salt pan. Its river-mouth neighbor is Eelmouth.
- Inland village: Harrowfell, on the moor above, named for the harrow-shaped ridge.
- Tavern in Saltwick: The Salted Gull, because the owner's family once ran the salt pans.
Now introduce a southern region that speaks a softer language, with names like Valmere and Ostrelle. When the two meet at a river, you might get Saltwick on northern maps and Sauvalle on southern ones. Nobody had to explain it; the names do the worldbuilding.
Quick test: cover the map and read only the names. Can you tell which names belong to the same region? If not, tighten the palettes.
Common mistakes
- Every name is dramatic. Include dull, practical names like Millbrook, and the dramatic ones will land harder.
- Mixing too many styles in one region.
- Unpronounceable spellings that readers will skip rather than read.
- Names that never change. Real places get renamed after conquests, mergers and fashion.
- Forgetting the meaning. Even if it never appears in the book, keep a one-line note about why each name exists.
A simple naming workflow
- Sketch the geography and mark rivers, coasts and trade routes.
- Assign each region a palette, endings and a naming source.
- Name the old, big features first (kingdom, mountains, main river), then the towns, then the taverns.
- Use generators to produce 20 candidates per slot, then edit them to fit your rules.
- Write the one-line meaning for each name in a worldbuilding note.
Do that and your map will read as if it grew over centuries rather than being drawn on a Tuesday evening.
Naming from trade and history
Economy is the most underused source of place names. Ask what each place produces or sells, and let the name remember it even after the trade has changed. A town called Tanbury might once have been a tannery settlement that now lives on fishing. That mismatch is realistic: names outlive the reasons for them, and a character who says "nobody's tanned a hide here in two hundred years" gives the reader a free piece of history.
History works the same way. A kingdom might keep the name of a vanished people, a town might carry the title of a long-dead saint, and a ruined fort might survive only as a field name. When you rename a place after a conquest, leave the old name in use among the common people. Two names for one place tell the reader there was a conflict without a single line of exposition.