Studio unlocks the complete browser editor, unlimited cloud maps, editable project JSON, public links, and PNG export for Roll20, Foundry, print, or tabletop play.
RPG Map Editor · FAQ
Answers for your
next map.
Clear guidance on Studio, battle map exports, virtual tabletops, browser requirements, privacy, and the workflows the editor supports today.
Browse the answers · 8 topics
The useful
short version.
We keep the answers specific so you can decide whether the workflow fits your table before you sign in.
Personal and table use are straightforward. For resale, publishing, or bundled commercial distribution, we're waiting to publish a clear license instead of hand-waving. That policy lands before any marketplace or paid commercial plan.
No. The product is aimed at working Game Masters, not trained illustrators. Paint terrain, stamp props, export, and get on with session prep.
The editor is desktop-first today. It expects a modern browser with WebGL2, a keyboard, and enough room for the canvas chrome. Touch support is on the public roadmap, but it is not where we'd steer you yet.
Yes. PNG export is built in. The current browser workflow also writes VTT-ready sidecar metadata; richer VTT packages stay on the roadmap until they are verified.
The canvas stays responsive while you paint, stamp, measure, and undo—session prep that feels immediate, not a menu tree with a brush attached.
Each map is stored in your account as a JSON snapshot. Sessions use HTTP-only signed cookies, passwords are hashed with Argon2, and maps stay private until you explicitly share them. See the Privacy Policy for the longer version.
Not publicly yet. If you need automation or publishing hooks, send the use case through feedback; that helps us shape the eventual API instead of shipping one nobody actually needs.
Still deciding?
Bring the real
question.
Tell us what you are trying to build and we will point you to the right workflow.
Contact support ↗