Paint terrain, place readable props, tune a tactical grid, export a PNG, and keep campaigns organized—without turning Photoshop or a generic image editor into your weekly prep bottleneck.
Quick answer: RPG Map Editor’s features center on browser-based battle map prep—terrain painting, stamps and props, tactical grids, saved projects, and PNG export for Roll20 or Foundry. Use this page to map each prep job (blocking terrain, dressing scenes, exporting) to the controls that exist in the shipped editor today.
Each block states the capability, why it matters at the table, and the prep problem it removes.
What it does: broad brushes for grass, stone, water, floors, caverns—define the walkable encounter space before details.
Why DMs care: players grasp “where we can stand” in seconds, so you spend voice time on fiction, not interpreting muddy ground.
Removes: rebuilding base layers in a raster tool every time the story shifts.
What it does: stamps for doors, tables, cover, trees, rubble, landmarks—repeatable dressing on top of terrain.
Why DMs care: props encode encounter intent (chokepoint, ambush line, barricade) without you narrating geometry from a blank JPEG.
Removes: dragging individual PNGs onto canvas in a general-purpose design tool with no map-native library.
What it does: tactical grid overlays while you edit so spacing for movement, range, and lanes stays honest.
Why DMs care: fewer “is that 5 feet or 10 feet?” arguments mid-combat; faster rulings on line and cover.
Removes: exporting a beautiful image that lies about scale when imported to a VTT.
What it does: PNG export sized for virtual tabletops, print references, or projector use—verify final alignment in your VTT.
Why DMs care: the handoff is predictable: image + your platform’s grid settings, not a bespoke pipeline every week.
Removes: flattened-but-unplayable art that looks great in a portfolio but breaks at the table.
What it does: account-backed JSON snapshots with autosave cues and manual save—reopen the same map when your players pivot.
Why DMs care: campaigns evolve; editable source beats a stack of one-off renders you cannot revise.
Removes: versioning chaos—sloppy map_final3_really.png sprawl across Downloads.
What it does: per-account map list with clear free vs paid save limits (see Pricing).
Why DMs care: multi-arc games need a library, not a pile of untitled tabs.
Removes: scattering files across machines with no shared backing store.
What it does: the Pixel Snapper tool turns uneven sprites, icons, props, and tile swatches into grid-snapped PNGs.
Why DMs care: imported pixel-art details look cleaner when their source pixels line up instead of drifting.
Removes: hand-fixing tiny AI or procedural assets one square at a time.
Other tools are brilliant at illustration or layout in general—we focus on encounter readability, reusable projects, and repeatable export. No shade; just scope.
Great for comps, slow for weekly encounter maps: manual layers, no battle grid truth, heavy files, and no autosave into a campaign library unless you build it yourself.
Fine if you always prep on one machine. Browser workflow means your maps follow the account—handy for club machines, travel, or swapping rigs between home and game space.
Some VTTs sketch basic shapes, but artful terrain + prop libraries + export flexibility often still wants a dedicated mapper before you import.
If the workflow holds for forest ambush, tight tavern fights, and dungeon delves, it will stretch to your homebrew arcs.
Readable trees, lanes, sight lines outdoor combats demand.
Interior movement lanes when roleplay snaps to initiative.
Chokepoints and room reads for fog-of-war style reveals.
Regional readability for investigation or travel framing.
If you live in browser prep, prioritize one real encounter—not marketing screenshots.
Start with the RPG map editor comparison hub, then see the Dungeon Scrawl comparison, browser vs desktop guide, modern RPG map editor alternative page, Inkarnate alternative notes, or the Inkarnate vs RPG Map Editor table.
Dive into battle maps, dungeon maps, fantasy maps, or niche D&D workflows. Guides: how to make a battle map, Roll20 import guide, Foundry import guide, size guide.
Use the moderated forum for workflow questions before you lock a campaign process.
RPG Map Editor is strongest when the output is a real battle map a DM can open, save, export, and use at the table. It is deliberately not positioned as a full VTT automation suite or world-map cartography app.
You can create fantasy RPG maps for encounters, dungeons, towns, wilderness scenes, and tabletop handouts using terrain painting, stamps, grids, labels, saved projects, and image exports.
Yes. The editor is designed for DMs who need readable encounter maps with terrain, cover, props, grids, and a practical export path for game night.
Yes. Use PNG exports for VTT uploads, table handouts, or session notes. Always verify grid scale and alignment inside your VTT.
Yes. The workflow combines terrain brushes with stamps and props so you can dress rooms, roads, caves, taverns, ambush sites, and other play spaces.
Yes. RPG Map Editor runs in a modern desktop browser, so you can build maps without installing a desktop application.
It can be, depending on your workflow. RPG Map Editor focuses on browser-based tabletop prep, saved projects, practical grids, and exports for play.
Paint playable terrain inside five minutes, stamp only props that change tactics, reconcile the tactical grid visually, autosave, export PNG—most skirmish spaces land in fifteen to thirty minutes once the muscle memory sticks.
It replaces general-purpose layering workflows for tabletop encounters. If you already live in raster tools, you might still polish hero art there—but repeatable grid combat maps rarely need it.
Paint the ground, stamp props, walk the grid mentally, export, import to your VTT—if it fails, you learn before session zero.
