Grid size and origin
Set the Foundry grid size from the export math, then adjust origin until the artwork and platform grid agree.
Foundry grid guide
Foundry Grid Alignment Guide for Battle Maps
Align RPGMapEditor.com PNG battle maps in Foundry VTT by matching scene dimensions, grid size, and grid origin to the exported map.
The map editor creates the image. Foundry remains responsible for the final grid, walls, doors, lighting, regions, tokens, and player-view validation.
Quick answer
RPGMapEditor.com creates the PNG battle map image; Foundry VTT handles grid alignment, origin, walls, doors, lighting, tokens, and automation after import.
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 and is not affiliated with or endorsed by Foundry VTT.
Create
What you can create
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.
Multi-corner validation
Verify alignment near multiple edges before drawing walls or placing tokens.
Scene setup boundary
RPGMapEditor.com creates the map image; Foundry handles walls, doors, lights, and interactivity.
Source map revisions
Save the RPGMapEditor.com project so you can re-export if alignment exposes a layout issue.
Included in the editor
- Current VTT output: PNG image export.
- Roll20 workflow: upload the PNG as map-layer art and align Roll20's grid.
- Foundry workflow: use the PNG as a scene background and set grid size/origin.
- VTT automation: walls, doors, lighting, fog, tokens, and automation are configured in the VTT.
- Universal VTT status: planned or not shipped unless exposed in the editor.
Current limitations
- PNG export is current; structured VTT package export is not shipped.
- Roll20 use means manual PNG upload and grid alignment, not direct API upload.
- Foundry use means PNG scene background setup, not exported walls, doors, lighting, or tokens.
- Always verify grid alignment in the actual VTT before session day.
Try it on a real map
Open the editor, make one focused encounter-scale map, save it, then export once to see whether the workflow fits your table.
Workflow
How it works
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.
Choose map size
Pick columns, rows, and grid scale from the encounter footprint before decorating.
Paint terrain
Block walkable ground, walls, roads, rooms, water, caves, or outdoor edges first.
Add props and stamps
Place cover, furniture, trees, rocks, doors, hazards, and landmarks only where they help play.
Add grid and text
Keep movement readable and add labels only when they clarify the session.
Save map
Save the editable source map to return later. Free accounts can save up to 3 maps.
Export PNG
Export a PNG for Roll20, Foundry VTT, print, projection, or campaign notes.
Start your map now
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.
Tradeoffs
Comparison and tradeoffs
Use this table to decide whether the current RPGMapEditor.com workflow matches the map job before investing more prep time.
| Factor | RPGMapEditor.com | Tradeoff |
|---|---|---|
| Map art | Creates visual map art and exports PNG | The VTT runs tokens, sheets, fog, lighting, walls, and automation |
| Grid setup | Helps plan square count and visual grid readability | Roll20 or Foundry handles final grid alignment after image upload |
| Advanced export | Universal VTT, walls, doors, and lighting are not shipped today | Some tools may offer richer packages; verify official support before switching |
Fit
Best for / Not best for
RPGMapEditor.com is built for playable encounter maps. If the job below is not yours, a different tool will serve you better.
Best for
- Game masters who need a clean PNG scene background for a virtual tabletop.
- Maps where grid math, square count, and import alignment matter more than automation.
- Teams comfortable configuring platform-specific tokens, walls, lights, and fog in the VTT.
Not best for
- One-click Roll20 upload or native Foundry scene JSON export.
- Dynamic lighting, walls, doors, tokens, or actor data generated by the map editor.
- Replacing the VTT itself; RPGMapEditor.com creates the map image.
Export
Export and use workflow
Foundry grid alignment workflow Set grid size from export math, then adjust grid origin before drawing Foundry-specific walls or lights.
- Export the PNG with predictable dimensions and record the intended pixels per square.
- Create or edit the Foundry scene, set grid size from the export math, and shift grid origin until lines match.
- After alignment, draw walls, doors, lights, tokens, and regions manually inside Foundry.
Test one export before game night
Export a PNG, import it into your usual table or VTT setup, and check grid readability before a session depends on it.
Related pages
Keep planning your map
FAQ
Foundry Grid Alignment Guide for Battle Maps FAQ
The questions DMs usually ask before starting a map like this.
How do I align a PNG battle map in Foundry VTT?
Create the scene, set the map image as the background, match grid size to the exported pixels per square, then adjust grid origin until lines align across multiple corners.
Why does Foundry grid alignment drift?
Drift usually means the image dimensions, square count, or grid size do not divide cleanly. Re-export with predictable dimensions or adjust the scene grid size and origin.
Does RPGMapEditor.com create Foundry walls?
No. Use RPGMapEditor.com for the PNG artwork and add Foundry walls, doors, lighting, tokens, and regions inside Foundry.
What should I test before the session?
Check grid alignment near the top-left, top-right, bottom-left, and bottom-right of the scene, then preview as a player before adding final automation.
What export does RPGMapEditor.com support today?
The current VTT handoff is PNG export. Use the exported image as Roll20 map-layer art or a Foundry VTT scene background.
Does RPGMapEditor.com upload directly to Roll20?
No. Export a PNG from RPGMapEditor.com, then upload and align the image inside Roll20.
Does RPGMapEditor.com export Foundry walls or doors?
No. Add walls, doors, lights, regions, tokens, and automation manually inside Foundry after PNG import.
Can I use the map as a Foundry scene background?
Yes. Export PNG, create a Foundry scene, set the image as the background, then configure grid size and origin.
Can I use the map in Roll20?
Yes. Upload the PNG to the map layer, set the Roll20 page dimensions, and align the Roll20 grid to the image.
What grid size should I use?
Choose square count first, then export at a consistent pixels-per-square value so the VTT grid can match the image.
Does Universal VTT export work today?
No. Treat Universal VTT, walls, doors, and lighting export as planned unless the shipped editor exposes those options.
Is PNG enough for VTT play?
PNG is enough for the visual map background. Tokens, fog, lighting, walls, and automation remain in the VTT.
Can I print the exported map?
Yes. Export PNG and print at the size your table needs after checking grid scale and image readability.
What should I test before a session?
Import one exported PNG into your actual VTT, check grid alignment at multiple corners, and verify text and props remain readable.
Make the map
Open the editor, build the encounter you were planning, save it, and export a PNG when it is ready for your table.