Get AI summaries of any video or article — Sign up free
Obsidian - Linking to PDFs thumbnail

Obsidian - Linking to PDFs

Josh Plunkett·
5 min read

Based on Josh Plunkett's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Drag-and-drop PDFs into the Vault and store them in a dedicated attachments folder for consistent rendering and organization.

Briefing

Linking directly to specific pages inside PDF files is the key payoff: Obsidian can render a PDF preview inside a note and jump straight to a chosen page (e.g., page 5), turning rules and adventure handouts into navigable, campaign-ready references. That matters for tabletop RPG prep because it reduces the need to manually transcribe long modules into separate notes—especially when publishers provide well-formatted PDFs.

The workflow starts with getting PDFs into the Vault. PDFs can be dragged into Obsidian; when they’re added as attachments, they land in the Vault’s configured attachments folder (set via “Set as attachment folder” on a folder). Once the files are present, Obsidian can display them with built-in PDF viewing features such as page-by-page browsing, chapter mode navigation, zoom controls, page count, and options like rotate, download/print, and toggling annotations. To make sure file types show up correctly, the video recommends enabling “detect all file extensions” under Settings → Files and links.

The practical “cool” part is how Obsidian links to PDFs with embedded rendering. Instead of linking to a PDF as a generic file, the note can include a link that renders the PDF content inline. The example uses a syntax that both targets a particular PDF and specifies a page number, so the rendered view opens at the requested page rather than forcing readers to scroll from page one. In read mode, the preview loads and skips to the defined page; the presenter notes that the PDF render syntax uses code-like markers (including an exclamation mark) that should be removed when using the snippet as normal text.

This approach also supports contextual navigation inside an adventure. By creating links from wherever a player-facing note or prep note lives, the campaign can jump to the relevant section of the module—such as “this chapter corresponds to that page in the PDF.” The video demonstrates that the hover preview may be small, but clicking still takes you to the rendered PDF view at the correct page.

For organizing multiple PDFs, the video adds a second layer: DataView JS queries that automatically list PDFs in the Vault. One query scans all files where the extension equals PDF and produces a list of their file paths, effectively generating a live catalog. A variation filters to a specific folder (e.g., a folder like “Z_underscore assets”), so a landing page can show only the PDFs stored there. As new PDFs are added, the list updates automatically.

Overall, the method leans on out-of-the-box PDF support for viewing and linking, with optional plugins only for annotation/highlighting enhancements. The result is a faster prep pipeline: keep adventures and rules in their original PDF form, link to exact pages from Obsidian notes, and use DataView JS to maintain an always-current index of available documents.

Cornell Notes

Obsidian can ingest PDFs as attachments and render them inside notes, letting users browse and navigate documents without leaving their Vault. The most useful feature is page-targeted linking: a note can render a PDF preview and jump directly to a specified page (the example uses page 5), which streamlines RPG prep. Built-in PDF viewing includes page-by-page and chapter mode, plus controls like zoom and annotation toggles. For organization, DataView JS queries can generate an automatic catalog of all PDFs in the Vault or only those in a chosen folder, updating as files are added. This combination reduces transcription work and makes rules/adventure references easier to find.

How does someone add PDFs to an Obsidian Vault so they render properly?

PDFs can be dragged into the Vault. If they’re added via a note, they go into the configured attachments folder; the video recommends right-clicking a folder and using “Set as attachment folder” so external files (including PDFs) consistently land in that location. With PDFs in place, Obsidian’s PDF viewer can display them directly, including page navigation and rendering.

What does “page-targeted” PDF linking accomplish in Obsidian?

Instead of opening a PDF at the beginning, the link syntax can specify a page number so the rendered preview jumps straight to that page. In the example, the note renders the PDF and skips to page 5 in read mode. The video also notes that the render syntax includes code-like markers (such as an exclamation mark) that should not be left in normal text.

Which built-in PDF viewer features are available once PDFs are in the Vault?

The viewer supports page-by-page browsing, a “chapter mode” for easier navigation, zoom controls, page count, and a “fit to page” option. It also includes rotation (anti-clockwise in the demo), download/print options, and an annotation toggle that matters if annotations were added externally. A two-page view option is also mentioned.

How can Obsidian help create a catalog of PDFs without manually maintaining a list?

DataView JS can scan the Vault for files with extension equals PDF and then render a list of those file paths. The video demonstrates that this produces an automatic index of PDFs already in the Vault (e.g., “fistful of flowers,” “threshold of knowledge,” and “a little trouble in big ash blonde”). A second query filters to a specific folder (like “Z_underscore assets”) so the catalog can be scoped.

Why might a player or GM prefer linking to PDFs instead of transcribing modules into notes?

Linking avoids re-entering large amounts of text. Since publishers provide formatted PDFs, the GM can keep the source material intact and jump to the exact page from relevant notes (chapters, sections, or player-facing summaries). The video contrasts this with an alternative workflow where the entire adventure is transcribed and then customized, but emphasizes that transcription isn’t required for effective use.

Review Questions

  1. What steps ensure PDFs are stored in Obsidian’s attachments folder, and why does that matter for organization?
  2. How does page-targeted PDF linking change the reading experience compared with opening a PDF normally?
  3. How would you adapt a DataView JS query to list only PDFs inside a specific folder rather than the entire Vault?

Key Points

  1. 1

    Drag-and-drop PDFs into the Vault and store them in a dedicated attachments folder for consistent rendering and organization.

  2. 2

    Enable “detect all file extensions” under Settings → Files and links if Obsidian isn’t recognizing file types as expected.

  3. 3

    Use PDF link rendering to embed a PDF preview inside a note rather than treating the PDF as a plain file link.

  4. 4

    Specify a page number in the PDF render link so the preview jumps directly to that page (e.g., page 5).

  5. 5

    Create contextual navigation by linking from chapter/section notes to the corresponding page in the adventure PDF.

  6. 6

    Generate an automatic PDF index with DataView JS by listing files where extension equals PDF.

  7. 7

    Filter DataView JS catalogs to a specific folder (such as “Z_underscore assets”) to maintain a scoped landing page for RPG resources.

Highlights

Obsidian can render a PDF inside a note and jump straight to a chosen page, cutting out manual scrolling.
A simple attachments-folder setup keeps PDFs organized and ensures they show up correctly in the Vault.
DataView JS can auto-generate and maintain a living catalog of PDFs across the entire Vault or within one folder.

Topics

Mentioned