I have thousands of Readwise highlights and remember almost none of them

You opened the Readwise daily review this morning. The first card surfaced a one-line quote attributed to a book you read a few years ago. You stared at it for six seconds. You had no memory of the chapter, the argument, the page, or why you yellowed it.

You clicked next. Same thing. Next. Same thing.

By the fifth card you closed the tab. You'd done the ritual. You'd remembered nothing.

Why does Readwise highlights context decay so fast?

Readwise does one thing well: it pulls highlights from Kindle, Apple Books, Instapaper, and similar sources into one feed, with a clean markdown-friendly format. The daily review surface is well designed. The integrations with Notion, Obsidian, Roam, and Logseq mostly just work.

The gap is what gets captured. A Readwise highlight is the line you marked, plus a short title, a book or article source, an optional note you typed at the moment, and a tag or two if you tagged it. What it usually isn't, is the paragraph around the line. The chapter. The argument the sentence was supporting. The reason you cared enough to yellow it.

A highlight without the surrounding paragraph is a quote without an argument. The line "trust is built in drops and lost in buckets" means something inside the chapter on team dynamics where you found it. As a standalone card three months later, it's a fortune-cookie line you can't place. The signal that made it worth saving was in the surroundings, and the surroundings didn't come with the highlight.

Heavy Readwise users often describe a recurring pattern: libraries that grow into the thousands of highlights while the share of lines they can actually place in context stays small. The library grows. The recall does not.

What does the daily review actually do for you at scale?

The Readwise daily review is the feature most users start with, and many heavy users describe drifting away from once their library gets large. The pitch is spaced repetition for highlights: a small daily card stack that resurfaces older highlights so you don't lose them.

At small libraries the cards land in context. You remember the source. You sometimes write a follow-up note.

Once libraries grow into the thousands, the cards surface in a sequence that has no relationship to what you're working on. You scroll faster. The ritual remains, the use case erodes.

Long-time users discussing whether the daily review is still worth it often land on yes-but. Yes, the design is well-considered. But no, I'm not actually learning from it. Yes, I get the resurfacing. But no, I don't remember the context.

The failure mode is not laziness. The failure mode is structural. A daily review card with no paragraph context is a recognition test on a snippet your brain doesn't have an anchor for.

Why does more tagging not fix the Readwise highlight problem?

Readwise supports tags, notes per highlight, and a quote-styled note editor. Power users sometimes try to fix the context gap by retagging old highlights, adding paragraph context manually, or writing short summaries per chapter.

It's the same trap note-taking power users hit. The maintenance cost scales linearly with the library size. A retag pass over a large library takes most people a full weekend.

The Readwise team has shipped genuinely useful improvements over the past couple of years: GhostReader (AI-assisted summaries of highlights), better daily review controls, smarter tagging, integration improvements. None of them fully close the underlying gap. The system captures the yellow line. It does not capture the why.

And it cannot, easily. Asking the reader to type a sentence of context per highlight would slow down reading enough that most people would just stop highlighting. The friction has to stay low for the capture to happen. Which means the context has to come from somewhere else.

What is Readwise honest about, and what is not it?

If the job is "get my highlights out of fragmented apps and into one searchable feed," Readwise is well-established for this work.

The place Readwise is honest about itself is the daily review. The team has acknowledged that the review is a starting point, not the whole story. They've added GhostReader summaries, better filtering, and tag-based review streams to address the context gap. The gap remains because it's structural, not because they haven't tried.

Where Readwise's product fit narrows is the question of recall. The product is built for capture, organization, and resurfacing. It is not built for "I half-remember a thing about trust from a book I read a year ago, find it." The search is keyword-based. You have to know the words. If you don't remember the words, the highlight might as well not be there.

How does dEssence help with the context gap Readwise leaves?

Readwise is a highlight tool. dEssence is memory you don't have to maintain. Different jobs.

The Readwise daily review is the resurfacing of yellowed lines. The dEssence ask is the other direction: you describe what you're looking for the way you'd describe it to a friend, and the system returns what you saved, with the surrounding context.

When you save into dEssence from the Chrome extension while reading, the page comes with its paragraph, its source, the time and place you saved it. When you forward an article excerpt to the Telegram bot, the full excerpt and the source go in together. When you paste a passage into the web app at dessence.ai, the surrounding text comes with it. No folders, no tags, no organizing. Save it, forget it, ask for it later.

Later you ask in your own words. "That thing about trust building in drops and lost in buckets, from the leadership book I was reading last spring." The line comes back with the paragraph, the source, the date, and any note you wrote at the time. Not as a daily-review card you didn't ask for. As an answer to the question you actually have.

The two tools are complementary if you read a lot. Readwise stays the highlight extractor and the integration hub. dEssence holds the longer passages, the surrounding context, the articles and threads and posts you want to come back to with intent.

Honest about dEssence: it's in beta, with no native iOS or Android app yet. The three save surfaces are Chrome extension, Telegram bot, or the web app at dessence.ai. The Pro tier isn't finalized. No team or shared-library features. The free tier caps at 500 items, less than a year of heavy clipping for most active readers. dEssence does not extract highlights from Kindle or Apple Books the way Readwise does. If the job is "pull yellow lines from every ebook source into one feed," Readwise is the right tool, not dEssence.

What dEssence is, is the place to send the longer context, so the highlights you keep in Readwise stop being orphans.

Should you cancel Readwise?

The useful move is usually to lower the expectation of what the daily review can do, and add a recall-focused tool alongside it. Use Readwise for capture, export, and daily resurfacing at small scale. Use a separate tool for the contextual ask, the "find me that thing about trust from last spring" question.

Frequently Asked Questions

Why don't I remember my Readwise highlights?

Mostly because a highlight is a yellow line without the paragraph around it. The signal that made the line worth saving was in the surroundings, and Readwise captures the line cleanly but doesn't usually save the chapter context with it.

Is the Readwise daily review actually useful?

At small library sizes (a few hundred highlights), yes: the resurfacing genuinely helps recall. The Readwise team has shipped GhostReader summaries and tag-filtered reviews to help, but the structural gap (snippet without surroundings) remains.

What's the difference between Readwise and Readwise Reader?

Readwise (the highlight aggregator) pulls yellow lines from Kindle, Apple Books, Instapaper, and similar sources into one feed with daily review. Readwise Reader is a separate read-later app bundled with the same subscription. They share an account and an integration pipeline.

How many Readwise highlights is too many?

The library still works as a searchable archive at any size. The resurfacing feature is what stops scaling once libraries grow well into the thousands.

What can I use alongside Readwise for context?

A recall-focused tool that holds longer passages and surrounding paragraphs, rather than yellow lines alone, complements Readwise well. The split-the-jobs move applies: keep Readwise for highlight extraction and export to Notion or Obsidian, and use a separate tool for the contextual ask. dEssence is one option, with Chrome extension, Telegram bot, or the web app at dessence.ai, plus natural-language recall.