Foundry VTT Battle Map Export

Direct answer

What this page answers

RPGMapEditor.com currently supports PNG battle map export that can be used as a Foundry VTT scene background. Walls, doors, lighting, and Universal VTT export are not shipped unless visible in the editor.

Export a PNG Map Start a Battle Map

Foundry VTT scene background style battle map with grid and interior terrain — Product preview: browser battle map workflow with terrain, grid, props, saves, and PNG export.

RPGMapEditor.com is independent and is not affiliated with or endorsed by Foundry VTT.

Product output

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.

Foundry scene background

Export a PNG battle map and use it as the scene background in Foundry VTT.

Grid size and origin

Match the exported pixels-per-square value in Foundry, then adjust grid origin until corners stay aligned.

Manual walls and doors today

Add walls, doors, lights, tokens, and regions inside Foundry after import; they are not exported from the map editor today.

Universal VTT is not shipped

Treat Universal VTT or richer scene metadata as planned work unless it appears in the shipped editor and docs.

Feature facts

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.

Build one map before comparing tools

Open the editor, make a focused encounter-scale map, save the source, then export once to see whether the workflow fits.

Open Editor Start a Battle Map

Workflow

How it works

This is the same practical sequence for core pages, comparison pages, VTT workflows, and template-style pages. The details change by map type, but the activation path stays measurable.

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.

Mid-page action

Move from research to a concrete map. A saved or exported map is the useful validation point.

Export a PNG Map Export a PNG Map

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

The goal is trust, not overclaiming. Use RPGMapEditor.com when the current browser and PNG workflow matches the job; choose another workflow when it does not.

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 PNG scene setup Use RPGMapEditor.com to make the scene art and Foundry to make the scene interactive.

Export the visual battle map as a PNG and note the square count and intended pixels per square.
Create a Foundry scene, set the PNG as the background image, and configure grid size and origin.
Trace walls, doors, lights, regions, tokens, and automation manually inside Foundry after the image is aligned.
Treat Universal VTT as planned work unless the shipped editor exposes it.

Export proof beats feature guessing

Export one PNG, import it into your actual table workflow, and check grid readability before a session depends on it.

Export a PNG Map Pricing

Internal links