Manual map editor
RPGMapEditor.com is for painting and revising a specific battle or dungeon map rather than rolling a procedural result.
RPGMapEditor.com is a Donjon alternative only for one specific job: manually creating and revising playable battle maps and dungeon maps in the browser with saved maps and PNG export.
Use this comparison to understand where the other tool may be better for random generators and where RPGMapEditor.com is better for editable encounter art, props, grids, and VTT-ready PNG output.
RPGMapEditor.com is a Donjon alternative for users who want editable browser battle maps and dungeon maps with saved source projects and PNG export, not random RPG generation.
Account policy: new accounts need an active Studio subscription ($3/month) to use the editor. Accounts created before Aug 21, 2026 keep their free plan. Details on the pricing page.
RPGMapEditor.com is independent. Trademarks belong to their respective owners; Donjon is named only for comparison.
Use RPGMapEditor.com when the result needs to become an actual tabletop map: opened in the editor, edited around play, saved for later, exported as PNG, and reused when the campaign changes direction.
RPGMapEditor.com is for painting and revising a specific battle or dungeon map rather than rolling a procedural result.
Use terrain, props, grid, labels, saved maps, and PNG export when the table needs playable scene art.
Donjon-style tools are often better when the job is random generation, quick inspiration, or RPG utility output.
RPGMapEditor.com exports PNG maps today; VTT automation and procedural room generation are outside the current product.
Open the editor, make one focused encounter-scale map, save it, then export once to see whether the workflow fits your table.
The same six steps whether you are building a dungeon, a wilderness ambush, or a tavern brawl. The details change by map type; the workflow does not.
Pick columns, rows, and grid scale from the encounter footprint before decorating.
Block walkable ground, walls, roads, rooms, water, caves, or outdoor edges first.
Place cover, furniture, trees, rocks, doors, hazards, and landmarks only where they help play.
Keep movement readable and add labels only when they clarify the session.
Save the editable source map to return later. Free accounts can save up to 3 maps.
Export a PNG for Roll20, Foundry VTT, print, projection, or campaign notes.
Pick a map size, block out the terrain, and you will have a playable layout in minutes. Save or export it when the tactical read looks right.
Use this table to decide whether the current RPGMapEditor.com workflow matches the map job before investing more prep time.
| Factor | RPGMapEditor.com | Tradeoff |
|---|---|---|
| RPGMapEditor.com is better for | Fast browser battle maps, saved encounter sources, grid readability, and PNG export | Depends on competitor; may be better for world maps, marketplaces, or offline workflows |
| Competitors can be better for | Focused tactical encounters rather than broad cartography | World/region/city maps, polished illustration, larger asset ecosystems, or mature VTT packages |
| Fair test | Build one encounter, revise it once, save it, export PNG, and test VTT alignment | Run the same test and compare output, revision time, and real table fit |
RPGMapEditor.com is built for playable encounter maps. If the job below is not yours, a different tool will serve you better.
Manual map editor vs random generator RPGMapEditor.com creates saved source maps and PNG battle maps. It does not claim procedural dungeon generation or random RPG utility output.
Export a PNG, import it into your usual table or VTT setup, and check grid readability before a session depends on it.
The questions DMs usually ask before starting a map like this.
It can be a Donjon alternative when the task is manually creating and revising playable RPG battle maps or dungeon maps. It is not a replacement for random RPG generators.
Choose a generator-style tool if you want random dungeon layouts, encounters, names, treasure, calendars, or other generated RPG utilities instead of drawing the map yourself.
Use RPGMapEditor.com when you want a browser editor with terrain, props, stamps, text, grids, saved source maps, and PNG export for a map you can visually revise.
No. It is a manual map editor. You choose the size, paint terrain, place props, add grid/text, save the map, and export PNG.
Yes. Export PNG for Roll20 upload or Foundry VTT scene backgrounds, then set grids and VTT-specific walls, doors, lights, and tokens inside that platform.
It is best at fast browser-based battle maps for D&D and TTRPG sessions: terrain, props, grid, saved maps, and PNG export.
Competitors can be better for world maps, regional maps, illustration-heavy cartography, marketplaces, offline editing, or native VTT package exports.
Yes. The primary workflow is browser-based and aimed at session-ready battle map creation.
Yes. Signed-in users can save editable maps. Free accounts can save up to 3 maps.
Yes. PNG export is the current output for VTTs, print, projection, and notes.
No. RPGMapEditor.com creates the map image; Roll20, Foundry, or another VTT handles tokens, walls, lights, fog, and automation.
Build the same small encounter in each tool, revise it once, export it, and test grid alignment in the VTT you actually use.
No. Use RPGMapEditor.com for battle maps and encounter scenes, not large-scale world, region, or city cartography.
No for the browser workflow. Use a desktop app only if offline editing or local asset workflows matter more.
Upgrade when you need more than the Free plan's saved-map limit or paid workflow features such as share links.
Open the editor, build the encounter you were planning, save it, and export a PNG when it is ready for your table.