Get AI summaries of any video or article — Sign up free
Official Obsidian Plugin for Readwise | Full Product Walkthrough thumbnail

Official Obsidian Plugin for Readwise | Full Product Walkthrough

Systematic Mastery·
5 min read

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

TL;DR

The official Readwise plugin exports highlights into Obsidian as structured notes designed for graph-based discovery and linking.

Briefing

Readwise’s official Obsidian plugin is built to turn highlights from books, articles, and even transcribed podcasts into searchable, linkable notes inside an Obsidian “second brain”—with tags carried over so the highlights can plug directly into an existing knowledge graph. The practical payoff is retention plus active reuse: instead of re-digging through old notebooks or margins, users can surface past ideas on demand and connect them to new notes months later.

The walkthrough starts with what appears in Obsidian after syncing. A synced book becomes a structured note containing that book’s highlights, and—newly—tags added to highlights in Readwise also sync into Obsidian. That tag mirroring matters because it enables graph-based discovery: searching for a tag like “mastery” can pull up every highlight ever tagged that way across the entire vault, not just within a single book. The plugin’s export approach is also described as intentionally integrated with Readwise’s templating options. While community plugins exist, the official integration is positioned as smoother and more customizable, including how document tags and topic prefixes are inserted into each synced file.

Beyond formatting, the plugin adds control over what gets imported. A filtering option lets users exclude certain sources—such as tweets or other highlight-heavy categories—so sensitive or unwanted material doesn’t land in Obsidian. Setup then focuses on operational details: choosing a base folder for synced content, setting a resync frequency (the example uses 24 hours to avoid overloading the Readwise server), enabling automatic syncing when Obsidian opens, and using “recent deleted files” to optionally recreate files that were deleted after a sync. Formatting settings can also link highlight dates to daily notes, creating a timeline trail that supports local graph exploration of when ideas arrived.

Once synced, the workflow shifts from passive storage to active thinking. The walkthrough demonstrates creating a new Obsidian note and pulling in inspiration from Readwise highlights—using tags as a starting point for ideation. A “mastery” tag session shows how Readwise-sourced highlights (blue) can sit alongside user-written notes (yellow), with links already established so the graph view becomes a launchpad for drafting and expanding themes.

Podcast highlights are treated as a standout capability. The integration relies on transcriptions produced by a separate app called Air, which lets users capture “best moments” from podcasts on iPhone (Android is on a waitlist). Those captured segments sync into Readwise and then into Obsidian, enabling users to quote or reference specific spoken ideas directly in their notes.

Finally, the broader Readwise system is summarized as the engine behind retention: daily reviews with streaks, recency and frequency tuning to bias what resurfaces, and highlight categories spanning books, articles, tweets, and podcasts. Supplemental books can add highlights from books the user marked as read elsewhere (e.g., via Goodreads), and “Mastery” can turn highlights into flash-card style prompts. The walkthrough closes by emphasizing Readwise’s wide integration ecosystem (Instapaper, Kindle, Apple Books, Goodreads, and more) and a “killer feature” for physical books—photographing pages, selecting text in the image, and importing it as highlights—so the same capture-to-graph workflow can extend beyond digital reading.

Cornell Notes

Readwise’s official Obsidian plugin syncs highlights from books, articles, and transcribed podcasts into Obsidian as structured notes, turning reading into a searchable, linkable knowledge graph. A key upgrade is tag syncing: tags applied to highlights in Readwise also appear in Obsidian, enabling fast discovery across the entire vault (e.g., finding every highlight tagged “mastery”). The plugin also supports templating and formatting controls, including adding document/topic tags and linking highlight dates to daily notes for timeline-based graph exploration. Filtering options let users exclude unwanted or sensitive sources from syncing. Combined with Readwise’s daily review system (recency/frequency tuning, streaks, and categories like supplemental books), the workflow supports both retention and active idea reuse.

What makes the Readwise-to-Obsidian sync more than simple exporting of highlights?

