How to Name a Fantasy City: A Worldbuilder's Complete Guide

A great city name does more than label a place on a map. It evokes smell, sound, and history. It tells your reader something about the people who built those walls, the climate they endured, the gods they feared. The name of your city is its first sentence.

Whether you're writing a fantasy novel, building a D&D campaign, or designing a video game world, getting city names right can make the difference between a setting that feels like wallpaper and one that feels like somewhere real.

This guide covers everything: the linguistics of invented names, the cultural signals a name carries, how to build a consistent naming system, and the most common mistakes worldbuilders make. At the end, we'll point you to our free city name generator so you can put these principles into action instantly.

Why City Names Matter More Than You Think

Consider the difference between these names: Millhaven, Xorthax Prime, Aelindor, Ashfall. Before you know anything else, each name conjures a genre, a mood, even a rough geography. That's the power of a well-constructed name — it front-loads world information without a single word of exposition.

Tolkien spent years constructing languages before he named a single place in Middle-earth. He understood that names aren't decoration — they're the compressed history of a culture. You don't need Tolkien's obsessive depth, but you do need a system.

The Four Pillars of a Strong City Name

1. Phonetics: How It Sounds Out Loud

The sounds in a name carry emotional weight. Linguists call this "sound symbolism" — the idea that certain phonemes feel inherently harder, softer, darker, or more magical than others. Here's a quick reference:

• Hard stops (K, G, T, D) → aggressive, ancient, industrial. Good for dwarven cities, military fortresses, dark empires.
• Fricatives (F, V, S, Sh) → mysterious, whispered, arcane. Good for elvish settlements, hidden guilds, desert nomads.
• Nasals (M, N) → warm, rolling, familiar. Good for human towns, coastal villages, places of commerce.
• Liquids (L, R) → flowing, musical, noble. Good for elvish capitals, river cities, royal seats.
• Glottals and unusual clusters (Kh, Rh, Zh) → exotic, foreign, ancient. Good for any culture that should feel distinctly non-Western.

The best names often blend types. Lothrendor opens with an L (noble), centers on a hard D (ancient weight), and ends with a rolling R — it sounds elvish but not soft. That tension makes it memorable.

2. Structure: Prefix, Root, Suffix

Real-world place names are almost always compound words — a combination of descriptors, geography, and people. English place names offer great examples:

• -ford (Oxford, Hereford) → a river crossing
• -wick / -wich (Norwich, Warwick) → a settlement or dairy farm
• -chester / -caster (Manchester, Lancaster) → from Latin castra, a military camp
• -heim (Mannheim, Bernheim) → home or settlement in Germanic

Build a library of suffixes for each culture in your world. A mountain-dwelling civilization might end cities in -krag (crag, cliff face) or -gard (enclosure). A coastal culture might use -haven, -port, or -mere. When your suffixes are consistent, your world starts to feel like it has real linguistic history.

3. Meaning: Etymology Beneath the Surface

Even if your readers never know what a name means, you should. Knowing that "Ashfall" was named after the volcanic eruption that destroyed the original settlement changes how you describe it, what legends locals tell, and what ruins lie beneath the streets.

Try building names from meaningful components:

• Valdenmere → "valley of the lake" in a Germanic-ish language
• Solcrest → "the ridge where the sun rests"
• Korrath → "place of the blood-oath" in a darker tongue

You don't need a fully constructed language. Even a loose etymology document — a list of roots and their meanings — gives your names coherence that readers feel even when they can't articulate why.

4. Consistency: Building a Naming System

The most immersion-breaking error in fantasy worldbuilding is naming inconsistency. If your human cities are called Millhaven, Briarstone, and Ashford, don't suddenly introduce a human city called Xal'Koreth. That kind of naming belongs to a different culture — and if you're using it for humans, readers will notice the seam.

Create a simple naming guide for each major culture in your world:

• What phonemes does this culture prefer?
• What suffixes do their city names end in?
• What do those suffixes mean geographically or historically?
• Are names typically short (1–2 syllables) or long (3–4)?

Common Mistakes Worldbuilders Make

The Apostrophe Problem

Apostrophes in fantasy names (D'val, Xor'keth, L'anthas) became a cliché decades ago. They signal "this is fantasy" in the most lazy way possible. Unless you have a specific linguistic reason — a glottal stop, a conjunction in the original language — avoid them entirely.

Too Many Syllables

Long names are memorable when they're euphonious (Caradhras, Valinor). Long names are forgettable — or worse, annoying — when they're just a pile of syllables (Xoltharendraketh). Three syllables is usually the sweet spot. Four is acceptable for important capitals. More than four, and you're asking readers to work.

Copying Real-World Names Too Closely

Naming your city Londrium or Neo-Rome signals a failure of imagination and pulls readers out of the world. It's fine to draw inspiration from real languages and cultures — all good worldbuilders do — but the name should be transformed enough to feel genuinely new.

Ignoring Geography

Real cities are almost always named after what's there: a river, a mountain, a forest, a ford. If your city sits at the confluence of two rivers, its name might reference water. If it's built on volcanic rock, its name might reference fire or stone. Geography-rooted names feel earned rather than invented.

A Practical Naming Workflow

Here's the process I recommend for naming a city you'll use heavily in your story or campaign:

1. Decide the culture. What language family does this culture draw from? Germanic, Latin, Semitic, East Asian?
2. Identify the geography. Where is the city? What natural feature defines it?
3. Draft three to five candidates. Use your culture's phoneme library and suffix list.
4. Say them out loud. Multiple times. Does it trip off the tongue, or does it feel like a dental procedure?
5. Check for unintentional real-world words. Read it backwards, check it against other languages you know. Salgas is fine in English but might mean something unfortunate in another language.
6. Give it an etymology. Even one sentence: "Named after the gray stone quarried from the Aldenmere cliffs."

Using a Generator as a Starting Point

No tool replaces the thoughtful process above, but a good generator can do two things: break through naming block, and give you raw material to refine. When you're stuck, spinning through fifty generated names in thirty seconds often shakes loose the one that almost works — and almost-right is much easier to fix than nothing at all.

Our free city name generator is built around style-specific phoneme systems — the fantasy names don't sound like the sci-fi names, which don't sound like the coastal names. Use it to generate a batch, then apply the principles in this guide to find, refine, and justify the best ones.

Conclusion

A city name is a tiny story. Get it right, and it does a thousand words of work before your reader even reaches the first chapter. The secret isn't luck — it's system. Build phoneme libraries, construct suffixes with meaning, keep cultures consistent, and always ask: what does this place feel like, and does the name reflect that?

Do that, and your cities will feel less like labels on a map and more like places that existed before your story began — and will exist long after it ends.