Virtual Tabletop Platforms Compared: Roll20, Foundry, and More

Virtual tabletop (VTT) platforms have transformed how tabletop RPG groups gather — or rather, how they gather without gathering at all. Roll20, Foundry VTT, Fantasy Grounds, Alchemy, and a handful of smaller competitors each make distinct architectural choices that produce meaningfully different experiences at the table. This page maps those differences across hosting models, pricing structures, automation depth, and system support so groups can match a platform to how they actually want to play.

• Definition and scope
• Core mechanics or structure
• Causal relationships or drivers
• Classification boundaries
• Tradeoffs and tensions
• Common misconceptions
• Checklist or steps
• Reference table or matrix
• References

Definition and scope

A virtual tabletop platform is software — delivered through a browser, a desktop application, or both — that replicates the shared physical space of a tabletop RPG session in a digital environment. The functional minimum is a shared canvas where a game master and players can see the same map, move tokens, and roll dice with verifiable results. Beyond that minimum, platforms diverge sharply.

The scope of the VTT market is broader than most newcomers expect. Roll20, launched in 2012, reported over 10 million registered users as of its own public statements, making it the most widely adopted browser-based VTT. Foundry VTT entered the market in 2020 as a one-time-purchase self-hosted alternative and accumulated over 100,000 licenses sold within its first two years, according to the developer's public announcements. Fantasy Grounds, the oldest major commercial VTT still in active development (predating Roll20 by roughly eight years), occupies a distinct niche with deep ruleset automation. Alchemy, Owlbear Rodeo, and Astral Tabletop represent a newer generation of lighter-weight or browser-first tools.

The home page for this reference site provides broader context on the tabletop RPG ecosystem these tools serve.

Core mechanics or structure

Every VTT is built around four structural layers, though each platform weights them differently.

The canvas layer is the shared visual space — grid or gridless — where maps, tokens, and handouts exist. Roll20 uses a paginated layer system (GM layer, token layer, map layer, lighting layer) that is functional but widely described as showing its age; it predates modern browser rendering approaches. Foundry VTT uses a scene-based model with a more modern canvas engine built on PixiJS, which enables dynamic lighting and line-of-sight calculations that run smoothly on mid-range hardware.

The dice engine must be transparent to all players and tamper-resistant. Roll20 uses a proprietary dice formula language; Foundry uses a modular Roll class that developers can extend. Fantasy Grounds uses its own scripting environment. Critically, all three major platforms provide server-side roll verification — the dice result is computed centrally, not locally, so no client can manipulate the outcome.

The character sheet and data layer is where complexity concentrates. Roll20 character sheets are HTML/CSS/JavaScript templates stored per-campaign; quality varies enormously by sheet author. Foundry's system layer is handled by community or commercial "game system" packages — the official D&D 5e system (maintained by third parties, with an officially licensed version available through the D&D Beyond integration) is one of roughly 300 supported game systems as of the Foundry VTT package repository. Fantasy Grounds ships with tightly integrated rulesets and sells official licensed content from publishers including Wizards of the Coast and Chaosium.

The content distribution layer determines how maps, tokens, music, and rulebooks reach the table. Roll20 sells content through its marketplace; Foundry relies on a package ecosystem combining free community modules with commercial content from the Forge, Patreon creators, and publishers. Fantasy Grounds Unity has its own store with an unusually high percentage of officially licensed sourcebooks.

Tools like tabletop RPG apps and digital tools complement VTT platforms rather than replacing them — companion apps for rules lookup, initiative tracking, or ambient sound sit outside the VTT canvas but integrate with session workflow.

Causal relationships or drivers

The hosting model is the single variable that drives the largest downstream differences in a VTT experience.

