Annotating PDFs in Obsidian

Obsidian is the second brain of choice for users who want local files, plain Markdown, and a long tail of community plugins. For PDF-heavy users, Obsidian plus a few key plugins becomes a genuinely powerful PDF annotation environment, with the unique property that your notes live as plain Markdown next to the PDFs themselves. This guide covers the practical setup.

Why Obsidian for PDF annotation

The themes:

• Local-first. PDFs and notes live on your machine; sync is optional and configurable.
• Plain Markdown. Notes survive forever; portable across tools.
• Plugin ecosystem. PDF annotation is community-driven but mature.
• Bidirectional linking. PDF annotations can become notes that link to other notes.
• Graph view. See connections across your reading.

The trade-offs: less polished than Acrobat for raw PDF editing; setup requires picking the right plugins.

Built-in PDF support

Obsidian's core supports:

• PDF preview when you click a PDF file in the vault.
• Embedding a PDF in a note with the ![[file.pdf]] syntax.
• Page-specific embedding with ![[file.pdf#page=12]].
• Internal links to specific pages.

For light use (read inline, link to specific pages, write notes next to), the core is enough. For real annotation, plugins.

The annotation plugins

Two stand out in 2026:

Annotator. Loads a PDF inside an Obsidian view; lets you highlight, comment, and underline. Annotations save into the note as Markdown, tied to specific pages. The PDF file itself is unmodified.

PDF++. A newer plugin offering a richer in-app PDF viewer with extensive annotation controls. Saves annotations either into the PDF file directly or into a Markdown sidecar.

Pick one and stick with it; mixing both creates confusion.

Workflow with Annotator

The pattern:

1. Open a PDF inside Obsidian (the plugin gives you an in-app viewer).
2. Highlight passages. The highlights appear as Markdown blocks in the corresponding annotation note.
3. Add notes in the right-hand panel; they become Markdown next to each highlight.
4. Close the PDF. Reopen later; highlights persist.
5. Link annotations to other notes via standard Obsidian [[wikilink]] syntax.

The result is a Markdown note that contains all your highlights and reflections, alongside the original PDF.

Workflow with PDF++

The pattern:

1. Open a PDF; the in-app viewer is more polished.
2. Use the toolbar to highlight, comment, draw.
3. Annotations save back to the PDF file (portable; visible in other PDF readers).
4. Optionally extract highlights into a Markdown note via a command.
5. Link extracted highlights to other notes.

PDF++ supports more annotation types (boxes, freeform drawing) and tends to be the active choice for new setups.

Capture from external readers

Some users prefer to annotate in a dedicated PDF reader (Preview, Acrobat, PDF Expert) and then import the highlights into Obsidian. Plugins that help:

• Citations: imports BibTeX entries and references PDFs in Zotero.
• Obsidian Zotero integration: pulls Zotero highlights and notes into Obsidian.
• DEVONthink for Obsidian: link DEVONthink-stored PDFs.
• Highlights (Mac app) sells an Obsidian sync option.

For research workflows centered on Zotero, this is often the better path. Annotate in Zotero or a preferred PDF tool; sync notes into Obsidian.

Organizing PDFs in the vault

Obsidian works on a vault folder. PDFs can live:

• Inside the vault: alongside notes. Plugin annotation works on them directly.
• Outside the vault, linked: store PDFs in a separate folder; link in Markdown. Saves vault size for sync.
• In a cloud, linked via URL: PDFs in Drive/Dropbox; link to them.

For sync (Obsidian Sync, iCloud, Dropbox), in-vault PDFs add to the sync footprint. For a 10 GB PDF library, you may prefer external storage with links.

Annotation as Markdown

A killer pattern: annotations rendered as Markdown.

Each highlight becomes a block in a sidecar note. Example:

> The transformer architecture has displaced recurrent networks across most NLP tasks.

Page 3 | tag: deep-learning, transformers

These blocks become first-class searchable, linkable, embeddable content. A weekly review pulls all the week's highlights into a single page.

For knowledge management specifically, see academic research PDF workflow and citation management with PDF papers.

Bidirectional links

Obsidian's superpower: connecting ideas across notes. With PDF highlights as Markdown blocks:

• Link a highlight to a note that elaborates on the idea.
• Backlinks show every PDF that touched a topic.
• Graph view exposes structure across your reading.

A research project becomes a network: PDFs at the leaves, notes in the middle, ideas at the hubs.

Searching across PDFs

Obsidian's search is text-based and lives over Markdown. For PDF text:

• Annotated highlights are indexed (since they are Markdown).
• PDF body text is not indexed by core Obsidian.
• Omnisearch plugin indexes PDF content too.

For cross-PDF search, install Omnisearch. The tradeoff is some indexing overhead.

Sync

Obsidian sync options:

• Obsidian Sync (paid; encrypted; tied to Obsidian).
• iCloud / OneDrive / Dropbox / Google Drive: free; works but has occasional sync conflicts on large vaults.
• Syncthing: peer-to-peer; fast; no cloud.
• Git: power users sync vaults via git.

For PDF-heavy vaults, sync size matters. External PDF storage with links keeps the vault small.

Mobile

Obsidian Mobile (iOS / Android) supports PDFs:

• Built-in viewer for read.
• Annotation plugin support varies; PDF++ has some mobile support.
• For active reading on mobile, a dedicated PDF app may work better, with notes captured in Obsidian.

Workflows worth copying

Research synthesis. Each paper is a PDF in the vault with a sibling Markdown note. Highlights extract into the note. Cross-links show which papers touch which ideas. Topic notes accumulate the relevant highlights.

Book reading. Each book is a folder with the PDF plus a chapter-by-chapter notes file. Highlights flow into chapter notes; takeaways into a book summary note.

Course or textbook study. Each lecture's PDF lives next to a lecture note. Practice problems become questions; answers reference back to specific pages.

Legal review. Each contract PDF with a sibling annotation note. Risk flags become tagged Markdown blocks. The whole corpus is queryable by tag or date.

Limits

Plugin instability. Community plugins sometimes break across Obsidian versions. Pick well-maintained ones.

Annotation portability. Highlights in Annotator's Markdown sidecar are Obsidian-specific. PDF++ can write to the PDF itself, which travels.

Performance on huge PDFs. Multi-hundred-page PDFs slow plugin rendering.

No collaboration. Obsidian is single-user; no shared annotation. For collaborative reading, use Drive comments or a dedicated tool.

Backups. Just because annotations are Markdown does not mean they back themselves up. Include the vault in your backup strategy.

Practical recipe

A working Obsidian PDF annotation setup:

1. Pick a plugin: PDF++ for most new users.
2. Vault structure: a PDFs folder; sibling Notes/papers folder for annotation notes.
3. Sync: pick one (Obsidian Sync, iCloud, Syncthing).
4. Templates: a note template per PDF type (paper, contract, book chapter).
5. Tags and links: tag highlights with topics; link to related notes.
6. Weekly review: pull recent highlights into a "this week" note.
7. Backup: full-vault backup independent of sync.

For deeper PDF edits (split, merge, sign, redact) that should not live in Obsidian, a browser tool like Docento.app runs locally without uploading.

Takeaway

Obsidian plus the right plugin is one of the best PDF annotation environments in 2026 for researchers, writers, and anyone who wants their reading to feed a long-lived knowledge base. The Markdown-first model means your annotations outlive any single tool. For the deepest PDF operations beyond annotation, pair Obsidian with a browser PDF editor that respects local-first principles. See also note-taking with PDFs in Notion, citation management with PDF papers, and academic research PDF workflow.