What RPG map-making tool should I use?

Start from the job, not the software

A combat encounter map, a political world map, a player-facing travel map and a hexcrawl are not different zoom levels of the same drawing. They answer different questions during play, and each question rewards a different kind of tool. When you browse map makers before naming the job, it is easy to buy a powerful illustration app for a problem that needed grid precision, or a precise dungeon builder for a problem that needed quick regional geography.

Name the information the map must carry while the session is running. Does it need to show distance and travel time, control movement square by square, track who controls which hex, or look convincing as a handout the characters found in world? The answer tells you whether you need geography layers, street editing, wall and door logic, hex bookkeeping, or VTT export more than it tells you which brand to download.

Quick chooser: match the job to the tool category

Tool features, export formats, and pricing change over time. Use these examples to identify the right category, then confirm the current feature or licence you need on the tool's own site.

Six questions that narrow the field

Run through these in order before you compare products. The first answer that feels settled usually decides the category.

• What kind of map are you making? Name one of the rows above as your primary use. If you are making two kinds of map for the same region, treat them as two jobs and make two simpler files rather than forcing one tool to do both.
• What must it communicate during play? A travel map communicates distance, terrain cost, and visible landmarks. A battle map communicates line of sight, cover, and who stands where this round. Write the questions the map must answer when a player points at it and asks what they can see or do.
• How much control versus automation do you want? Procedural generators such as Azgaar or Watabou give you a complete geography or street plan in seconds that you then edit. Illustration-first tools such as Inkarnate or Wonderdraft give you brush-by-brush control but need more time. Pick the balance that matches the hours you will actually spend, not the result you wish you had.
• Do you only need a background image, or structured VTT scene data? For an image-only workflow, prioritise the right grid dimensions and resolution, a PNG, WebP, or JPG export, and easy alignment in your VTT. For scene data, check for UVTT/DD2VTT or a VTT-specific export that your target VTT can import, with the wall, door, lighting, or line-of-sight metadata your scene needs. Dungeondraft and Worldographer 2025 support UVTT export; Dungeon Alchemist documents VTT exports with wall, light, and door data; Dungeon Scrawl currently offers UVTT export to Pro subscribers. An image is a backdrop; it does not carry that scene data by itself.
• Is it GM-facing, player-facing, or both? Decide whether you need a campaign reference map for operational truth, a player navigation map for information the characters could reasonably know, or an in-world map that may be incomplete, outdated, biased, or wrong. Keep secret routes and encounter keys on the reference map; show known roads, places from briefings or local knowledge, and rumours marked as uncertain when that matters. Plan whether you need separate versions or a handout with its own point of view.
• Which platform, licence, and workflow fit your needs? Browser tools often make it easy to start quickly, while desktop apps can offer offline use and deeper file or export control. Both categories may have free, paid, subscription, or Pro tiers; for example, Worldographer 2025 has a robust free version with optional Pro features. Check the current licence and export limits before committing.

Three map modes: campaign reference, player navigation, and in-world

A campaign reference map records what the campaign treats as operationally true: routes, keyed locations, hidden entrances, faction territory, and tactical information. A player navigation map shows what the characters can reasonably use to make decisions. That can include geography learned through upbringing, purchased maps, briefings, local knowledge, libraries, or guides, as well as places they have visited. An in-world map is an artefact that exists in the fiction; it may be incomplete, outdated, biased, stylised, based on rumour, or deliberately wrong.

Keep those jobs distinct when uncertainty matters. Put whatever the characters could reasonably know on the player-facing map, and visually distinguish uncertain or disputed information when that uncertainty matters in play. A handout can be valuable precisely because it is not an omniscient truth layer. Layers or separate annotations can help you produce different views, but a single shared image is not always the right answer.

Do not make the map more precise than the decisions it needs to support. Narrative travel may need only named routes and travel times; a hexcrawl needs explicit hex positions and keys; tactical combat needs spatial precision; a political map may need borders and control rather than accurate roads; and a treasure map may need recognisable landmarks rather than scale.

When not to make a detailed map

A finished map earns its keep only when it answers recurring questions at the table. For a single overland journey where the party follows a known road, a short list of travel times and a few roadside encounters does more than a fully painted continent. For a negotiation, chase, or social scene, a simple sketch of positions or a point-crawl with three to five nodes gives clearer choices than a street-accurate town plan.

Skip the detailed build when the location will not return, when you can describe the space faster than you can draw it, or when fog of war and player mapping are part of the point. A blank area with a scale bar, two named roads, and a note that says what the party has not yet seen often helps exploration more than a dense map that fills every hex before play begins.

Before you pick a tool

Answer these on paper first, then open the app store.

• Write one sentence for the map's job: what must a player or the GM be able to do with it during the session?
• Circle the row in the chooser table that matches that job and note what you need to prioritise.
• Decide whether your VTT workflow needs only a background image or structured scene data, and confirm the import format your table uses.
• Decide whether you need a campaign reference map, a player navigation map, an in-world map, or more than one of these modes.
• Set a time budget and check the current licence and export limits before committing to a tool.
• If no row in the table clearly matches, start with a quick sketch or point-crawl and draw the finished map only after the first session shows what information mattered.