Spell automation is not about taking judgment away from the DM. It is about removing the repetitive work that appears every time someone says 'I cast Fireball' and everyone waits for targeting, saves, damage, and map feedback to catch up.
Good D&D 5e spell automation should handle targeting, areas, saves, damage, conditions, concentration, resistance context, visible feedback, and the combat log while leaving the DM in control. Lumen currently has 200+ automated 5e spells with animated combat feedback and 350+ structured spells, actions, class features, and monster abilities in the structured engine path.
The major D&D 5e spell automation VTT
This is not a universal ranking for every table. It is a way to sort the major choices by how they feel during a real D&D session: setup load, player access, map flow, combat state, and what the GM still has to manage by hand.
Lumen VTT
Automation as product behavior
Lumen's spell automation is built into the session flow: players can cast, the table can see the effect, and the DM can keep momentum without rebuilding the same rules workflow every encounter.
Best fit: Targeting and saves, Damage and conditions, Animated table feedback.
Tradeoff: The GM should still adjudicate edge cases; automation supports the table, not replaces it..
Foundry VTT
Automation through a custom stack
Foundry can support deep automation, especially through modules. That is powerful for technical DMs, but it changes the question from 'does the VTT do it?' to 'which stack do I maintain?'
Best fit: Deep module ecosystem, Advanced customization, Power-user automation.
Tradeoff: Automation depends on module choices and compatibility..
Roll20
Macros and sheet rolls
Roll20 can reduce manual work with sheets, roll templates, macros, and API scripts. For many tables, though, spell resolution still becomes a GM-managed process.
Best fit: Familiar sheets, Macros and API scripts, Hosted browser access.
Tradeoff: More automation can require setup and maintenance..
Owlbear Rodeo
Reference-first spell play
Owlbear is excellent when you want a clean map and handle spell rules elsewhere. It is better described as spell reference plus map play than full spell automation out of the box.
Best fit: Clean interface, Fast map play, Low complexity.
Tradeoff: Not the strongest fit if spell resolution is your main pain..
When Lumen is not the right fit
Full automation is not always desirable. If your table prefers every roll and ruling by hand, keep it light. If your sessions slow down because spells are hard to resolve and hard to show, automation becomes one of the highest-value VTT features.
Questions to ask before switching
What should spell automation never do?
It should not hide the rules, remove DM judgment, or make edge cases impossible to override.
What is the minimum useful spell automation?
Targets, area shape, save prompt, damage result, condition output, and clear table feedback.
Why does animation matter?
Because players understand the result faster when the map shows what happened instead of burying the moment in chat text.
The useful test is a real encounter, not another feature grid. Try the Lumen demo and see whether the table feels easier to run.
Related reading
Sources and notes
Lumen VTT is an independent product and is not affiliated with D&D 5e VTT spell automation workflows, Wizards of the Coast, Dungeons & Dragons, or any referenced trademark owner. This guide is written to help groups compare workflow fit.