How to Name Fantasy Kingdoms, Cities, and Places

Every great fantasy world is built on its geography, and every memorable location begins with a name. Think of Middle-earth without Mordor, Westeros without King's Landing, or the Forgotten Realms without Waterdeep. These names do more than label locations on a map—they convey history, culture, danger, and promise in just a few syllables.

Place names are arguably the most important element of worldbuilding because they are the words your readers or players will encounter most often. A character name appears when that character is present. A place name appears every time someone travels, gives directions, recalls history, or plans a journey. Your kingdom's name might be spoken a thousand times across a campaign or novel. It needs to carry that weight.

The good news is that naming fantasy places is not an arbitrary art. Real-world place names follow remarkably consistent patterns that evolved over centuries. By understanding how places like Edinburgh, Constantinople, Reykjavik, and Sacramento got their names, you gain a toolkit for creating fictional names that feel just as authentic. This guide will walk you through those real-world patterns, then show you how to apply them to kingdoms, cities, villages, and wild places in your fantasy world.

Before inventing fantasy names, it helps to understand how real places got theirs. The study of place names is called toponymy, and it reveals a surprisingly simple truth: almost every place name in the world started as a description. Someone pointed at a geographic feature, described it in their language, and that description stuck. Over centuries, pronunciation shifted, languages changed, and the original meaning was forgotten—but the name endured.

This means that the most authentic fantasy place names are, at their core, descriptions. They describe what the place looks like, who founded it, what happened there, or what resource it provides. The trick is making those descriptions sound like names rather than sentences, and that is where linguistic patterns come in.

English place names are a masterclass in compound naming. Most are formed by combining a descriptive element with a geographic suffix. Once you recognize these suffixes, you can reverse-engineer almost any English town name—and use the same logic to create fantasy equivalents.

Common English place name suffixes and their meanings:

• -ton / -town — an enclosed settlement or farmstead (e.g., Brighton, Northampton)
• -ham — a homestead or village (e.g., Birmingham, Nottingham)
• -bury / -burgh — a fortified place (e.g., Canterbury, Edinburgh)
• -ford — a river crossing (e.g., Oxford, Bradford)
• -ley / -leigh — a woodland clearing (e.g., Beverley, Hadleigh)
• -stead — a place or site (e.g., Hampstead, Berkhamsted)
• -wick / -wich — a dwelling or trading place (e.g., Norwich, Warwick)
• -mouth — the mouth of a river (e.g., Plymouth, Portsmouth)
• -dale — a valley (e.g., Airedale, Clydesdale)
• -field — open land (e.g., Sheffield, Chesterfield)
• -bridge — a bridge crossing (e.g., Cambridge, Tonbridge)

To create fantasy equivalents, replace the descriptive element with something from your world. Instead of "Oxford," you might have "Elkford" (where elk cross the river) or "Greyford" (named for grey stone). Instead of "Canterbury," perhaps "Thornbury" (a fort surrounded by thorns) or "Kingsbridge" (where the king built a bridge).

Norse and Germanic naming traditions produced some of the most evocative place names in history, and they are a gold mine for fantasy worldbuilders. These languages favored strong consonant clusters, compound words, and names that evoked the harsh beauty of northern landscapes.

Key Norse and Germanic place name elements:

• -heim / -ham — home or dwelling (e.g., Trondheim, Mannheim)
• -burg / -berg — mountain or fortress (e.g., Hamburg, Nuremberg)
• -vik / -wick — bay or inlet (e.g., Reykjavik, Lerwick)
• -fjord — a narrow sea inlet (e.g., Sognefjord, Hardangerfjord)
• -ness — a headland or promontory (e.g., Inverness, Skegness)
• -dal / -dale — a valley (e.g., Gudvangen, Arendal)
• -holm — a small island (e.g., Stockholm, Bornholm)
• -foss — a waterfall (e.g., Gullfoss, Dettifoss)
• -stad / -stead — a place or farm (e.g., Hallingstad, Karlstad)
• -by — a farmstead or village (e.g., Derby, Whitby)
• -thorp / -thorpe — an outlying settlement (e.g., Cleethorpes, Scunthorpe)
• -garth / -gard — an enclosure or yard (e.g., Asgard, Midgard)

Norse names are particularly powerful for fantasy because they combine descriptive prefixes with geographic suffixes in a way that feels both ancient and immediately comprehensible. "Reykjavik" literally means "smoky bay" (from the geothermal steam the first settlers saw). "Stockholm" means "log island" (from the log barriers in the harbor).

