Configure your maps and scenes before the session starts, assign tokens to every player character and key NPC, set up fog of war or dynamic lighting on encounter maps, preload music or ambient sound, and test the full session from a player perspective before your group joins. The biggest time saver is building a reusable campaign template so setup time decreases with every session you run.
Running games on a virtual tabletop is a different skill set from running games at a physical table. The storytelling, pacing, and improvisation are the same. The prep work is not. A VTT session that runs smoothly is almost entirely the result of setup completed before the first player logs in.
This practical VTT session prep framework covers maps, tokens, lighting, audio, session flow, and the reusable habits that make each adventure faster to prepare than the last.
Why is VTT prep different from in-person prep?
In-person prep centers on notes, encounters, and narrative. VTT prep adds a technical layer. Before a single die roll happens, you need scenes configured, maps imported and grid-aligned, tokens placed, lighting set, and connections tested on the devices your players use.
The good news is that most of this work is front-loaded into the first few sessions of a campaign. Reusable assets, saved scenes, and established templates can make every later session easier to prepare.
For a typical three-to-four-hour session, two to four fully configured battle map scenes is a practical target. Prepare tactical maps for moments where positioning, terrain, and movement affect play.
Step 1: Which scenes should you plan before opening your VTT?
Plan the session route
The most effective prep starts away from the computer. Before opening Foundry VTT, Roll20, or Owlbear Rodeo, write a simple list of every location your players might visit during the session.
Be realistic about which locations need a battle map. A throne room conversation, travel montage, or dream sequence may work better with a static illustration, ambient sound, or no visual at all. Save detailed map prep for encounters where the battlefield changes player decisions.
| Scene Type | Best Visual | Prep Priority |
|---|---|---|
| Combat or tactical exploration | Configured battle map | High |
| Social encounter | Illustration or simple room | Medium |
| Travel, montage, or dream | Static art or ambient scene | Low |
Step 2: How should you import and configure battle maps?
Configure maps before session day
Map configuration is usually the most time-intensive part of VTT prep and the part most likely to be rushed. Import maps, align the grid, and test each scene at least one day before the session.
In Foundry VTT, set the scene dimensions to match the image file, calculate the grid size from the image width and square count, and confirm alignment before placing tokens. In Roll20, set the page dimensions to match the grid count, place the image on the map layer, and verify alignment in the page settings.
Use the gridless map file inside your VTT. The platform draws its own grid, while a gridded image can create a distracting double-grid effect.
The Dark Encounter Battle Maps Pack and Shadows Beneath the Tavern Map Pack are both built at 4096 by 4096 pixels on a 30 by 30 grid. Because the configuration values stay consistent, setup becomes faster after the first import.
Step 3: Which tokens should you prepare?
Prepare every likely creature
Tokens are one of the clearest signs that a session is ready. A configured token with the right portrait, name, and hit point bar creates more immersion than a generic placeholder labeled “Monster 3.”
Prepare tokens for every creature the party is likely to encounter, including player characters, named NPCs, and combatants. Set each hit point bar to the creature’s maximum HP and decide which names should be visible to players.
Ask players for token images before the campaign starts, then keep those files in a reusable asset library. For monsters and NPCs, use your VTT’s included assets or compatible token packs and modules.
Step 4: How much fog of war should you set up?
Control what players can see
Fog of war is one of the most impactful tools available to a VTT dungeon master. When players cannot see the entire map, they explore more cautiously and make decisions with incomplete information.
Your available controls depend on the platform and account tier. Foundry VTT supports walls, token vision, and lighting. Roll20 offers dynamic lighting on eligible paid plans, while manual reveal tools provide a simpler alternative.
For encounter-heavy sessions, draw walls while importing the map. A standard dungeon with five to eight rooms may take roughly ten to fifteen minutes to configure, depending on its complexity, but that work can be reused whenever the scene returns.
Step 5: How should you prepare music and ambient sound?
Set the tone before players arrive
Ambient sound and music establish tone immediately. A dungeon corridor with a low rumble and distant dripping water feels different from the same scene in silence.
Build a simple reusable library with three to five tracks for each common environment: dungeon, tavern, wilderness, urban exploration, and combat. Assign tracks to scenes where your platform supports it, then confirm volume levels from the player perspective.
For tavern scenes, a warm background track paired with the Gilded Mug Tavern or Velvet Crown layouts from the Shadows Beneath the Tavern Map Pack can establish the social encounter’s mood before a word of dialogue is spoken.
Step 6: What belongs on a VTT pre-session checklist?
Run the same check every time
The most consistent dungeon masters use a short checklist before every session. It does not need to be complex. It only needs to cover the issues most likely to interrupt play.
- All encounter scenes are imported, grid-aligned, and tested.
- Player character tokens are placed in the starting scene.
- Hit point bars and visible names are set on creature tokens.
- Fog of war or dynamic lighting is active on encounter maps.
- Music and ambient sound are assigned at appropriate volume levels.
- The campaign has been tested from a player perspective.
Running through this list takes only a few minutes. Discovering a misaligned grid, hidden token, or broken audio source after the group joins takes longer and interrupts the session.
Step 7: How do you test a VTT session from the player perspective?
See what your players will see
This is the step many dungeon masters skip, and it catches some of the most disruptive problems. Before players join, open the campaign with player-level permissions and inspect the starting view.
Confirm that the correct scene is active, the view is centered, restricted areas remain hidden, and tokens can move and snap correctly. In Foundry VTT, log in as a player user in another browser or private window. In Roll20, use a player account or the platform’s player-view controls to verify the experience.
Move one player token through the opening scene, reveal one area, trigger one audio track, and open one handout. This short rehearsal verifies the parts of the session your players will touch first.
How do you build a reusable VTT campaign template?
The long-term goal of VTT prep is to build a campaign template that makes each new session faster. This preconfigured game file should include player tokens, organized asset folders, preferred lighting and fog settings, and a tagged music library.
When the next session approaches, duplicate or reopen the template, import only the maps and encounters needed for that adventure, and leave the foundational setup in place. Building the template may consume much of the first prep session, but later sessions focus on new content instead of repeated technical work.
Why do some dungeon masters overprepare their VTT sessions?
Smooth sessions do not require preparing everything. They require preparing the elements players interact with most often. Map configuration and token setup are high-return tasks because poor setup creates friction throughout an encounter. Elaborate notes for an NPC the party may never meet provide less immediate value.
Invest in the technical foundation early, reuse what works, and protect more of your prep time for the creative decisions that drive the campaign.
Explore gridless 4K battle maps built on consistent dimensions for faster scene setup across your campaign.
Explore Battle Maps →Frequently Asked Questions
An established campaign may take one to two hours to prepare once a reusable template is in place. The first session often takes longer because player tokens, asset libraries, and baseline scene settings still need to be configured.
Map configuration is usually the highest priority. A misaligned grid, missing fog of war, or incorrectly layered image affects the entire encounter. Token setup comes next because players interact with tokens continuously during tactical play.
Build a reusable campaign template with player tokens, organized asset folders, and default scene settings. Use map packs with consistent pixel dimensions and grid counts so you do not need to calculate new configuration values for every import.
No. Social encounters, travel sequences, and narrative moments may work better with a static illustration, ambient sound, or no visual. Battle maps are most valuable when positioning and terrain affect player decisions.
Dynamic lighting updates a player’s line of sight as tokens move and blocks vision behind configured walls. It can improve exploration and immersion, but it is not required. Manual fog tools can provide similar control with more hands-on management.
Open the campaign with player-level permissions in a separate browser or private window. Confirm that the starting scene is active, hidden areas remain concealed, tokens move correctly, the grid aligns, and audio plays at a comfortable level.
Sources
- Foundry VTT: Scenes Documentation
- Foundry VTT: Ambient Sounds
- Roll20: What Is Dynamic Lighting?
- Roll20: Dynamic Lighting Checklist
