It is tempting to draw a fantasy map for the aesthetic — a coastline, some mountains, a scatter of evocative place names — and move on. But the map is doing far more than decorating the front matter. It silently decides how long it takes to get anywhere, where food and wealth come from, which nations can reach each other to trade or fight, and where cities can exist at all. Get the geography wrong and every scene that touches travel, supply, or strategy inherits the error.
This guide covers how to build a fantasy map with internal logic — climate, terrain, and settlement that follow believable rules — and, just as important, how to treat the finished map as canon the rest of your story has to honor.
Why geography comes first
Geography is the layer most of the world rests on. Where the land is fertile decides where people farm; where rivers and harbors are decides where trade concentrates; where mountains and seas are decides who can reach whom. Wealth, power, and conflict collect along the lines geography draws. Build the land first and a great deal of the economy and politics follows almost on its own.
This is why a map is worth making early even if you never publish it. It is not an illustration so much as a constraint — a record of distances and directions and terrain that the rest of the story has to obey. A world whose geography is vague tends to grow contradictions: a journey that takes a week in one chapter and a day in another, a desert kingdom that somehow exports timber.
A little climate and terrain logic
You do not need to be a geologist, but a few rules of thumb keep a map from feeling arbitrary. Mountains catch rain on their windward side and cast dry rain shadows behind them, so deserts sit where the wet winds cannot reach. Rivers run downhill from high ground to the sea, gathering tributaries as they go rather than splitting apart. Forests grow where there is rain and warmth; tundra and ice sit at the poles and the heights.
None of this has to match Earth exactly — your premise may include a magic that breaks the rules, and that is fine as long as it is consistent and explained. What matters is that the reader never hits a jolt of nonsense: a river flowing uphill, a tropical jungle beside a glacier with nothing between them, a fertile breadbasket where no water could reach. Internal consistency, not realism, is the goal.
Placing civilizations
People settle where survival and trade are easiest: near fresh water and arable land, on defensible ground, and above all where routes converge — natural harbors, river mouths and confluences, fords, mountain passes, and crossroads. The great cities of your world should sit where wealth naturally collects, and their rivalries and alliances should make sense given who can actually reach whom across the terrain you have drawn.
When you place a settlement, ask why it is there: what does the land give it, who does it trade with, what protects it, what does it want that it cannot get at home. A city with a real geographic reason to exist feels inevitable. A capital dropped into a trackless waste for the look of it invites the reader to ask the question you skipped — unless your world has an answer ready.
The map is canon
Once the map exists, it is no longer a sketch — it is a set of binding facts. The distance between two cities, the direction a river runs, which kingdom borders which, how long a march or a voyage takes: these are now canon, and every scene that moves a character across the world has to respect them. The most common map-related continuity error is travel time that quietly changes to suit the plot.
Holding the map's facts as explicit canon — distances, directions, borders, travel times — is what lets you catch those errors before a reader does. It turns the map from a pretty picture into a source of truth the story can be checked against, which is exactly what you want once the world is large enough that you cannot hold every distance in your head.
Where CanonBoard fits
In CanonBoard, places, regions, and the routes between them live as connected, typed cards alongside the rest of your world — with a real timeline for the journeys and events that play out across them. Your geography becomes structured canon, not a static image you have to interpret by eye.
Because distances, borders, and travel times are held as facts, CanonBoard can check the story against them — surfacing a journey that takes too long or too little time, a border that contradicts an earlier one, an event that could not have happened where the map says it did, with both sides quoted and the conflict named. It never draws your world for you; the map and its logic are yours. It just keeps the story honest about the geography you built. Start free and put your map somewhere the story has to obey it.
Frequently asked questions
- Do you need a map to write a fantasy story?
- You need the geography to be consistent, which usually means at least a rough map. The map keeps travel times, directions, and distances from contradicting each other across the story — a river that flows one way in chapter two should not reverse in chapter twenty. Whether it is a polished illustration or a sketch, the geography has to hold.
- How do you make a fantasy map realistic?
- Follow a little physical logic: rain falls on the windward side of mountains and leaves deserts in their shadow, rivers run downhill to the sea and do not split as they go, and cities grow where trade concentrates — harbors, river mouths, fords, and crossroads. You do not need real-world accuracy, only internal consistency that does not jolt the reader.
- Where should cities go on a fantasy map?
- Where people would actually settle: near fresh water, arable land, and defensible ground, and especially where trade routes meet — natural harbors, river confluences, mountain passes, and crossroads. Placing a great city in a barren waste with no water or trade reason undercuts believability unless the world explains why it is there.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free