Fantasy Map Scale: How Big Should Your World Be?

Here’s a symptom worth recognising. Every journey in your campaign takes about a week. The neighbouring kingdom is a week away. The mountains are a week away. The far coast is, somehow, also a week away.

That happens when a map has no scale. Not a missing scale bar, though that’s usually true too, but no decision about how big the world is. Without one, distance stops meaning anything, and every trip collapses into the same handful of travel days because there’s nothing to measure against.

Scale isn’t a maths problem. It’s a pacing problem, and it’s worth deciding on purpose.

What scale actually controls

The size of your map determines three things that matter at the table and on the page.

How long journeys take, which is your pacing. A three-day ride is a scene. A three-week ride is a chapter, or an act.

Whether a kingdom can function. A realm that takes two months to cross cannot be governed from one capital with medieval communications. It will have regional lords with real power, slow-arriving news, and a permanent risk of a province deciding it’s a country now. That’s not a flaw, it’s plot.

How isolated a place feels. The village two days from the city is a suburb. The village three weeks past the mountains is another world, and its people will have different gods.

Get the scale right and these come free. Get it wrong and you’ll be arguing with your own map all campaign.

The numbers people actually moved at

This is the useful part, and it’s where most guesses go wrong. Real pre-industrial travel was slower and more variable than instinct suggests. Bret Devereaux’s breakdown of army movement rates is the best treatment of the military end of this, and worth reading in full.

Who is travelling	Miles per day
Walking pace (raw speed, not sustained)	about 3 mph
A body of infantry on the march	8 to 12
A household moving its possessions	around 15
Traveller with one horse	20 to 25
Army on a forced march	20, exceptionally up to 50
Rich traveller changing horses	30 to 40
Messenger, riding at night, requisitioning fresh horses	55 to 60

Two things jump out.

First, an army is slow. Eight to twelve miles a day is the realistic figure, because an army moves at the speed of its supply train, its stragglers and its worst road. Forced marches of fifty miles did happen, but plenty of soldiers dropped out or straggled far behind, so it isn’t a rate you can sustain.

Second, the gap between an army and a messenger is enormous. A rider can carry news five or six times faster than a force can march. That single ratio generates more plot than any magic system: the warning always arrives before the enemy, and how much before is a decision you get to make.

Also worth remembering: these are good-conditions numbers. Rain, mud, mountains, winter and rivers without bridges all cut them, sometimes by half.

Work backwards from the story

The method is simple. Don’t pick a map size and calculate travel times. Pick the travel times you want and size the map to fit.

Ask: how long should it take to get from the party’s home to the capital? If the answer is “about a week, so it feels like a real trip but doesn’t eat a session,” and they’re riding, that’s roughly 150 miles. Now you know one distance on your map, and everything else scales from it.

Do this for two or three journeys that matter, then measure them against your drawing. If the map disagrees with your intent, the map is wrong, and it’s easier to change than the story.

A worked example

Say the campaign is about a border war between two kingdoms, and you want these things to be true:

An army takes about a month to reach the border from its capital. A messenger makes the same trip in under a week. A merchant caravan crosses the whole kingdom in a season.

An army at 10 miles a day for 30 days gives you 300 miles from capital to border. Check the messenger against that: 300 miles at 40 miles a day is about seven or eight days. Close enough, and you can tighten it to a week by moving the capital slightly closer or giving the messenger a road.

So the kingdom is roughly 300 miles from its heart to its edge, meaning something like 600 miles across. On a map 1600 pixels wide showing that kingdom plus its neighbour, you’re at something like a mile and a half per pixel, and your scale bar should say so.

Now the interesting part. At that size, when the border is attacked, the capital learns about it a week later and can respond three weeks after that. That’s a month of campaign in which the frontier lords are entirely on their own. You didn’t invent that situation. The scale did.

Four scale mistakes

The pocket continent. A landmass with eleven kingdoms, four mountain ranges and a great desert, all fitting inside a week’s travel. Everything is adjacent, so nothing feels foreign. If your map has a lot of features, it needs to be big, or it needs fewer features.

The unusable empire. The opposite: a realm so vast that its own map can’t explain how it holds together. If a courier takes four months to reach the frontier, you need something doing the work that couriers can’t. Magic, an ancient road network, a river system, trained birds. Any of those is a good answer. No answer is a problem.

The undifferentiated distance. Every place roughly equidistant from every other. Real geography clusters: towns bunch along a river valley and then there’s a hundred empty miles. Uneven spacing is what makes a map look surveyed rather than arranged.

The invisible scale. No scale bar. This is the most common of all, and it’s the one that lets the other three happen unnoticed. Put a number on the map and the errors surface immediately.

Choosing a scale for what you’re making

A rough guide for where to start:

A battle map is measured in feet, and a 5-foot grid is correct. Nothing in this article applies to it.

A local region, for a campaign that stays in one valley or barony, works well somewhere around 30 to 60 miles across. Every location is within a few days, and the party knows the territory.

A kingdom or campaign region, the most common scale for a table map, sits comfortably between 300 and 800 miles across. Long enough for travel to matter, small enough for one power to plausibly rule it.

A continent runs into the low thousands of miles, with several realms, real climate variation and journeys measured in months.

A world map is planetary, and its job is different: it isn’t for measuring journeys, it’s for showing what exists. Put the scale bar on anyway.

Getting the bar on the map

Every map our fantasy map generator produces draws a scale bar in the corner by default, sized to the map type you chose, along with a compass rose and a title banner. If you want it gone for a stylistic reason, the Advanced panel has a toggle, but leave it on while you’re planning: it’s the thing that keeps your journeys honest.

The map type control is effectively a scale control. Island for a single self-contained setting, Continent for a campaign region, World for planetary scope. Pick the one that matches the journeys you want to run, generate a few seeds, and check the bar against the trips in your notes.

Once the scale is settled, two things are worth checking before you call the map done: whether your rivers behave, and whether your cities are where cities would actually be. Scale, water and settlement are the three that hold a map together.