My EFFICIENT Note-Taking System using Readwise and Obsidian
Based on John Mavrick Ch.'s video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use Readwise Reader as a single capture layer for articles, epub ebooks, newsletters, and unrolled Twitter threads to avoid juggling multiple apps.
Briefing
A streamlined learning workflow is built around just two core tools—Readwise Reader for capturing and highlighting information, and Obsidian for turning that material into a searchable knowledge base. The system targets a common bottleneck in self-education: the gap between consuming content and actually producing useful notes and ideas. By routing reading, highlights, and metadata into one place, it aims to reduce app sprawl and information overwhelm while making it easier to revisit what matters.
Readwise Reader is positioned as an all-in-one intake layer that replaces multiple separate services. Instead of bookmarking articles in a dedicated app, a Chrome extension sends links directly into Readwise Reader, where highlights and annotations can be created immediately. For ebooks, uploaded epub files become readable across devices rather than being locked to a single desktop setup. Newsletters are handled by forwarding emails into a Readwise library email, letting subscriptions appear in a unified view. Even social content gets folded in: Twitter threads can be unrolled into the Readwise interface, with a “read y save thread” style workflow that adds content to the account.
Navigation and speed matter throughout. Hotkeys switch between views, and reading can be done with minimal mouse use—arrow keys for movement, and shortcuts like “h” for highlighting and unhighlighting. A command palette (triggered with Ctrl K) centralizes actions so the workflow stays fast even when the user forgets specific capabilities.
Once highlights exist, the system routes them into Obsidian using Readwise’s official plugin. After enabling the plugin in Obsidian’s community plugins, the import settings can be customized to control where notes land (by folder) and how they render. The example setup uses metadata fields such as status (e.g., a yellow indicator for notes being processed), tags describing the input type (like “book”), author and source details, and a dedicated “highlights” section. Each highlight is formatted as a quote block, with annotations appended beneath.
From there, the workflow shifts from storage to transformation. A script-based automation converts selected headings in input notes into “Atomic ideas,” reflecting a learning philosophy that books and long-form material are less effective unless their key concepts are broken into searchable, reusable units. The process uses Obsidian’s Quick Add and a JavaScript user script (via a macro) to turn level-4 headers into new notes under a summary header, applying a template and embedding the relevant header content.
The end result is a single source of truth in Obsidian: inputs remain stable, while derived idea notes become the building blocks for future writing and project work. Full-text search and note linking make it possible to retrieve concepts quickly when starting new outputs, turning scattered reading into a system that supports ongoing creation rather than passive collection.
Cornell Notes
The workflow streamlines learning by capturing reading and highlights in Readwise Reader, then importing them into Obsidian for organization and reuse. Readwise Reader consolidates bookmarks, epub ebooks, newsletter reading (via forwarding to a library email), and unrolled Twitter threads, with hotkeys and keyboard-first navigation for speed. An official Readwise plugin in Obsidian imports highlights into chosen folders and formats them with metadata, quote blocks, and annotations. A JavaScript-driven Quick Add macro can convert level-4 headings from input notes into new “Atomic ideas” notes using templates, creating smaller, searchable units for later writing and projects. This matters because it reduces app sprawl while turning consumed content into reusable knowledge.
How does Readwise Reader replace multiple separate tools in the intake stage?
What makes the Readwise reading workflow efficient for capturing highlights?
How are highlights transferred from Readwise into Obsidian, and what can be customized?
What is the role of “input notes” inside Obsidian?
How does the automation convert headings into reusable ideas?
Review Questions
- When importing highlights into Obsidian, which settings determine the destination folder and the formatting of highlights (quote blocks, metadata, and headers)?
- What specific intake sources does Readwise Reader consolidate in this system (book files, newsletters, Twitter threads, bookmarks), and how are they added?
- How does the Quick Add macro transform level-4 headings into “Atomic ideas,” and what template and folder choices affect the resulting notes?
Key Points
- 1
Use Readwise Reader as a single capture layer for articles, epub ebooks, newsletters, and unrolled Twitter threads to avoid juggling multiple apps.
- 2
Rely on keyboard-first controls (hotkeys, arrow-key navigation, and “h” for highlighting) to keep intake fast and consistent.
- 3
Import highlights into Obsidian with the official Readwise plugin, then customize folder routing and note formatting to match how you think about inputs.
- 4
Store each intake as an “input note” with metadata (status, tags, author, source) and formatted highlights so the record stays stable.
- 5
Convert selected headings from input notes into smaller “Atomic ideas” notes using a Quick Add macro and a JavaScript script to improve searchability and reuse.
- 6
Treat derived idea notes as the building blocks for future writing and projects, while leaving raw inputs as the single source of truth.