Battle Map Export Settings for VTT and Print

Direct answer

What this page answers

Battle map export settings in RPGMapEditor.com should be chosen from square count, pixels per square, grid visibility, PNG dimensions, and the destination workflow.

Export a PNG Map PNG Export for VTT

Battle map export settings preview with square-grid interior map — Product preview: browser battle map workflow with terrain, grid, props, saves, and PNG export.

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.

Square count

Start from the encounter footprint: columns, rows, rooms, lanes, and how much empty movement space the fight needs.

Pixels per square

Pick a consistent pixel scale that balances crisp art with upload size and table performance.

Grid visibility

Export a visible grid for print or projection, or avoid a double grid when Roll20 or Foundry will draw the active grid.

Final validation

Open the exported PNG in the target workflow and verify readability before relying on it during a session.

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 PNG Export for VTT

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

Choose export settings from the destination Square count, pixels per square, PNG dimensions, and grid visibility decide whether the exported map is usable.

Pick square count from the encounter footprint instead of starting from arbitrary pixel dimensions.
Choose pixels per square and grid visibility based on the destination: Roll20, Foundry, print, projection, or notes.
Export PNG, test it in the actual destination, and re-export from the saved source if readability or alignment fails.

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