Best for
Fast DnD and TTRPG encounter maps, readable tactical grids, browser editing, saved source projects, and PNG export for Roll20, Foundry VTT, print, or sharing.
Battle map maker
Battle Map Maker for D&D and TTRPG Sessions
Terrain painting, stamps, tactical grid, saved maps, and PNG export for encounter prep in your browser—then import to Roll20, Foundry, or use at the table.
A battle map maker helps Dungeon Masters create tactical encounter maps with terrain, props, grids, and export settings for virtual tabletop or in-person play. RPG Map Editor focuses on fast browser-based map creation, letting you paint terrain, place objects, align a grid, and export a playable PNG map.
About RPG Map Editor
RPG Map Editor is a browser-based DnD and TTRPG map maker for creating battle maps, dungeon maps, and fantasy RPG maps online.
Paint terrain, place stamps, align a tactical grid, save projects to your account, and export PNG snapshots for Roll20, Foundry VTT, or in-person play. No installer — runs in a modern desktop WebGL browser.
Start in one session
Create a free account, open the editor, and export one encounter map at the size your table uses.
Basics
What is a battle map maker?
It is software for tactical encounter layouts: you show where creatures can move, what blocks line of sight or movement, and how large each square is, then export an image your VTT or physical table can use. RPG Map Editor targets browser-based prep—terrain painting, props, grids, account saves, and PNG export—without claiming native export of Roll20 walls or Foundry lighting data. If you arrived from a search for an older “RPG Map Editor 2” workflow, read the honest browser RPG map editor positioning page first.
Not best for
Native Foundry scene export, Roll20 dynamic lighting export, automated walls, token data, or broad world-atlas illustration.
Audience
Who uses battle map makers?
Dungeon Masters and game masters running grid-based TTRPGs—especially D&D-style combat—who need readable spaces for tokens or minis. GMs who prep on a desktop browser and repeat a save → export → play loop also benefit when a map-first editor replaces ad-hoc image tools.
Speed
Why browser-based map prep is faster
You skip installing a separate native map suite for the shipped workflow: open a project, paint walkable terrain first, stamp only props that change tactics, keep the grid visible while editing, autosave on cadence shown in the product, and download PNG when the read is clear. That loop stays in one tool built for squares and encounter scale instead of general-purpose layers.
Workflow
How to create a battle map in 5 steps
Ten minutes is a discipline target for a small skirmish: block terrain, one chokepoint, minimal props, grid check, export. Larger set pieces take longer; the order below stays the same.
Step 1: choose map size
Pick width and height in squares for the encounter you will actually run. For fifth-edition style tables, start with D&D battle map size guidance so export pixels line up with your VTT plan.
Step 2: paint terrain
Block grass, stone, water, and interior floors so negative space reads before detail. Corridors and rooms should be obvious at a glance on a laptop screen.
Step 3: add paths, water, walls, or cover
Use terrain and stamps to show movement lanes, swim or difficult terrain, opaque walls, and objects that grant cover—only what changes decisions at the table.
Step 4: place props and tactical objects
Doors, rubble, trees, furniture, and landmarks belong after layout is readable. Skip decoration that does not touch movement or line of sight.
Step 5: align the grid
Keep the tactical overlay on while editing so exports do not surprise you at upload time. Reconcile spacing before you commit to final PNG dimensions.
Step 6: export PNG for VTT or tabletop play
Export raster PNG at dimensions that match your pixels-per-square math, then import into your VTT or print for in-person play. See platform notes below.
Step-by-step narrative: How to make a battle map · D&D framing: D&D map maker
Try the workflow
Build one map you will run this week, export once, and align it in your VTT before the session.
Roll20
Roll20 export notes
RPG Map Editor does not upload directly to Roll20. Export PNG, add it as a map image, then set Roll20’s cell size and offset until the platform grid tracks your art. Common clarity targets are 70 px per square or 140 px per square—see the Roll20 battle map export guide for formulas tied to map width in squares.
Product workflow
How to do it in RPGMapEditor
Open RPGMapEditor, choose a blank map or demo, paint the terrain that defines movement, place cover and props that affect decisions, keep the grid readable, save the source map, then export a PNG for Roll20, Foundry VTT, print, or sharing.
Foundry VTT
Foundry VTT export notes
Import the PNG as a scene background, configure grid size in pixels to match your export, then shift grid origin until squares line up. Walls, doors, and lighting are added inside Foundry after import—not exported from the map editor today. Full checklist: Foundry VTT battle map export guide.
Pitfalls
Common battle map mistakes
Decorating before layout
Props before readable terrain make maps noisy on small screens and slow token play.
Ignoring the grid until export
Late grid fixes often mean repainting edges; check alignment while terrain is still easy to adjust.
Guessing VTT scale
Write down pixels per square and square count before upload so movement math stays honest.
Use cases
Example battle map use cases
- Tavern brawl — tight furniture lanes, bar cover, door width for escapes.
- Forest ambush — trees for partial cover, paths that reward positioning.
- Boss arena — open center with ring hazards or pillars so melee and ranged both have choices.
- Urban chase — long axis with obstacles every few squares to break line of sight.
Visual reference: Example maps showcase
Guides
Related guides
Jump to the pages that match your next action—VTT import, sizing, or product limits.
D&D encounter prep
D&D map maker for fifth-edition style language and encounter focus.
Map dimensions
D&D battle map size guide for squares, feet, and export pixels.
Roll20
Roll20 battle map export for import and alignment.
Foundry
Foundry VTT battle map export for scene setup.
Tutorial
How to make a battle map for build order and restraint.
Product
FAQ
Battle map maker FAQ
What is a battle map maker?
Software for tactical encounter layouts: terrain, props, grids, and exports so players and VTTs can run combat without redrawing the scene each session.
Can I make D&D battle maps in a browser?
Yes. RPG Map Editor runs in a desktop WebGL-capable browser with terrain painting, stamps, saved maps, and PNG export—no separate native install for the shipped editor workflow.
What size should a battle map be?
Most D&D-style tables use a 5-foot square grid. Pick square counts that fit the encounter (often 20×20 to 40×30), then match export pixel width and height to your VTT pixels-per-square plan—see the D&D battle map size guide on this site.
Can I export maps for Roll20?
Yes. Export PNG from the editor, upload the image as a map in Roll20, then align Roll20’s grid to the art. Use the Roll20 battle map export guide here for pixels-per-square targets.
Can I export maps for Foundry VTT?
Yes. Import the PNG as a scene background in Foundry, set grid cell size in pixels to match your export math, then shift the grid origin until it tracks the map. See the Foundry VTT battle map export guide on this site.
Do I need to install software?
No separate desktop map app is required for the shipped workflow: create and export in the browser. Your VTT is still a separate product where you import the PNG and configure walls, fog, and lighting.
Is RPG Map Editor free to try?
Yes. The Free plan includes core editor tools, up to three saved maps, PNG export, and forum access—enough to run a real session map through export before you decide on paid options.
Start free
Create an account, open the editor, and run one encounter through export before your next session.