Roll20 Dynamic Lighting Masterclass: Setting Up Doors, Walls, and Light Sources Fast

The map is loaded. The tokens are ready. The players join the game, step through the first dungeon doorway, and immediately see half the room beyond the wall because one tiny Dynamic Lighting line never quite reached the door frame.

Or the opposite happens. The fighter opens a door that looks open on the map, but an invisible barrier still blocks vision because the GM traced a solid wall through the doorway twenty minutes earlier.

Roll20 Dynamic Lighting is powerful because it turns a static battle map into an explorable space. It is also easy to overbuild. DMs often spend more time tracing walls than preparing the encounter itself, then discover that excessive barrier lines, too many vision-enabled tokens, or badly placed doors create more problems than immersion.

The goal is not to reproduce every pixel of the architecture. The goal is to build the simplest lighting layer that produces the correct player experience.

What Does Roll20 Dynamic Lighting Actually Need?

A functional Dynamic Lighting page only needs a few systems working together.

Roll20's current setup flow separates map building from token preparation. Build the barriers and lighting behavior first. Then configure the tokens that will interact with it.

That order matters because troubleshooting becomes much easier. If the map geometry works with a single test token, you know later problems are probably token settings rather than the entire page.

How Do You Turn Dynamic Lighting On Quickly?

On Roll20's latest VTT engine, Dynamic Lighting controls are accessible from the left toolbar. You can also use the traditional Page Settings method by opening the Page Toolbar, hovering over the page, selecting its settings, and opening the Dynamic Lighting tab.

Turn Dynamic Lighting on before you start drawing walls.

From there, decide whether the environment needs Daylight Mode, individual light sources, or a combination of both.

Explorer Mode can preserve previously explored areas in a muted state. It is useful in sprawling dungeons where players should remember where they have been without seeing what is currently happening there.

If you are running a horror session, pair these settings with the encounter pacing ideas in our guide to running horror campaigns with lighting, maps, and pacing.

What Is the Fastest Way to Draw Walls?

Trace gameplay geometry, not artwork.

Switch to the Dynamic Lighting layer, select the drawing tools, and create barriers along the parts of the map that should block light and vision.

A common beginner mistake is following every curve, broken brick, decorative pillar edge, and irregular stone texture. That creates dozens or hundreds of tiny line segments that players will never notice.

Instead, simplify.

For a rectangular dungeon room, four lines are usually enough. For an irregular cave, use longer polygon segments that approximate the cavern shape rather than tracing every rock.

Roll20 also recommends building complex maps from smaller individual barrier lines rather than one enormous shape. That makes later editing easier because you can move or replace one section without rebuilding the entire dungeon perimeter.

Use Transparent Barriers for Movement-Only Obstacles

Transparent barriers let vision and light pass through while still blocking movement when Restrict Movement is active.

That makes them useful for railings, thick vegetation, counters, low walls, furniture boundaries, and other terrain the characters can see across but cannot simply walk through.

Use One-Way Barriers for Elevation Tricks

One-way barriers allow vision from one direction while blocking it from the other. They can represent balconies, cliff edges, stairwells, elevated platforms, and other locations where one side has a visual advantage.

Do not use them everywhere. They are most valuable when elevation is mechanically important, especially in encounters built around vertical combat, climbing, falling, and flying.

How Should You Set Up Doors Without Light Leaks?

Do not draw a continuous wall through a doorway if you plan to use Roll20's interactive door component.

Instead, stop the wall at one side of the doorway, leave a gap, then continue the wall on the other side. Place the door component into that gap.

Roll20's current door component supports open and closed states, locked doors, and secret doors. Secret doors can remain hidden from players until you want them revealed.

On the latest VTT engine, doors and windows can also be copied, pasted, and multi-selected. That is a major time saver on maps containing repeated architecture. Configure one standard dungeon door, duplicate it across the map, then only modify the few that need to be secret or locked.

Restrict Movement should be enabled when doors and windows are being used as physical boundaries. Roll20 prompts for this because those components need movement restriction to behave as intended.

