Short answer
A D&D battle map is usually planned as 5-foot squares. Choose the grid footprint for the encounter, then multiply columns and rows by the pixels per square required by your VTT or print workflow. For example, 30 x 20 squares at 70 px/square exports at 2100 x 1400 px.
A D&D battle map size is the number of playable grid squares plus the pixel or print dimensions used to deliver those squares to a VTT, printer, or table display.
From search intent to usable map
- Choose columns and rows from the encounter footprint before thinking about pixels.
- Multiply columns and rows by your chosen pixels per square to get export dimensions.
- Validate the exported PNG in Roll20, Foundry VTT, D&D Beyond Maps, or a print proof before session day.
Use the workflow in the editor
Create one map, save the source project, export a PNG, and test it in the table workflow you actually use.
Battle map export dimensions by square count and pixels per square.
| Grid squares | 70 px/sq | 100 px/sq | 140 px/sq | Best use |
|---|---|---|---|---|
| 20 x 20 | 1400 x 1400 | 2000 x 2000 | 2800 x 2800 | Small rooms, taverns, tight skirmishes |
| 30 x 20 | 2100 x 1400 | 3000 x 2000 | 4200 x 2800 | Roads, camps, flexible medium fights |
| 40 x 30 | 2800 x 2100 | 4000 x 3000 | 5600 x 4200 | Large arenas, streets, set pieces |
When RPGMapEditor.com is the right tool
- You want browser-first D&D or TTRPG battle map prep.
- You need grid-readable terrain, props, saved source maps, and PNG export.
- You are comfortable configuring tokens, walls, lights, fog, and platform automation inside the VTT.
When another tool may be better
- You need direct VTT scene packages, wall exports, or dynamic lighting data today.
- You mainly create polished world, regional, or atlas-style illustrations.
- You require a fully offline desktop workflow or a dedicated print-layout application.