Foundry VTT Version 14 Stable Release Prompts Pathfinder 2e Compatibility Updates
Foundry VTT's first V14 stable build landed on April 1 with the pf2e system not yet confirmed compatible; GMs should hold updates until a full compatibility release arrives.

Foundry Virtual Tabletop shipped build 14.359 on April 1, 2026, and the first thing its release notes did was address the obvious: "No, this is not an April Fools prank."
It wasn't. But for PF2e GMs, the real story wasn't the platform reaching stable; it was what wasn't ready when it did. At the time of the 14.359 release, Foundry confirmed compatibility for three systems: D&D 5E, the Crucible game system, and the Universal Tabletop System. The PF2e system, maintained by a volunteer team under an official partnership between Foundry Gaming LLC and Paizo, was not among them. The release notes directed players to the #pf2e channel on the official Foundry Discord, stating that "a pre-release version of the PF2E system for testing purposes is in active development and expected soon."
That gap matters for the PF2e tables running on Foundry. Version 14 is built around five major development pillars: Scene Levels, Active Effects V2, Scene Regions V2, ProseMirror improvements, and pop-out applications. The Scene Levels feature is the headline for PF2e GMs specifically, enabling stacked multi-floor maps and layered environmental effects that weren't previously achievable on the platform. But those features only become usable in PF2e sessions once the volunteer system team ships a V14-compatible release and companion modules, including HUDs, automation tools, and lighting effects packages, follow suit.
The Foundry team described 14.359 as "deliberately modest in scope and contains only a few changes to ensure stability," a design choice meant to lock down the platform rather than push new features at the stable tier. That's actually good news for pf2e maintainers: the V14 API surface is now fixed, giving the volunteer team a stable target to write compatibility patches against rather than chasing a moving prototype build. Module authors historically post compatibility notes to package pages and GitHub repositories within 24 to 72 hours of a stable release.

The Forge, one of the primary cloud hosting services for Foundry, was still completing its own V14 testing on April 1 and had not yet rolled the new version out to hosted games. Its guidance was consistent with the broader pattern: don't update until required systems and modules confirm compatibility.
For self-hosted GMs, the safest path is cloning a production world into a sandbox and running through character sheet interactions, item automation, and a full combat encounter before touching anything with active players in it. Groups coordinating Pathfinder Society or multi-table organized play face the highest stakes; a broken aura or an unresponsive sheet at session start can derail an entire event in ways a home table can simply reschedule around. The pf2e GitHub changelog and the #pf2e Discord pins are the two places to watch until the full V14-compatible system release lands.
Know something we missed? Have a correction or additional information?
Submit a Tip