How Are Windows Different From Doors?

Windows are designed to allow line of sight while controlling movement.

That makes them useful anywhere characters should be able to see a room before they can enter it. A tavern window can expose figures moving inside. A prison cell window can reveal the creature behind the door. A manor window can create a clean heist route once a character opens it.

Like doors, windows should sit in deliberate gaps between normal wall barriers. Roll20 notes that the components should be placed beside barrier lines rather than directly on top of continuous barriers.

What Is the Fastest Way to Add Light Sources?

Use Roll20's Place Light tool for environmental lights instead of building every torch from scratch.

The current Place Light tool creates a light-emitting token with 20 feet of Bright Light and another 20 feet of Low Light. You can then edit that token's light settings like any other token.

That means a fast dungeon workflow can be surprisingly simple:

1. Place one light token where the first torch or lamp belongs.
2. Adjust its radius and direction if needed.
3. Duplicate it for repeated fixtures.
4. Delete or weaken lights in rooms that should feel darker.
5. Test the final illumination from an actual player token.

Do not place a light on every decorative flame simply because the artwork contains one. Add lights where they influence tactical visibility.

Lighting should create decisions. If an extra torch does not change what the players can see or how they move, it may not need to exist as a Dynamic Lighting object.

How Do You Configure Player Vision Correctly?

A perfect lighting layer still fails if the player tokens do not have vision enabled.

Place the token on the Token Layer, open its settings, enable Vision, then configure Night Vision or limited fields of view when appropriate.

For ordinary characters carrying torches, it is usually cleaner to let the torch or character token emit light and leave the map itself dark. For characters with darkvision, use token vision settings rather than adding invisible lights to simulate what only that character can see.

The critical test is not what the GM sees. Use a controlled token and verify the page from the player's perspective.

Why Do Most DMs Make Dynamic Lighting Slower Than It Needs to Be?

The most common failure is overbuilding the lighting layer.

Roll20 specifically identifies large maps, many complex Dynamic Lighting lines, giving sight to many tokens on heavily populated pages, and Explorer Mode as features that can become demanding on lower-performance computers.

None of those features are bad. Problems appear when all of them are used at maximum intensity at the same time.

Failure Mode 1: Hundreds of Tiny Wall Segments

Do not trace rough stone walls one brick at a time. Use fewer, longer segments that preserve the intended room shape.

Failure Mode 2: Every NPC Has Vision

NPC vision may be useful for the GM, but enabling sight on dozens of creatures can increase scene complexity. Only give tokens vision when you actually need it.

Failure Mode 3: Giant Maps for Small Encounters

If the session only uses one dungeon wing, loading an enormous multi-level complex is unnecessary. Smaller encounter pages can be easier to light, easier to troubleshoot, and easier on lower-end hardware.

Failure Mode 4: Testing Only as the GM

The GM's view is intentionally more permissive. Always test from a player-controlled token before the session starts.

If a player's computer struggles, Roll20 also recommends confirming hardware acceleration and WebGL are enabled in a supported browser. On the latest engine, lower Dynamic Lighting texture-resolution settings can also reduce the rendering load on lower-end systems.

Can You Skip Manual Wall Setup Entirely?

Sometimes.

Roll20 currently supports Universal Virtual Tabletop files such as UVTT, DD2VTT, and DF2VTT exported from compatible tools. Those files can include wall, door, and light information, allowing Roll20 to place much of the Dynamic Lighting setup automatically.

That is the fastest route when you created the map in a compatible tool and the export already contains accurate lighting data.

For ordinary JPG, PNG, or WebP battle maps, manual barrier setup is still required. The fastest approach is to use a map whose architecture is visually clear enough that walls, doors, stairs, and room boundaries can be traced without interpretation.

If you are still getting the base image aligned, start with our Roll20 battle map setup guide for Dungeon Masters before building the lighting layer.

What Is the Fastest Complete Dynamic Lighting Workflow?

That workflow keeps setup focused on gameplay. You can always add more lighting detail later if the encounter benefits from it.

Frequently Asked Questions

Sources