Short answer
RPGMapEditor.com exports visual PNG battle maps that can be used as Foundry scene backgrounds. Set scene dimensions and grid size in Foundry after import, then add walls, doors, lights, and tokens inside Foundry. Universal VTT or wall/door export should be treated as planned unless it exists in the codebase.
A Foundry VTT battle map export is a map image, and sometimes scene metadata, prepared so Foundry can display it with an aligned grid and optional Foundry-authored walls, doors, and lighting.
RPGMapEditor.com is independent and is not affiliated with or endorsed by Foundry VTT.
From search intent to usable map
- Export a clean PNG from the finished visual map.
- Create a Foundry scene, set the image as the background, and enter the grid size that matches the export math.
- Add walls, doors, lights, regions, tokens, and automation inside Foundry after the background is aligned.
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.
Foundry VTT support status for RPGMapEditor outputs.
| Feature | Status | What to do |
|---|---|---|
| PNG background | Works today | Export a flat PNG and use it as scene art |
| Grid math | Works today | Set Foundry grid size and origin after import |
| Walls and doors | Not exported today | Author these inside Foundry |
| Universal VTT | Not available unless implemented | Treat as planned, not shipped |
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.