Readwise Reader - How I Process EVERYTHING I Read

Readwise Reader is positioned as a single “inbox-to-notes” system that captures information from across the internet—articles, RSS, newsletters, Twitter, and even YouTube transcripts—then exports highlights and notes into tools like Obsidian or Notion without stitching together multiple apps. The practical payoff is reducing the mental friction of consuming content just to manage it later: instead of juggling browser extensions, separate RSS readers, and podcast workflows, Reader funnels sources into one place and keeps the capture-to-organization loop tight.

At the center of the workflow is Reader’s centralized library, split into a Home tab, a Library tab, and a Feed tab. The Home tab acts like a Netflix-style dashboard for continuing reading, with configurable sections such as recently added items, quick reads, and long reads. The Library functions like a triage queue: nothing is meant to linger indefinitely in the inbox. Items saved from the web land in the inbox first, then get moved to Later/Archive or deleted after review—mirroring a to-do list mentality rather than an ever-growing reading pile.

Reader’s editing experience is built for speed and consistency. Navigation and actions run heavily through keyboard shortcuts: arrow keys move through the text, bracket keys hide side panels, “h” highlights the current paragraph for export, “t” tags, and “o” jumps to the source website. A command palette (Ctrl/Cmd+K) provides metadata and note actions, including author and domain details, save timing, estimated reading time, and the ability to create document notes. Search is also keyboard-driven (forward slash), and Reader can read highlighted content back at adjustable speeds—available on mobile first, with desktop voice playback promised.

The standout feature is note-taking on video and social content. For YouTube, the browser extension pulls the transcript into Reader, syncs playback position with the transcript, and lets users highlight specific segments that later appear in Obsidian. The workflow extends to Twitter threads as well: threads can be shared into Reader, then highlighted and saved like any other article. Because Reader is still in public beta, occasional parsing errors can occur, and video highlights currently land under an Articles folder with a dedicated video section expected later.

On the ingestion side, the Feed tab aggregates subscriptions and discovery. It supports Twitter lists (by pasting a public list URL), newsletters via special forwarding addresses, and RSS subscriptions directly inside Reader. Feeds can be managed with frequency awareness—high-post-rate sources are flagged as likely clutter—and Reader also includes “suggested” feeds based on reading behavior. Filtered views on the sidebar let users define what appears using query-like syntax.

Finally, Reader’s value compounds through integrations. A “Ghost Reader” command can summarize content and generate questions or Q&A pairs based on existing highlights. In Obsidian, a Readwise Official plugin exports content into a structured folder (books, articles, tweets, podcasts) and supports resync scheduling. The transcript also notes a pricing shift planned after beta: new subscribers are expected to pay more later, while beta subscribers are promised lifetime access at $7.99—framing Reader as a practical “no-brainer” adoption point for anyone building a personal knowledge system.