Celtic and Latin naming traditions offer a different flavor from Germanic names. Celtic names tend toward flowing sounds with soft consonants, while Latin names carry the weight of empire and administration. Both are invaluable for certain kinds of fantasy settings.

Common Celtic place name elements:

• -dun / -din — a fort or hill-fort (e.g., Dundee, Edinburgh/Dun Eideann)
• -llan / -lan — a sacred enclosure or church (e.g., Llandudno, Llanelli)
• -aber / -inver — a river mouth or confluence (e.g., Aberdeen, Inverness)
• -drum / -druim — a ridge (e.g., Drummond, Drummore)
• -glen / -glyn — a narrow valley (e.g., Glendale, Glencoe)
• -kill / -kil — a church or cell (e.g., Kilmarnock, Kilkenny)
• -rath / -rath — a ring fort (e.g., Rathmore, Rathlin)
• -strath — a wide river valley (e.g., Strathmore, Strathclyde)
• -loch / -lough — a lake (e.g., Lochaber, Loughborough)
• -ben / -pen — a peak or head (e.g., Ben Nevis, Penzance)

Latin place names, meanwhile, often feature endings like -um,-us, -ia, and -ium (e.g., Londinium, Aquileia, Hispania). Latin prefixes like nova- (new),magna- (great), and sancta- (holy) create names with an imperial gravitas. For fantasy empires, bureaucratic civilizations, or ancient ruins, Latin-inspired names are unmatched.

Celtic names work beautifully for ancient, mystical, or druidic cultures in fantasy. The soft consonants and rolling vowels evoke old forests and standing stones. Latin names, by contrast, suit empires, legions, and civilizations that value order and architecture. Mixing the two—as history actually did when Rome occupied Celtic lands—creates richly layered names like "Camulodunum" (the fortress of Camulos, a Celtic war god, given a Latin suffix by Roman occupiers).

Kingdoms and empires demand names that sound grand, historical, and weighty. These are the names that appear on the largest scale of your map, the names spoken by ambassadors and written in treaties. They need to feel like they have endured for centuries.

In the real world, kingdoms are named in several distinct ways:

Named after a people or tribe. France comes from the Franks. England comes from the Angles. Scotland from the Scots (originally an Irish tribe). This is the most common pattern historically. The kingdom is the land of a people. In fantasy, this means creating a cultural name first, then deriving the kingdom name from it: the Valdori people live in Valdoria; the Thane clans rule the Thanemark.

Named after a founder or dynasty. The Carolingian Empire was named for Charlemagne (Carolus Magnus). The Ottoman Empire was named for Osman I. Saudi Arabia is named for the Saud family. In fantasy, this creates names like "The Aldric Dominion" or "Korvath's Reach"—names that immediately imply a single powerful figure or bloodline.

Named for geography. The Netherlands (low lands), Iceland (island of ice), Montenegro (black mountain). Geographic names work well for kingdoms defined by a single dominant landscape feature. "The Ashlands," "Stormreach," "The Sunward Coast"—these names tell you what the kingdom looks like before you read a single description.

When naming kingdoms, lean toward two or three syllables for the core name. Modifiers like "The Grand Duchy of" or "The Free Cities of" add formality without burdening the name itself. Your characters will say "Valdoria," not "The Most Serene Kingdom of Valdoria" in everyday conversation.

Consider how the name sounds when used possessively and adjectivally. "Valdorian soldiers," "the Valdorian court," "a Valdorian merchant"—if the adjective form feels natural, the kingdom name works. If it is awkward ("The Shattered Isles-ian army"), you may need a demonym that differs from the kingdom name, or a simpler base name.

Cities begin as practical places: a crossing on a river, a sheltered harbor, a hilltop that is easy to defend, a crossroads where trade routes meet. Their names almost always reflect this origin, even if centuries of linguistic drift have obscured the connection.

River and water names are the most common origin for cities worldwide. Rivers were highways before roads existed, and settlements clustered at crossings, confluences, and harbors. In your fantasy world, a city at a river fork might be called "Twinwater" or "Merrowmeet." A port city could be "Greyhaven" or "Tidegate."

Defensive position names reflect the city's strategic value. Real examples include every city with "castle," "fort," "-burg," or "-chester" in its name. In fantasy, walled cities and fortress-towns might be called "Irongate," "Highwatch," or "Shieldmount."

Trade and resource names mark cities known for a particular industry. "Saltburg" produces salt. "Copperfield" mines copper. "Markethollow" hosts a famous bazaar. These names are especially useful for giving players or readers immediate economic context.

