On 8 July 2025, Mozilla shut Pocket down. Exports stayed available for a few months, and after that the data was deleted.
For a lot of people that was the moment they discovered two things at once. That they had saved several thousand articles. And that they had read almost none of them.
Both facts are worth sitting with, because the second one is not a personal failing. It is what read-it-later systems do by default.
What the queue is actually for
The honest description: a read-it-later app is a holding pen for the gap between finding something and having attention for it.
That gap is real and worth solving. You find a good long piece at 11am on a Tuesday. Reading it now costs you the thing you were doing. Not saving it means losing it. Saving it is correct.
The failure is what happens next. Saving feels like progress, and it is not, and the feeling is strong enough to substitute for the reading. This is the collector's fallacy in its purest form: the sense of having acquired something that you have not actually acquired.
The queue then grows monotonically, because saving takes two seconds and reading takes twenty minutes. There is no arrangement of those numbers where the pile shrinks on its own.
The options after Pocket
The field consolidated after the shutdown. What is left divides by what you want it to do.
| App | Shape | Best for |
|---|---|---|
| Instapaper | The classic. Clean reader, highlights, offline, generous free tier | Just reading, without a system attached |
| Readwise Reader | Articles, RSS, newsletters, PDFs, YouTube transcripts, highlights that sync out | People who want the highlights to go somewhere |
| Raindrop.io | A bookmark manager with a reader attached | Collecting and organising links, not just reading |
| Matter | Reader plus newsletter inbox, strong mobile | Reading on a phone |
| Wallabag | Self-hosted, open source | Owning the data outright |
| Your notes app | Save the link into a note | Small volumes, no separate system to maintain |
Two practical notes. Instapaper is the low-commitment default and has outlasted almost everything else in this category, which counts for something. Readwise Reader is the only one whose real product is the layer after reading, and if highlights are the point, that is the difference that matters.
The last row is not a joke. If you save five things a week, a dedicated app is overhead. A note with links in it works, and it does not become another inbox to declare bankruptcy on.
Why the pile grows and what actually stops it
Three rules do nearly all of the work.
Save less. The lever nobody wants. Most saves are not "I want to read this", they are "this seems like the kind of thing I should read", which is a different and much weaker impulse. Before saving, ask what you are going to do with it. If there is no answer, close the tab. See information overload.
Give the queue an expiry. Anything unread after thirty days gets deleted, without reviewing it. This feels wrong and is right. If it mattered, it will come back to you from somewhere else, and if it does not come back, it did not matter. An old queue is not a library, it is a record of past intentions and it makes the whole system unpleasant to open.
Separate reading from saving in time, deliberately. A read-it-later app only works if there is a later on the calendar. Not "when I have a moment", because you will not, but an actual recurring slot. This is the same fix that makes the weekly review work and the same reason it is the first habit people drop.
A fourth, softer one: keep it to a single queue. Two apps plus browser tabs plus starred emails is not a system, it is four systems, none of which you trust. Trust is the thing that decides whether you open it at all.
The part that makes it worth keeping
A queue you only read from is a slow-motion content feed. What turns it into something durable is the handoff into your notes.
The rule: the highlight is not the note. Highlighting is fast, feels productive, and produces almost nothing on its own, for the same reasons discussed in how to highlight effectively. A folder of exported highlights is another unread pile with extra steps.
What survives is the sentence you write in your own words about why the thing mattered. One per article is plenty. That is a literature note, and it is the point at which reading stops being consumption. See how to take notes while reading and how to remember what you read.
Readwise built an entire business on automating the transport of highlights into notes apps, and it is genuinely useful, but note what it does and does not solve. It moves the text. It does not do the thinking, and the thinking is the part that makes it yours. See the generation effect.
The lesson from the shutdown
Pocket ran for fourteen years, was acquired by a well-funded nonprofit, and still closed with three months of notice.
Two things to take from that. Export before you need to, and check that the export contains the full text and your highlights rather than a list of URLs, many of which will already be dead. And do not let the queue be the only copy of anything you actually care about. If an article matters, the note about it belongs in your own notes, in a format you control.
This is the same argument as how to back up your notes, applied to the pile most people never think of as data.
The short version
Save less, expire aggressively, schedule the reading, and write one sentence per piece into your own notes.
A read-it-later queue is a good tool for the twenty minute gap between finding and reading. It is a bad tool for the twenty month gap, and left alone it will always become the second one.
More in the note inbox, the capture habit, and how to declutter your notes.