Obsidian - Import the Pathfinder 2e Remaster Content

Pathfinder 2e Remaster content can be imported into an Obsidian Vault in a way that preserves the system’s mechanics and enables automatic linking—so prep and at-the-table lookups don’t require flipping through books. The core workflow uses Foundry Virtual Tabletop as a legal bridge to pull in Pathfinder 2e community mechanics (monsters, spells, items, feats, actions) and, importantly, also supports importing adventure content that isn’t covered by the community policy—provided it’s available in Foundry. Once the exported notes land in Obsidian, plugins render stat blocks and action items, and Obsidian indexing powers fast internal links between encounters, monsters, hazards, and rules.

The process starts with purchasing Foundry Virtual Tabletop ($50, one-time) and installing the Pathfinder Second Edition game system inside Foundry. Then the setup shifts to add-on modules: three prerequisites are required for exporting—lib wrapper, more handlebar helpers, and the pf2e exporter module (a Pathfinder 2e-focused fork maintained by Mostorn Brain). The exporter’s GitHub instructions guide installation, including adding a module.json manifest URL directly into Foundry’s module installer.

After creating a Foundry world configured for Pathfinder 2e, the exporter is enabled via Foundry’s module management. The pf2 exporter settings are tuned for the user’s needs: output format is kept as non-decoded data (JSON), technical UID fields are turned off, and optional features like “include initiative tracker” are disabled if redundant. A key optional step involves purchasing Pathfinder tokens for beastiaries and enabling “export custom images” so exported monster notes include the artwork. Without that purchase and Foundry configuration, Foundry’s default content lacks those images.

With Foundry configured, exporting becomes a repeatable action. In Foundry’s compendium packs, the user right-clicks a content package (for example, Beastiary 1, Beastiary 2, Beastiary 3, and Monster Core) and exports it to Markdown, producing a downloadable ZIP. That ZIP is then dragged into the Obsidian Vault (the user places it under a “2-mechanics/Beastiary” folder). If images were enabled, an assets folder comes along with the stat blocks, keeping monster artwork attached to the notes.

To make the Vault usable at game speed, Obsidian plugins are installed and configured. Fantasy stat blocks (Jeremy Valentine) renders creature stat blocks; Pathfinder 2e action items turns structured action markup into clickable/usable action components. The IT theme and style settings are used to match Pathfinder remaster aesthetics, with care taken to avoid conflicting renderers. Finally, a CSS snippet for spells is downloaded from Mostorn Brain’s resources and added to Obsidian’s CSS Snippets folder so spell notes display correctly.

Once Obsidian reloads and indexes the new notes, automatic linking kicks in: creating an encounter note and typing a monster name (or hazard) can link directly to the corresponding exported stat block. The workflow also includes a practical warning about “how much content is enough”: having every race, background, and similar entries can clutter results (the user chooses to limit some rulebook-derived categories and focuses on monsters and related content). The end result is a Vault where monsters, hazards, spells, feats, and actions are all connected—built for faster prep and smoother play, including hazards entering initiative tracking when configured.