Religious and political names appear in cities founded by decree or devoted to a deity. Constantinople was the city of Constantine. San Francisco honors Saint Francis. In fantasy, "Solara" might be a city devoted to a sun goddess, while "Throneport" was founded as a royal capital.

Size matters for naming. Major capital cities in history often have grander, more distinctive names. Smaller market towns are more likely to bear simple, descriptive names. A sprawling capital might be "Aurenthas"—unique and imposing. A local market town is more likely "Millford" or "Greendale"—descriptive and unassuming.

Villages and hamlets are the smallest named settlements, and their names should feel organic, local, and unpretentious. These are not places that were planned or decreed into existence. They grew naturally around a farm, a mill, a crossroads, or a spring, and their names reflect that humble origin.

In the real world, village names are overwhelmingly descriptive of the immediate landscape. "Oakfield" had oak trees and a field. "Brookside" sat beside a brook. "Stonewall" had a notable stone wall, perhaps the remnant of an older structure. The pattern is simple: combine a visible local feature with a generic settlement or landscape term.

Natural features: Names reference trees, rocks, water, hills, and soil. "Ashwick" (ash trees + dwelling), "Redmere" (red-colored lake), "Thornhill" (thorny hill). These names are immediately evocative and require no explanation.

Personal names: Many villages are named after an early settler or landowner. The Old English suffix -ing means "people of," so "Wokingham" was "the homestead of Wocca's people." In fantasy, "Aldric's Hollow" or "Brennan's Field" implies a founding family.

Occupational names: Villages centered on a trade sometimes carry that trade in their name. "Potter's Crossing," "Tanner's Rest," "Millhaven." These instantly communicate the village's economic role.

The key to authentic village names is restraint. Villages are small and humble; their names should be too. A village called "Shadowspire of the Eternal Night" is absurd. A village called "Mudwall" or "Oldbrook" is perfect. Save the dramatic names for places that earned them.

Forests, mountains, seas, deserts, swamps, and ruins are the spaces between civilization. They are where monsters dwell, where ancient powers sleep, and where adventurers venture at their peril. Their names should reflect both their geographic nature and the emotional response they provoke.

Forests in real life are often named for their dominant tree species (the Black Forest, Sherwood), a color impression (the Dark Forest, the Greenwood), or a local legend. In fantasy, forest names work best when they hint at what lies within. "The Whispering Wood" suggests mystery. "Bloodthorn Forest" suggests danger. "The Silverleaf Glade" suggests beauty and perhaps elvish presence.

Mountains are traditionally named for their appearance from a distance, for the gods believed to inhabit them, or for the dangers they pose. "Mount Olympus" was the home of the gods. "The Matterhorn" means "peak of the meadow." In fantasy, mountain names often combine a dramatic adjective with a geographic term: "The Shattered Peaks," "Dragonspine Ridge," "Mount Ashengrey."

Seas and lakes are named for their color, temperament, or the lands they border. The Mediterranean means "middle of the earth." The Dead Sea reflects its lifelessness. In fantasy: "The Bitter Sea," "The Jade Depths," "Lake Sorrow."

Dungeons and ruins are named by the people who know to avoid them, not by the people who built them. A ruined fortress might have an original name lost to history, replaced by what locals call it: "The Bonepits," "Greyhollow Keep," "The Sunken Halls." Dungeons named by their builders would sound administrative ("The Lower Vaults of Karathis"). Dungeons named by terrified locals sound ominous ("The Screaming Depths").

The difference between a fantasy world with good names and one with great names is linguistic consistency. When all the places in a culture sound like they belong to the same language, the world feels real. When every name seems to come from a different linguistic tradition, the illusion shatters.

You do not need to create a full constructed language like Tolkien's Quenya or Sindarin. You need a small, consistent set of phonetic rules and common morphemes that you apply across all names within a culture. Here is how to build one.

Step 1: Choose your sound palette. Decide which sounds define this culture's language. A harsh, warrior culture might favor hard consonants (k, g, t, d) and short vowels (a, o, u). An elegant, ancient culture might favor soft consonants (l, n, s, th) and long vowels (ee, ai, oo). Write down five to eight consonant sounds and three to four vowel sounds that feel right.

Step 2: Define common suffixes. Pick four to six place-name endings and assign rough meanings. For example: -rath (fortress),-mere (lake), -val (valley), -kor(mountain), -wyn (forest), -hest (city). Every place name in this culture will end with one of these.

Step 3: Define root words. Create eight to twelve root words for common descriptors: colors, materials, animals, elements, cardinal directions, and significant concepts. For example: ael- (silver), dun-(dark), thor- (great), bel- (white),mor- (black), kel- (river).