The plugin syncs highlights into Obsidian in a way that supports graph-based retrieval and linking. Most importantly, tags added to highlights in Readwise also sync into Obsidian, so searching for a tag (like “mastery”) surfaces every tagged highlight across the vault. That means highlights become reusable building blocks for new notes, not just static records inside one book file.

How does templating affect how highlights become navigable in Obsidian?

Templating determines how each synced highlight file is structured. In the example setup, synced book files include document tags and topic prefixes in the header. Those topic tags are then linked to dedicated “topic” notes, which are further linked to domain roots—creating a navigable graph where highlights connect to themes and themes connect to broader areas of the knowledge system.

Why does the plugin include filtering and “recent deleted files,” and how do they change day-to-day control?

Filtering lets users prevent certain sources (like tweets or other categories) from syncing into Obsidian, which helps keep the second brain clean and protects sensitive material. “Recent deleted files” addresses a common workflow issue: if a user edits or deletes a plugin-created note after syncing, resync can recreate the file so highlights aren’t lost unintentionally; disabling it stops that recreation.

How are podcast highlights captured and turned into Obsidian notes?

Podcast segments are captured using Air, which transcribes podcasts and lets users highlight “best moments” (iPhone only; Android is on a waitlist). Those highlighted segments sync into Readwise, and then the Obsidian plugin exports them into the vault. The result is the ability to reference specific spoken ideas directly inside Obsidian notes.

How do tags drive ideation in the Obsidian workflow described?

Tags act as an entry point for writing sessions. With tag syncing enabled, Readwise-sourced highlights appear alongside user notes in graph view. A user can start from a theme tag (e.g., “mastery”), then link from highlights to draft notes, and expand the theme by adding new associations and links—turning retrieval into creation.

What retention mechanism in Readwise complements the Obsidian graph workflow?

Readwise’s daily review system. It uses streaks and configurable highlight selection based on recency and frequency tuning—so recently read material is more likely to reappear, and priority books can be weighted higher. Categories like supplemental books can also surface highlights from books marked as read elsewhere (e.g., via Goodreads), even if the user didn’t create their own highlights.

Review Questions

  1. How does tag syncing between Readwise and Obsidian change the way you search and connect ideas across your vault?
  2. What are two reasons filtering and “recent deleted files” settings matter for maintaining a trustworthy second brain?
  3. Describe one workflow for turning a podcast moment into a linked Obsidian note, from capture to sync to graph use.

Key Points

  1. 1

    The official Readwise plugin exports highlights into Obsidian as structured notes designed for graph-based discovery and linking.

  2. 2

    Readwise highlight tags sync into Obsidian, enabling vault-wide retrieval by tag (e.g., every “mastery” highlight).

  3. 3

    Templating controls how synced files are organized, including document tags, topic prefixes, and optional date links to daily notes.

  4. 4

    Filtering settings let users exclude specific sources (like tweets) from syncing to keep the vault clean and protect sensitive content.

  5. 5

    Operational settings such as resync frequency, auto-sync on Obsidian open, and “recent deleted files” determine how resilient the workflow is to edits and deletions.

  6. 6

    Podcast highlights can be captured via Air (transcription-based), synced into Readwise, and then exported into Obsidian for direct note reuse.

  7. 7

    Readwise’s daily review (streaks plus recency/frequency tuning and categories like supplemental books) supports retention so highlights keep resurfacing for active use.

Highlights

Tag syncing is positioned as the unlock: highlights tagged in Readwise become instantly discoverable inside Obsidian’s graph via the same tag vocabulary.
Each synced book note is organized through templating, letting users build navigable structures like topic notes linked to domain roots.
Podcast capture is made practical through Air’s transcription-based “best moments,” which then flow into Readwise and into Obsidian.
“Recent deleted files” offers a safety net: deleted plugin-created highlight files can be recreated on resync unless the option is disabled.
Readwise’s daily review uses recency and frequency tuning to bias what resurfaces—turning passive highlights into an ongoing learning loop.

Topics

  • Readwise Plugin
  • Obsidian Sync
  • Highlight Tags
  • Podcast Capture
  • Daily Review Tuning