Fantasy mapmaking tools are unusually good at creating the feeling of progress. You can spend an evening drawing coastlines, another labeling rivers, a third choosing a projection, and still have no answer to the question the story actually needs: Why is this city here?

A useful geography toolkit should make worldbuilding decisions easier to test. It should not merely make the map prettier.

For most creators, that means combining three kinds of tool rather than searching for one perfect app:

  • a fast sketch surface for thinking;
  • a structured map or GIS tool for layers, scale, and revision;
  • reference data and checklists that keep geography internally consistent.

The exact software can change. The logic should survive the software.

This guide focuses on paper or simple drawing tools, QGIS, Natural Earth data, and a small set of creator-made templates. QGIS is open-source GIS software; its current official 3.44 documentation covers project coordinate systems, layer handling, print layouts, and export. Natural Earth provides public-domain vector and raster map data at several world scales. These are real cartographic tools, not fantasy-map generators, which is precisely why they can be useful: they force you to separate geography from decoration.

Tool one: the ugly sketch that answers one question

The fastest map is often the least beautiful one.

Use paper, a tablet note app, or a simple drawing canvas when the question is still conceptual:

  • Where does rain fall?
  • Which route avoids the mountains?
  • How many days apart are these cities?
  • Which state controls the river mouth?
  • What does an army have to cross?
  • Which coast faces the prevailing storm track in your fictional climate model?

At this stage, a polished coastline is a distraction. Draw only the variables that affect the question.

A practical sketch might contain five marks: a mountain wall, two rivers, one pass, one port. If the plot requires a caravan to move from the inland capital to the port, this crude map is already useful because it exposes the choke point.

What this tool is bad at: version control, accurate distances, layered alternatives, and consistent export.

Do not ask a napkin sketch to become the canonical production map.

Tool two: QGIS when the world needs layers

QGIS becomes valuable when the same geography must answer many questions over time.

A GIS project can separate information into layers: terrain, rivers, settlements, borders, roads, languages, trade zones, military control, climate regions, archaeological sites, or story events. That allows a creator to hide one interpretation without deleting another.

For fantasy work, the biggest gain is not “professional GIS accuracy.” It is reversible structure.

Suppose your fictional border follows a river in chapter one, but later research suggests the river changes course across a floodplain. In a flat image, the line and the river may be baked together. In a layered project, the border can be edited separately while the physical map remains intact.

Set the project coordinate logic before drawing everything

Real-world GIS must relate coordinates to Earth. A fully fictional planet does not automatically need a real Earth CRS, and creators should not pretend otherwise.

QGIS can work with a project CRS and can also handle unknown/non-Earth-style coordinate use cases depending on setup. If you are building a non-Earth map, your main requirement is consistency: establish what one unit means, where your origin sits, and how distance will be interpreted before you start using measurements as story facts.

If you are using Earth reference data as a scaffold, coordinate reference systems matter. USGS notes that no map projection is “best” for every purpose because flattening a globe necessarily introduces distortion. A projection appropriate for a world overview may be poor for measuring a small region.

For creators, this leads to a simple rule:

Choose a map projection or coordinate method because of the decision you need to make, not because the world map looks familiar.

Use layers as arguments, not storage bins

Avoid creating thirty layers named “misc,” “new roads,” and “final final borders.”

Give each layer a decision purpose:

Layer Question it should answer
Relief / elevation What blocks movement or redirects weather?
Drainage Where does water collect and flow?
Settlements Why are people clustered here?
Routes What is the cheapest or safest connection?
Political control Who can tax, close, or defend the route?
Cultural regions Where do customs or languages change?
Story state What is true at a specific point in the narrative?

If a layer cannot answer a question, it may belong in the art file rather than the geography model.

Tool three: Natural Earth as a reference library, not a fantasy stencil

Natural Earth is a public-domain cartographic dataset designed for mapmaking. It provides vector and raster data at 1:10m, 1:50m, and 1:110m scales, including coastlines, rivers, populated places, administrative boundaries, and physical features.

For a fantasy creator, its best use is comparative.

You can study how many major rivers appear at different scales, how coastlines simplify as the map zooms out, how real mountain regions sit relative to cities, or how a world map visually suppresses small details that matter on a regional map.

You can also build a temporary Earth-based practice project in QGIS before building your fictional geography. This is useful because it teaches scale, labeling, and layer hierarchy with data that already has known relationships.

What you should not do is trace a real coastline, change the names, and call the geography original. Reference should teach structure, not donate a silhouette.

Natural Earth also documents disputed-boundary handling and different points of view. That is a useful reminder for fiction: a political border is not the same thing as a physical fact. Your canonical map may need to record who claims a line, who controls it, and which version a character sees.

