70 px per square
Common default feel on many monitors.
VTT guides
Create Battle Maps for Roll20
Pick PNG dimensions that match Roll20’s grid, export from RPG Map Editor, import the image, then align cells—without fighting scale drift mid-session.
Quick answer: For Roll20, battle maps usually work best when exported as PNG files with a consistent pixels-per-square value such as 70 or 140 pixels per grid square. RPG Map Editor helps you create a map, align the grid, export the PNG, and import it into Roll20 as a playable encounter map.
Recommended PNG sizes
Think in pixels per square, not vague “high res”
Roll20 measures imported maps against its grid cell size. Formula: export width = columns × pixels per square, export height = rows × pixels per square.
140 px per square
Sharper tokens and zoom headroom; larger files.
Hex or offset grids
Roll20 supports alternate grids; your export still needs clean geometry. Verify in Roll20 after import—do not assume automatic detection from art alone.
| Map size (squares) | At 70 px/sq | At 140 px/sq |
|---|---|---|
| 20 × 20 | 1400 × 1400 px | 2800 × 2800 px |
| 30 × 30 | 2100 × 2100 px | 4200 × 4200 px |
| 40 × 30 | 2800 × 2100 px | 5600 × 4200 px |
Checklist
Grid alignment before you invite players
- Export dimensions: width and height divisible by your pixels-per-square target.
- Roll20 page settings: set cell size in pixels to the same per-square value you used in math.
- Offset: shift grid origin until a few squares track across the whole map.
- Token scale: pick default token size that matches art scale so range templates feel right.
Workflow
Export from RPG Map Editor → import into Roll20
- Finish terrain, props, and baked grid (if you want grid in the image—many tables prefer VTT-drawn grids instead).
- Use the editor’s PNG export; download the file.
- In Roll20, create or open a game, add a page, set the map image from upload.
- Open grid settings, match cell size to your export math, align offset, save.
- Add dynamic lighting and walls in Roll20—RPG Map Editor does not emit Roll20 wall data today.
Common mistakes
What usually breaks first-time imports
Odd pixel widths
When total pixels are not divisible by square count, Roll20 cannot land a perfect cell boundary—rounding errors stack across the map.
Double grids
Art with a heavy baked grid plus Roll20’s overlay can moiré or confuse players. Prefer one source of truth.
Assuming auto alignment
Always manually verify a few squares on each axis after import.
FAQ
Roll20 export FAQ
What resolution should a Roll20 battle map use?
Match pixels per square to Roll20’s grid after import—70 px per square is a common default; 140 px per square yields sharper art at larger file sizes. Export width and height should be multiples of your chosen pixels per square times map width and height in squares.
Does RPG Map Editor upload directly to Roll20?
No. You export a PNG from the editor, download it, then upload that file as a map image in Roll20 and align the Roll20 grid to the artwork.
Why does my grid look misaligned in Roll20?
Usually the image pixel dimensions do not match Roll20’s configured cell size, or the art grid is not square to the image edges. Re-export with clean square dimensions or adjust Roll20’s scale and offset until squares line up.
Can I use fog of war with these maps?
Yes—Roll20 handles fog and dynamic lighting on top of the imported image. Build the base map as a flat PNG, then add walls and lighting inside Roll20.
Related guides
Size maps before export, compare Foundry workflow, or jump into encounter-focused tooling.
Docs: Export your map · simple tabletop map editor · Pricing: Pricing · Features: Features