Roll20 is fully cloud-hosted. The server stores all assets, all campaign data, and handles all computation. This produces zero setup friction — a new group can run a session within 30 minutes of account creation — but it also means Roll20 controls the infrastructure, the pricing, and the pace of feature development. Storage limits apply to free accounts (100 MB per campaign on the free tier, as of Roll20's published pricing), and performance is subject to Roll20's server load.

Foundry VTT is self-hosted by default. The game master purchases a one-time license (priced at $50 USD as of the developer's published pricing at foundryvtt.com) and runs the software on a local machine or a rented cloud server. Players connect via browser — they need no account and no software installation. This model means the GM bears infrastructure responsibility but also has no ongoing subscription cost and no storage ceiling beyond their own hardware. The Forge (forge-vtt.com) offers managed Foundry hosting for a monthly fee, splitting the difference.

Fantasy Grounds operates on a peer-to-peer model with two license tiers: the GM purchases either a Standard license or an Ultimate license ($149 USD as of Fantasy Grounds' published pricing). The Ultimate license allows players to connect with the free Fantasy Grounds demo client, which matters significantly for group adoption friction.

These hosting decisions cascade into everything: update cadence (Roll20 updates are invisible to users; Foundry updates require GM action), module compatibility (Foundry's 1,000+ community modules can break after version updates), and data portability (Roll20 campaigns are not exportable in any standard format).

Classification boundaries

VTTs are not all competing for the same use case, and treating them as a single product category produces bad decisions.

Automation-first platforms (Fantasy Grounds, Pathfinder-specific tools) assume the software enforces the rules. Attack rolls calculate hit or miss automatically; spell slot tracking is embedded in character sheets; condition effects apply programmatically. This is ideal for groups who want the rules handled for them, particularly for complex systems like Pathfinder 2e or D&D 5e with many interlocking mechanics.

Flexibility-first platforms (Foundry VTT, Roll20 with custom sheets) provide the infrastructure but leave rules enforcement optional. A group running a homebrew system or a narrative-light game like Powered by the Apocalypse gains little from deep automation and benefits more from a flexible canvas and easy handout distribution.

Zero-friction tools (Owlbear Rodeo, Letsrole) prioritize immediate usability over depth. Owlbear Rodeo in particular requires no account — a GM creates a room, shares a URL, and the session begins. Feature depth is deliberately limited.

The tabletop RPG system comparison page addresses how game system choice interacts with platform selection — a decision that is more entangled than it first appears.

Tradeoffs and tensions

The deepest tension in the VTT space is between automation depth and system agnosticism. A platform optimized for D&D 5e automation will handle a Monster Manual creature with near-zero GM prep: drag the stat block onto the canvas, and attack rolls, saving throws, and hit point tracking all function immediately. That same platform will be clumsy for running a game like Call of Cthulhu, where the skill check economy, sanity tracking, and combat lethality work differently. Call of Cthulhu has dedicated Foundry modules and a Fantasy Grounds ruleset — but their quality and completeness vary.

A second tension exists between asset ownership and platform lock-in. Content purchased through Roll20's marketplace exists only within Roll20 — the PDFs, maps, and tokens cannot be extracted. A group that spends $200 on Roll20 marketplace content and later wants to migrate to Foundry starts over. Foundry content purchased through compatible publishers (such as Kobold Press's Foundry-native releases) travels with the license.

A third tension involves the GM's technical load. Foundry's power comes with a learning curve that is genuinely steep — configuring dynamic lighting, installing modules without creating conflicts, and troubleshooting a broken scene before a session starts in 20 minutes is not a hobby experience everyone wants. Roll20's ceiling is lower, but its floor is much more forgiving.

Groups built around finding a tabletop RPG group online often default to Roll20 precisely because player onboarding is friction-free, even if the GM would prefer Foundry's feature set.

Common misconceptions

Foundry VTT requires players to install software. It does not. Players join a Foundry session through a standard web browser. Only the GM runs the application (or pays for hosted infrastructure).

Roll20 is free. Roll20's free tier exists, but it excludes dynamic lighting, API access, and premium assets. The Plus subscription costs $4.99/month and the Pro subscription costs $9.99/month (as published on Roll20's pricing page). Many features groups assume are standard require the Pro tier.

More automation means better play. Automation reduces lookup time and arithmetic errors, but it also moves rules enforcement out of the players' awareness. Groups new to a system sometimes learn the rules better on a less automated platform because they have to engage with the mechanics manually.

VTTs replace physical play. Platforms like Foundry and Roll20 are digital approximations of the physical table — they do not replicate the tactile experience of tabletop RPG miniatures and terrain, the social dynamics of shared physical space, or the improvisational energy of in-person sessions. They solve a logistics problem; they do not upgrade the experience in every dimension.

All VTTs support all RPG systems equally. Fantasy Grounds' ruleset for Pathfinder 2e is among the most automation-complete implementations of any system on any VTT, the product of years of official publisher partnership. The same platform's support for an indie system with no developer-built ruleset is essentially a blank canvas. System support is platform-specific and varies enormously.

Checklist or steps

Factors a group works through when selecting a VTT platform:

Reference table or matrix

Pricing figures reflect published rates on each platform's official site and are subject to change; verify current pricing directly before purchase.