Tool four: a projection test card

Many fantasy maps inherit one rectangular world-map look without asking what the map is for.

USGS explains the unavoidable trade-offs among projections. Shape, area, distance, and direction cannot all be perfectly preserved across a flattened globe.

A creator does not need to become a cartography specialist to use that insight. Make a one-page projection test card:

Map purpose: atlas overview / travel planning / naval navigation / classroom propaganda / sacred diagram.

Most important property: relative area / local shape / route direction / visual symbolism / easy comparison.

Acceptable distortion: what can be wrong without harming the story?

Danger zone: where does the projection exaggerate or compress features enough to mislead you?

Even if your final illustrated map ignores real cartographic conventions for artistic reasons, documenting that choice prevents accidental “facts” from leaking into travel times or territorial comparisons.

Tool five: the geography decision log

This is the least glamorous tool and one of the most important.

A decision log records why a feature exists.

Example:

Decision: City of Arel sits 30 km inland rather than at the river mouth.
Reason: the estuary is marshy and exposed to seasonal storm surge; the old fortified crossing is inland.
Consequences: port district requires a canal/road link; customs authority controls two nodes instead of one.
Story effect: smugglers can bypass the official inland checkpoint by using shallow-draft boats.
Revisit if: climate model, river course, or technology level changes.

That paragraph prevents a future editor from “fixing” the city by moving it to the coast and accidentally breaking three plot mechanisms.

A spreadsheet, markdown file, database, or note app all work. The format matters less than recording cause and consequence.

Tool six: a scale ladder

Fantasy maps often fail when a continent, kingdom, city, and dungeon all inherit the same level of detail.

Natural Earth’s multiple scales illustrate a basic cartographic principle: the information shown at one scale should not simply be shrunk from another.

Build three map products instead:

World view: major landmasses, major climate regions, political blocs, long-distance routes.

Regional view: passes, navigable rivers, secondary settlements, borders, agricultural zones.

Local view: streets, gates, bridges, elevation changes, sight lines, building access.

Then define what is intentionally omitted at each level.

This makes the map more believable because it behaves like information produced for a purpose rather than an omniscient encyclopedia dumped onto one image.

Tool seven: QGIS print layouts for repeatable exports

The QGIS documentation describes print layouts that can combine map views, legends, scale bars, text, images, and other layout items, then export to formats including image, SVG, and PDF.

For creators, the useful word is repeatable.

You can make one layout for an encyclopedia page, another for a writer’s-room reference, and another for a black-and-white print insert. When the underlying layers change, the map can be regenerated instead of manually rebuilt from screenshots.

That matters once a project has collaborators. The canonical map should not live only in one person’s flattened image file.

A practical stack for three creator types

Solo novelist

Use:

  • rough sketches;
  • one structured geography file;
  • a decision log;
  • a small number of export layouts.

Skip complex GIS analysis unless the story needs it. Your goal is continuity, not cartographic certification.

Worldbuilding team

Use:

  • QGIS or another layer-based map system;
  • controlled naming for layers;
  • a change log;
  • export layouts;
  • a shared glossary of place names and political states.

The hard problem is governance: who can change a border, rename a city, or alter a route?

Visual/IP project

Use:

  • geography model in a structured map tool;
  • art map in illustration software;
  • explicit handoff between the two;
  • source/asset log for real-world reference data;
  • style guide stating which distortions are intentional.

The production map and the lore map may differ visually. They should not contradict each other accidentally.

The anti-tool checklist

A tool is getting in the way when:

  • you are drawing detail that has no story or world function;
  • the file structure is more complex than the questions you ask;
  • collaborators cannot tell which map is canonical;
  • changing one border requires repainting the entire world;
  • distance numbers come from a projection or coordinate setup nobody understands;
  • real-world data is being copied rather than studied;
  • the map looks finished but the reasons behind settlements, routes, and borders are undocumented.

At that point, adding another plugin will not rescue the process.

A 90-minute setup that is actually reusable

First 20 minutes: write the five geography questions your project repeatedly asks.

Next 20: create only the layers needed for those questions.

Next 15: define units, scale, coordinate/projection assumptions, and naming rules.

Next 15: create a decision-log template and record five existing choices.

Final 20: make one clean export layout with title, legend only where needed, scale treatment, and version/date.

The output is not a finished world map. It is a map system that can survive revision.

That is the standard worth aiming for. A fantasy map becomes useful when a change in geography produces understandable changes in travel, politics, economics, culture, and story—not when the coastline has the most brush texture.

Sources

Related Reading