Place names are the oldest documents in any world. Long after the language that made them has died, after the people who spoke it have been conquered, absorbed or forgotten, the name of the hill is still the name of the hill. Nobody sat down and decided to preserve it. It survived because saying it was easier than agreeing on a new one.
That is the single most useful thing to know about naming places in fiction, and it is why invented place names so often feel weightless. A name like Shadowfell Keep was clearly coined by an author. A name that has been worn down by three hundred years of people mumbling it on the way to market feels like it belongs to somewhere real.
Real place names come in four broad kinds, and a map that uses all four looks like a map with a history.
Location name generators
Every generator below uses a hand-curated pool. No account, no email, no paid tier.
Settlements
- Village name generator — small, descriptive, usually named after the thing you can see from it.
- Town name generator · City name generator — larger settlements, where names get layered and abbreviated.
- Tavern name generator — the one naming tradition that is genuinely playful, because inn signs had to be recognisable to people who could not read.
Wilderness and terrain
Structures and sites
- Castle name generator — usually named for the land, not the family.
- Dungeon name generator — names given by the people who avoid the place, not the people who built it.
Realms and worlds
- Empire name generator · Kingdom name generator · Fantasy kingdom name generator
- Fantasy world name generator — for the name that sits at the top of the map.
Curated name lists
The four kinds of place name
Descriptive names are the most common and the most under-used in fantasy. Somebody arrived, looked around, and said what they saw: the black water, the long ford, the two hills. These names are boring on purpose, and that is exactly why they read as authentic. A map where every name is evocative is a map nobody actually lived on.
Ownership names record who held the land when names were being written down. Anything of the form “X’s farm”, “X’s ford”, “X’s town” freezes a person who is otherwise entirely lost to history. In your world, this is free depth: the village of Harrowsdene implies a Harrow, and nobody has to know who he was — least of all the people living there.
Event names record something that happened once. These are rarer and should stay rare, because they are the loudest kind. A place called the Drowned Field is a promise to the reader; use two or three on a map, not twenty.
Substrate names are the interesting ones. When one people replaces another, the incomers usually keep the old names without understanding them — and then, because the old word has become meaningless, they add their own word for the same thing on the end. This is why our own maps are full of accidental repetition: the Sahara Desert is the desert desert. The River Avon is the river river, because afon is simply Welsh for river. Lake Michigan takes its name from an Ojibwe word meaning large water, so it is large-water lake.
Put one or two of these on your map and you have implied an entire vanished civilisation without writing a word of its history. A river your characters call the Ansa River, where ansa was the old word for river, tells the reader that somebody was here first and is not here now.
Names change; maps should show it
Settlements outgrow their names and rarely get new ones. A city of two hundred thousand still called Oxford is named for a place cattle could cross a river, which stopped being the interesting fact about it roughly a thousand years ago. That mismatch is realistic and useful: a capital city with a humble, descriptive, obviously-village name tells the reader it was a village once, and grew.
The same applies in reverse. A grand name on a small place implies decline — somewhere that was important and no longer is. A hamlet of forty people called the Imperial Ford is a story in four words.
Naming a region so it hangs together
The trick to a map that feels like one country rather than a list of names is a shared vocabulary of endings. Pick three or four elements — say -dene for a valley, -wick for a farmstead, -mere for a lake, -cot for a shelter — and reuse them across the region. Suddenly Harrowsdene, Ashmere and Coldwick are obviously neighbours, and a name from three hundred miles away that uses none of those elements is obviously foreign, without you having to say so.
Then break it once, deliberately, at the border. That is where the map becomes a history.
Fill your settlements with people using the race name generators, give them professions with the class generators, put the powers that rule them together with the organization generators, and see how to name a fantasy world for keeping the whole map consistent.
Place naming questions
How do I make fantasy place names sound real instead of invented?
Make most of them boring. Real maps are dominated by flat descriptive names — the long ford, the black water, the north farm — with only a handful of dramatic ones. Fantasy maps usually invert that ratio, which is why they read as written rather than lived in.
Should place names be in a constructed language?
A few of them, ideally the oldest ones. Names your characters cannot translate are the strongest signal that somebody was there before them. But if every name on the map is untranslatable, nothing stands out and the map becomes noise.
How do I name a capital city?
Give it a name that was appropriate when it was small. Capitals almost never rename themselves, so a grand name on a capital reads as invented, while a humble one implies the city grew into its importance.
Can I use these location names in my campaign or published work?
Yes, freely and without attribution, commercial or not. Trademarked and recognisable names from published settings are deliberately kept out of the pools.