Where to Put Cities on a Fantasy Map (And Why It Matters)

Scatter twelve dots across a continent, name them, and something will feel wrong even to a reader who has never thought about urban geography for a second in their life.

The reason is that real cities aren’t distributed. They’re caused. Every one of them sits where it does because of something specific about that spot, usually something about moving goods, and a reader who has looked at a real atlas has absorbed the pattern without ever learning the rule.

The good news is that the rule is short, and applying it makes a map look researched.

A city is an answer to a question

The question is almost always some version of: where does the cargo have to stop?

Trade doesn’t flow smoothly. It hits points where goods must be unloaded, reloaded, transferred to a different kind of transport, taxed, stored or guarded. Geographers call these break-of-bulk points, and they are where towns grow, because every transfer needs people: dockworkers, carters, warehouses, inns, moneylenders, and eventually a lord who taxes all of it.

Find the places on your map where movement gets interrupted, and you’ve found your cities.

The six sites

Natural harbours. A sheltered bay where ships can ride out weather is one of the oldest reasons to build anything, offering trade access and fishing at once. It is not enough for the coast to be a coast: look for an inlet, a bay behind a headland, a river mouth with deep water. Istanbul and New York both grew where they did because of harbours.

River mouths. Where a river meets the sea, everything travelling downriver has to transfer to seagoing ships, and everything arriving from abroad transfers to riverboats. That’s a break-of-bulk point with a guaranteed hinterland behind it. River mouths are the single most reliable place to put a large city.

Fall lines. This is the one most fantasy maps miss, and it’s the most interesting. A fall line is where a navigable river stops being navigable, at rapids or a waterfall. Ocean-going boats can get exactly that far inland and no further, so cargo comes off the water and goes onto carts. That alone builds a town. But the falling water also turns mills, so the same spot gets industry: grinding grain, working metal, later anything that needs power. Furthest navigable point plus free energy is an unusually strong combination, and it’s why a whole line of American cities sits along one geological boundary.

Confluences. Where two rivers meet, a settlement can reach up both valleys, control traffic on both, and see anyone coming. Confluence towns are natural markets because two separate trade routes arrive at the same dock.

Fords, bridges and crossings. A road has to cross the river somewhere. Wherever that is, traffic concentrates, which means an inn, then a market, then a garrison to tax the traffic, then walls. Half the -ford and -bridge names on any real map are exactly this.

Passes and chokepoints. A gap through a mountain range funnels everything travelling between the two sides through one line. Whoever holds it controls a border, and towns there are fortified early and fought over often.

There’s a seventh that’s worth mentioning but is weaker on its own: resources. A mine, a quarry, salt, good grazing. These create settlements, but the settlement usually stays a town rather than becoming a city unless it also sits on a route out. A mining camp with no road is just a mining camp.

The unglamorous rule that ties it together

If you only remember one thing: cities form where transport changes.

Water to land. River to sea. Boat to cart. Road to road. Flat to mountain. Every one of those transitions costs time and labour, and wherever there’s a reliable transition, somebody sets up to profit from it and never leaves.

This is why so much of the answer is rivers and coasts. Before railways, moving heavy goods overland was brutally expensive compared to floating them, so water routes dominated, and the cities line up along them.

Capitals follow a different logic

Trade explains most cities, but not capitals, which is a distinction worth making on your map.

Capitals sit where power is convenient. Sometimes that means the largest trading city, so the two coincide. Often it means something else: near the geographic centre so the realm can be governed, near the founding dynasty’s ancestral seat for legitimacy, or deliberately away from the biggest merchant city so the crown isn’t standing on top of a rival power base.

A capital that isn’t the biggest city is one of the cheapest ways to make a kingdom feel like it has a history. Somebody chose that hill for a reason, and the reason stopped being true two hundred years ago.

You probably have too many cities

Pre-industrial societies were overwhelmingly rural. A realm the size of a small country supported a handful of places worth calling cities, a scattering of market towns, and an enormous amount of farmland and forest that nobody labelled.

If your continent has thirty named cities, it reads as a map of a modern country, and it also gives you thirty places to keep track of. Fewer, better-placed cities with real reasons behind them beat a dense sprinkle every time.

Empty space is a feature. It’s where things live that shouldn’t have a signpost.

Spacing that looks right

Real settlements cluster and then leave gaps. The clustering follows the routes: a river valley might hold five towns in eighty miles, and then there’s nothing for two hundred because the next valley is over a range.

So resist the urge to spread evenly. Line towns up along your rivers and coasts, let them thin out as the land gets higher or drier, and leave real voids in the interior. The gaps say as much about the world as the dots.

A quick pass over your own map

Take a map you’ve already drawn and check each city against a single question: why is it here?

If the answer is a harbour, a confluence, a crossing, a fall line, a pass or a resource, keep it. If the answer is “the map looked empty there,” either move it to the nearest real site or cut it. Most maps lose a third of their cities to this test and get better.

Then check the reverse: are there obvious sites with nothing on them? A river mouth with no port is strange, and if you want to keep it that way, that’s a story. Somebody used to live there.

Where the generator puts them

Our fantasy map generator places settlements using this logic rather than scattering them. Cities appear on coastlines and along rivers, where trade would actually put them, with the largest sites favouring river mouths and sheltered coasts. Generate a map and the placement should survive the “why is it here” test, which is exactly the point.

Every label is editable, so if you want to move a city to a pass you’ve decided matters, click it and drag. You can also add your own towns, castles and other marks anywhere on the map from the Advanced panel.

For a campaign region with two or three rival realms and their capitals, the D&D map generator is the right starting scale. Before you finalise anything, it’s worth checking your map’s scale, since city spacing only means something once you know how far apart they actually are, and your rivers, since almost every good city site on this list depends on the water being right.