Lumen VTT

Roll20 alternative

A Roll20 alternative for groups tired of manual combat flow

Roll20 is a strong broad browser VTT with sheets, marketplace tools, and Jukebox audio. Lumen is the challenger for D&D groups that want the session connected: player phone actions, a GM browser table, TV display, audio, and common 5e combat math without asking the GM to stitch the flow together.

Start with Lumen VTT Compare VTT features
A product-derived preview of animated spell feedback, map state, and loot flow in Lumen VTT.

Feature comparison for D&D 5e groups

Feature Lumen VTT Roll20 Foundry VTT Owlbear Rodeo D&D Beyond Maps
Storage and plan cost 300 MB included Lumen currently includes 300 MB of hosted account storage for uploaded campaign assets such as vault images and table media. 100 MB free Roll20 lists 100 MB free, 4 GB Plus ($5.99/mo), 10 GB Pro ($10.99/mo), and 50 GB Elite ($14.99/mo), with per-file upload caps. $50 + $4-6+/mo host Provider hosting costs incur unless you self-host; common Foundry hosts start around $4-$6/mo before larger storage needs. 200 MB free Owlbear documents 200 MB free cloud storage plus paid 5 GB and 10 GB tiers for uploaded custom assets and scenes. 10 GB on Master D&D Beyond lets free accounts host basic Maps sessions, while custom map and video uploads with 10 GB Maps storage are tied to Master Tier ($5.99/mo).
Whole-session D&D flow Built into Lumen GM tools, player phone controls, TV display, audio, map state, and common combat math are designed to work together. Manual/table-managed A broad browser VTT toolbox, but groups often connect sheets, macros, marketplace content, and GM rulings themselves. Requires setup Powerful workflows are possible, but the GM usually owns system setup, hosting choices, modules, and configuration. Map-first Fast shared maps are the core strength; deeper session flow usually comes from extensions or external tools. Map-first Official D&D map play is the strength; support docs currently describe Maps as beta and centered on library maps and monsters.
Common 5e combat math Built into Lumen Targeting, rolls, saves, damage, healing, HP, conditions, turns, and visible feedback stay tied to the encounter. Manual/table-managed Sheets and roll templates help, but many hits, saves, damage edits, conditions, and spell outcomes remain a table workflow. Module/API dependent Automation can be deep, but it depends on the game system, modules, settings, and compatibility. Extension based Core play is map movement; initiative and rules automation are extension or outside-table workflows. Official D&D library strength Official characters, monsters, maps, initiative, and dice are strengths; Lumen goes deeper on custom combat flow.
Player phone controls Built into Lumen Phones are focused player action controllers for character, dice, inventory, map, prompts, loot, shops, and rests. Requires setup Players can use browser and character tools, but phone-first table action control is not the central workflow. Requires setup Mobile usability depends on hosting, system UI, modules, browser/device behavior, and table configuration. Map-first Responsive map access is strong, but 5e player actions usually live elsewhere or in extensions. Official D&D library strength D&D Beyond is excellent for character reference, but Maps is not built around Lumen-style phone action control.
TV table display Built into Lumen A player-safe live display is a core workflow for in-person and hybrid games. Requires setup A shared screen can work, but the group assembles the TV workflow around the VTT. Requires setup Table displays are possible through player views, hosting, modules, and local setup choices. Map-first Excellent as a shared battlemap; deeper combat and table overlays depend on extensions or external tools. Map-first Useful for showing maps, but not positioned as a full GM-phone-TV session system.
Music and room audio Built into Lumen Music, ambience, SFX, and room context live inside the campaign flow. Built in Roll20 documents Jukebox audio with uploads and partner libraries. Built in Foundry documents playlists and ambient sounds inside worlds. Extension based Audio usually comes from extensions or external tools rather than the core map table. Map-first D&D Beyond Maps is not positioned around built-in room audio.
Online play without self-hosting Built into Lumen Run a hosted browser session without maintaining a game server. Built in Roll20 is a hosted browser VTT. Server/hosting required Foundry documents self-hosting, cloud hosting, and third-party hosting options. Built in Owlbear rooms are hosted and shared by link. Built in D&D Beyond Maps runs in the browser as an official hosted D&D tool.
No module stack Built into Lumen Core D&D 5e session flow ships as product behavior. Manual/table-managed Core tools work out of the box, but deeper automation may involve macros, Mods/API scripts, or marketplace setup. Module/API dependent Foundry's power often comes from modules that alter or extend software behavior. Extension based Extra workflows are intentionally handled through extensions. Official D&D library strength Official Maps does not ask users to assemble a module stack, but it is narrower than Lumen's session-flow pitch.
Best fit Whole-session flow Groups that want D&D combat flow, phone actions, TV display, audio, and hosted play in one product. Broad toolbox Groups that want a long-running browser VTT with many tools and marketplace options. Power users Groups that want maximum control and accept setup, hosting, and module management. Map-first Groups that want a clean, fast shared battlemap and add depth only when needed. Official D&D maps Groups already centered on D&D Beyond who mainly need official map play and library integration.

Comparison wording is intentionally conservative. It describes product shape and setup model, not a universal ranking.

Why DMs compare Lumen

The fight is the test

Run one real spell encounter and count the manual hits, saves, damage edits, conditions, and map-state fixes still left to the GM.

Audio alone is not the win

Roll20 has documented Jukebox audio; Lumen competes on audio living beside combat, player controls, and table display.

Phones are action controllers

Players are not just opening a mobile page. Lumen's pitch is focused player actions from the device already in their hand.

Where Roll20 is strong

Roll20 is a long-running browser VTT with character sheets, roll templates, marketplace content, and documented Jukebox audio. It is a real platform, not a strawman.

Where Lumen pushes harder

Lumen focuses on D&D 5e groups that want actions, targeting, saves, damage, healing, conditions, audio, and visible table feedback to stay in one flow.

Why phone and TV workflows matter

If your group plays around a TV, shared display, or mixed online table, Lumen's player phone controls and live table view are not side conveniences. They are part of the product shape.

A fair switcher test

Run a real encounter, invite a player on a phone, try a spell with an area effect, play a music cue, and compare how much GM correction is needed after each action.

Compare VTTs by how the whole D&D session actually runs A D&D 5e VTT for combat-heavy sessions Automated D&D combat that keeps the table moving A VTT for in-person D&D tables

Comparison sources

Lumen VTT is an independent product and is not affiliated with Roll20, Wizards of the Coast, Dungeons & Dragons, or any referenced trademark owner. Comparison pages are written to help groups evaluate workflows and feature fit.