Problems & Fixes
When your highlights are trapped in different apps — Kindle on one platform, web articles in another, PDFs in a third — you can't search them together and can't use them in your work without re-finding each one. Here's how to consolidate your highlights and build a system that makes them actually usable.
You highlighted a passage 6 months ago that's exactly what you need for what you're working on now. You know you highlighted it. The question is: where?
Was it in Kindle? You check the Kindle app. Hundreds of highlights across dozens of books, searchable only by keyword within a book if you remember which book. Was it in Readwise? You search Readwise. You find something close but not the exact passage. Was it in the PDF you annotated? You check your PDF reader — which one? Skim PDF? Zotero? Adobe? Was it in the Pocket article you highlighted? Was it in your personal notes where you copied it at the time?
After 10 minutes, you either find it (by luck) or give up and try to reconstruct from memory.
When your highlights are trapped in different apps, the act of highlighting becomes a form of misleading bookkeeping: you think you've captured something for future use, but you've actually created the need to remember not just the content but the container — which tool, which book, which annotation system you were using that day.
Root cause 1: Different media use different tools.
Books use Kindle (if e-books) or physical highlighting (if print). Web articles use Pocket highlights, Readwise Reader, or direct browser highlighting. PDFs use PDF annotation tools (Adobe, Skim, Zotero). Academic papers use reference managers. Each medium has its own native highlighting ecosystem, and the ecosystems don't talk to each other by default.
Root cause 2: You've used different tools at different times.
Your highlighting setup has evolved. Before Readwise, you used Kindle native highlights and sometimes exported them. Before Readwise Reader, you used Pocket for web articles. The tools you're using now aren't the tools you were using 2 years ago, which means your older highlights are in legacy tools that may not be integrated with your current workflow.
Root cause 3: No aggregation layer.
The tools that create highlights (Kindle, PDF readers, Pocket, physical books) aren't the same as the tools that organize knowledge (Notion, Obsidian, Roam). The gap between "where highlights are created" and "where you do your thinking" means highlights stay in the creation tool rather than flowing into the knowledge system. Readwise was specifically designed to bridge this gap, but it doesn't cover every highlight source and not everyone uses it.
Root cause 4: Highlights from physical books are in a different category.
Anything highlighted in a physical book requires either manual transcription or a scanning tool to enter the digital system. Most people don't do either — the physical highlights stay in the physical book, effectively unavailable unless you re-read that specific book.
Root cause 5: Highlights without notes are hard to search.
A highlight says "I found this important." A highlight with a note says "I found this important because X." Without the note, searching your highlights later requires finding the specific passage in the original source — which requires remembering the source. With a note, the search hits your note text, which is in your own vocabulary and easier to match against your recall.
Highlighting is a reading technique. It's valuable to the extent that it helps you retain, retrieve, or use the material you highlighted. If your highlights are trapped in different apps, inaccessible without knowing which container to search, they are not serving that purpose. They're a record of attention that doesn't translate into accessible knowledge.
The test: can you search across all your highlights with one query and find the relevant passage? If not, your highlight system is underperforming.
The goal is not a perfect aggregate of every highlight you've ever made. The goal is highlights that are:
Layer 1: Collection — where highlights are created Layer 2: Aggregation — where highlights from all sources are unified Layer 3: Integration — where selected highlights become part of your PKM
Most highlight systems only have Layer 1. The fix is building Layers 2 and 3.
Step 1: Audit where your highlights currently live.
List every tool that contains highlights:
This audit reveals the scope of the fragmentation and the specific systems you need to connect.
Step 2: Choose an aggregation layer.
The aggregation layer is the tool where highlights from all sources flow. Current options:
| Aggregator | Sources it connects | Coverage gaps |
|---|---|---|
| Readwise | Kindle, Pocket, Instapaper, Readwise Reader, Twitter, manual import | PDFs vary; physical books require manual entry |
| Readwise Reader | Built-in; plus imports from Kindle | Not all sources auto-import |
| Notion (manual) | Any source you manually copy into it | Fully manual; high effort |
| Obsidian (manual or Readwise plugin) | Readwise syncs automatically | Still requires Readwise as the upstream aggregator |
Readwise is the most mature and widely-used aggregation layer for reading highlights. It automatically collects from Kindle, major read-later apps, Twitter, and other sources, and syncs to Notion, Obsidian, and other PKMs via official integrations. If you highlight across multiple digital sources, Readwise is the most practical current solution for Layer 2.
The limitation: Readwise is a paid subscription ($8-10/month as of writing). For people who highlight heavily across multiple sources, this is often worth it. For light highlighters with a simpler reading workflow, manual approaches may be more appropriate.
Step 3: Handle physical book highlights separately.
Physical books are the awkward edge case. Options:
Step 4: Add notes to your highlights at read time.
Highlights without notes are opaque — they record that something was important, not why. When highlighting, add a brief note to the highlights you care most about:
Notes transform highlights from passive markers to active knowledge. They also make highlights searchable in your own vocabulary rather than requiring exact-phrase matches from the original text.
Step 5: Connect selected highlights to your PKM.
Not every highlight deserves to be in your PKM. The best 10-20% should flow from the aggregation layer (Readwise) into your PKM (Notion, Obsidian), where they connect to your own thinking, link to related ideas, and become part of your working knowledge.
The mechanism: Readwise → Notion or Obsidian integration. Each day or week, Readwise resurfaces a set of highlights (spaced repetition), and you decide which ones to develop into notes in your PKM.
| Tool | Role | Integration | Gap |
|---|---|---|---|
| Kindle | Creates highlights for ebooks | Syncs to Readwise | Amazon-only; no PDFs |
| Read-later + highlights | Syncs to Readwise | Highlights limited vs. Readwise Reader | |
| Readwise Reader | Read-later + best-in-class highlighting | Syncs to Readwise; then to PKM | Subscription required |
| Readwise | Aggregates highlights from many sources | Connects to Notion, Obsidian, Roam, etc. | Subscription; physical books limited |
| Notability / GoodNotes | iPad PDF annotation | Manual export required | Not auto-integrated |
| Zotero | PDF highlights + citations | Can export to Obsidian | Academic-focused |
| WebSnips | Web content capture + notes | For web reference, not highlight extraction | Not a highlight aggregator |
WebSnips alongside highlights: WebSnips handles a specific adjacent case: when you're reading something on the web and want to capture not just a highlighted passage but the full context of that passage — the article, your note about why it matters, and a full-text searchable archive. While Readwise handles the "extract highlights from reading" use case, WebSnips handles "save this source for reference, with context." For knowledge workers who both highlight and build reference libraries, these serve different purposes: highlights capture what resonated; WebSnips captures what you'll need to return to and retrieve.
Note at highlight time, not later: When you highlight something meaningful, add a one-sentence note in the same moment. The moment of highlighting is when you're most clear about why it matters; that clarity evaporates quickly.
The Readwise daily review habit: If you're using Readwise, take 5 minutes daily to review the resurfaces highlights. This creates the spaced repetition that moves highlights from "I marked this" to "I actually remember and can use this."
The "promote to note" weekly habit: Once a week, review highlights from the past week's reading. For the 2-3 that are most valuable or most connected to current work, write a brief note in your PKM that develops the highlighted idea further. These promoted highlights become real knowledge; the rest remain useful but lower-priority.
Consistent tool choice going forward: The fragmentation problem grows with each new tool you add. Going forward, standardize: one tool for ebooks (Kindle), one for web reading (Readwise Reader), one aggregator (Readwise). New tools require an integration plan before adoption.
When your highlights are trapped in different apps, the fix requires building the middle layer that's currently missing: an aggregation tool that pulls highlights from all your reading sources into one searchable place, combined with a promotion habit that moves the most valuable highlights into your PKM as developed notes. With that architecture in place, the highlights you've been making across years of reading become a unified, searchable knowledge base rather than a fragmented collection of annotations that requires knowing exactly where to look.
More WebSnips articles that pair well with this topic.
Link rot is inevitable — but losing the information behind a dead link doesn't have to be. Here's what link rot is, why it's worse than most people realize, how to recover what you can, and how to save content in ways that survive it.
Can't remember what you read last week? The problem isn't your memory — it's that reading without a retention system produces knowledge that evaporates within days. Here's the fix: what causes reading amnesia and how to build a system that makes what you read stick.
When you can't share research with your team easily, valuable intelligence stays siloed and the team re-researches what individuals already know. Here's how to build a shared research system that makes team knowledge genuinely accessible and collaborative.