Step 4: Combine consistently. Now generate names by combining roots and suffixes: Aelrath (Silver Fortress), Dunmere(Dark Lake), Thorval (Great Valley), Belwyn(White Forest), Morhest (Black City), Kelrath(River Fortress). Every name sounds like it belongs to the same culture.

Step 5: Set stress patterns. Decide where the emphasis falls. English tends to stress the first syllable. French stresses the last. Some languages always stress the penultimate syllable. Consistent stress patterns are subtle but powerful. If all names in one culture are stressed on the first syllable ("THRON-gar," "VAL-dor," "KOR-heim") and another culture stresses the last ("elen-THAR," "asol-VEEN," "kalar-NIS"), a listener can immediately distinguish between the two without knowing either language.

Even experienced worldbuilders fall into predictable naming traps. Here are the most common mistakes and how to avoid them.

The Unpronounceable Name. "Xzyrth'kaal" might look exotic on a map, but no one at your table or reading your novel will say it the same way twice—or at all. Every place name should be pronounceable on first reading. If you need an apostrophe, a double consonant cluster with no vowels, or more than four syllables, reconsider. The greatest fantasy names in literature are clean and clear: Gondor, Narnia, Hogwarts, Ankh-Morpork.

Inconsistent naming within a culture. If one city in your elven kingdom is called "Elarindel" and the next is called "Grakthor," something is wrong. Names within the same culture should share phonetic DNA. This is the single most common worldbuilding error, and it is the easiest to fix: define your culture's naming rules before naming any places, and follow them consistently.

Modern-sounding names. "New Riverside Heights" and "Lake View Estates" are real estate developments, not fantasy locations. Avoid modern naming conventions (numbered streets, compass-based subdivisions, marketing-speak). Medieval and ancient naming was descriptive and organic, never branded. Your fantasy world should feel the same way.

Over-the-top edginess. "Skull Mountain of Blood Death" tries so hard to be threatening that it circles back to comical. Real dangerous places have restrained names. "Verdun" does not sound scary, but it evokes horror because of its history. Let your places earn their ominous reputation through the story, not through name-sledgehammering.

Accidental real-world words. Always say your name out loud and consider how it sounds in the languages your audience speaks. "Dikton" and "Fartenheim" may seem perfectly reasonable in your naming system but will provoke laughter at the table. Search your invented names to make sure they are not slang, brand names, or profanity in another language.

Too many unique naming traditions. A world with twelve kingdoms, each with a completely distinct naming language, is exhausting. Real-world naming traditions cluster into families. Romance languages share naming elements. Germanic languages share others. Group your cultures into two to four linguistic families, with variation within each family, and your world will feel rich without being overwhelming.

Running a tabletop RPG creates unique naming challenges. You need names quickly, often improvised on the spot, and they need to be memorable enough that players can recall them weeks later without detailed notes. Here are practical strategies for Dungeon Masters.

Prepare a name bank. Before each session, generate a list of ten to fifteen place names that fit each region your players might visit. When players ask "What's this village called?" you have an answer ready. Use our generators to build these banks quickly and keep them organized by region.

Use the suffix method for improvisation. Memorize three or four suffixes for each culture in your world. When you need a name on the fly, glance at the environment, pick a descriptive word, and add the suffix. Players approaching a village near a river in your Norse-inspired region? "Welcome to Broadvik." Entering a forest settlement in your Celtic lands? "This is Oakhaven." The suffix anchors it to the culture; the prefix describes the immediate geography.

Write names down immediately. The moment you invent or use a place name, write it on your map or session notes. There is nothing more immersion-breaking than calling a town "Millford" one session and "Millbrook" the next. Consistency beats creativity in a long campaign.

Let players name things. When the party discovers an unnamed ruin or sets up a camp, ask them what they call it. Player-named locations become the most memorable places in any campaign because the players have personal investment in them. "Remember when we found that cave and called it Goblin's Regret?" is the kind of story that keeps campaigns alive for years.

Use name evolution for history. If an ancient empire once ruled this region, their old place names should linger beneath the current ones. "Thornwall" might have been "Thar'n Vael" in the old tongue. Having NPCs use the old name occasionally creates a sense of depth and history with minimal effort. Scholars use the ancient name; commoners use the modern one. This is exactly how real place names work.

Match name complexity to importance. The capital city of the kingdom deserves a distinctive, carefully chosen name. A random hamlet the players pass through on the road does not. Save your best names for the places that matter most, and let minor locations have simple, forgettable names. Players will naturally remember the distinctive names and forget the generic ones—which is exactly what should happen.