Obsidian - Entering an Adventure or Module

Turning a tabletop RPG adventure module into an Obsidian-ready, editable, and linkable knowledge base hinges on one practical choice: start from clean digital text (not scanned books) and then normalize the formatting page-by-page. The payoff is control—editing NPCs, adding descriptions, and building navigation that supports both reading and actual play.

The process begins with sourcing. Hardcover books are a poor fit for digital entry because they require manual retyping or inefficient scanning/OCR workflows. PDFs are better, but older PDFs often store text as positioned “visual fragments” rather than real copyable text, so copy/paste can produce broken characters and formatting. The recommended first step with any PDF is a “copy and paste check”: paste a chunk into a plain text scratchpad (the transcript uses a notepad) and verify that text arrives correctly. If it does, the PDF is usable; if it doesn’t, the entry becomes slow and error-prone.

When clean text is available from a web service, copy/paste tends to preserve line breaks more predictably than PDFs, making formatting easier. The transcript contrasts this by pulling content from DND Beyond (via a web adventure) and from Pathfinder Nexus (a Pathfinder Nexus adventure page), then using the same validation approach. For users who already own modules in a digital ecosystem, importing into Foundry and exporting to Obsidian is presented as a shortcut that can preserve structure and formatting.

Once the source is chosen, the next major decision is Obsidian organization. The workflow uses a Vault hierarchy with a dedicated “world” folder, then splits by setting (e.g., Forgotten Realms) and by system/module type. It also accounts for Windows path-length limits by shortening folder and file names to avoid sync or path errors. Each adventure gets its own folder note—treated as a parent container—where images, chapter notes, and supporting assets live.

Formatting is handled with a repeatable pipeline. Content is pasted using Ctrl+Shift+V when URLs should become readable text, and line breaks are cleaned up using a community plugin (“text format”) with a hotkey to merge broken paragraphs. Headings are converted into Markdown with hashes, and callouts (including “read aloud” blocks) are inserted via templates. Chapters are created as separate notes ahead of time (e.g., “Chapter 1…”, “Chapter 2…”) to make linking reliable later.

Images require extra care. The transcript shows that extracting images from PDFs can yield messy backgrounds, so it uses screenshot tools (ShareX) and image cleanup steps (including transparency handling) before pasting into the Vault’s assets area. It also notes a better option: if the same adventure exists in a cleaner digital format (e.g., Pathfinder Nexus), copying images directly can preserve transparency and edge fading, saving significant cleanup time.

Finally, the module becomes playable inside Obsidian. The workflow adds combat readiness by inserting monster stat blocks and encounter blocks using templates (including an initiative tracker-style approach). It then layers navigation: maps are embedded with templates, room headings are linked via hashtags, and “show to players” links are configured using the Second Window plugin so images can display on a separate TV screen. After text, images, and combat blocks are in place, linking and backlinks are treated as a later pass—using Obsidian’s outgoing links and “unlinked mentions” to connect monsters, items, and locations.

The central message is that the quality of the original digital source determines how painful entry will be; when the source is clean, the rest becomes a structured, mostly mechanical workflow that turns a module into an editable, interactive tabletop toolkit.