Pocket Is Dead. What Do You Do With Your Bookmark Graveyard?

Pocket, the read-it-later app most people in tech have used at some point, is shutting down. Mozilla pulled the plug. Users have a window to export their saved articles, then the lights go out. The obvious question is which Pocket alternative to switch to. The better question is what that pile of unread saves was actually for.

I want to be honest about something before we go any further.

I had a Pocket account for years. By the time Mozilla announced the shutdown, it held a few hundred articles. The kind of count that creeps up across years of saving without ever auditing. I could probably name three or four of them from memory. The rest were ghosts. Saved with good intent, abandoned the moment the tab closed.

That's the Bookmark Graveyard. And if you're reading this because Pocket is dying and you're trying to figure out where to migrate, you might want to sit with that for a second before you sign up for the next one.

Why Did Pocket Actually Die?

Mozilla framed the shutdown as a strategic refocus on Firefox. That's true on paper. The underlying reason is more uncomfortable: read-it-later as a category never quite worked.

Pocket launched in 2007 as Read It Later, built by Nate Weiner. It nailed a real problem at the time. The web was getting cluttered, articles were getting longer, and people wanted a way to strip ads and read on a phone later. Mozilla bought it in 2017 and bundled it into Firefox. For a while it was the default save button for thoughtful internet readers.

The problem wasn't the app. The app was good. The problem was that the act of saving an article and the act of reading an article are not the same thing, and the gap between them is enormous.

People kept saving. They kept not reading. Save rates are high across the category. Return rates are low. The library balloons. The reading does not. Eventually Mozilla looked at the numbers and decided the engineering cost wasn't worth a feature most users had stopped opening.

Pocket didn't fail. The job-to-be-done failed. Saving articles for later, as a stand-alone behaviour, doesn't translate into actually reading them. The shutdown is the funeral. The death happened years ago.

You can switch to Instapaper, Matter, Readwise Reader, or Raindrop.io. Each will accept your imported HTML file and store your old saves dutifully. None of them, by themselves, will make you read what you saved. The migration is the easy part. The honest audit is harder.

What Is the Bookmark Graveyard?

The Bookmark Graveyard is the gap between what you saved and what you actually read.

It looks like this. You're scrolling, you spot a long article that looks good, you don't have time, so you tap save. The save feels like a small victory. You've made a commitment to your future self. Future-you will read this. Future-you sounds smart and well-rested and has 45 minutes free.

Future-you never shows up.

The article sits there. You save another one the next day. And another. After six months you have a list of 200 articles you genuinely intended to read, which now functions as a passive monument to all the thinking you meant to do and didn't.

Behavioural psychology has a name for this. It's a substitute action. The save is doing the emotional work that the reading was supposed to do, without doing the actual work. Same shape, different content. You feel like you're learning. You're filing.

The graveyard is the natural endpoint of any save tool that doesn't have a strong return mechanism. The save is one tap. The return requires intention, time, a free attention slot, and a reason to pick this article over the new one. Five frictions vs one. The maths is simple. The save wins. The return loses. The graveyard grows.

This isn't a Pocket problem. It's the problem read-it-later was always going to have, because the design only solved the first half.

What read-it-later apps optimise for	What actually drives reading
Save speed (one tap)	Return cues (notification, audio, time slot)
Clean reader view	A reason to open the app today
Tag and folder structures	A retrieval prompt that surfaces old saves
Cross-device sync	Integration with how you actually consume (commute, walk, dishes)
Library size	Completion rate

If you've ever opened your read-it-later app, scrolled the list, felt tired, and closed it again, you've experienced the graveyard. It's not a personal failure. It's the predictable output of a system that optimised for the wrong half.

Why Do You Save Articles You Never Read?

Saving feels like reading. That's the whole trick.

When you tap the save button, your brain processes it as a small commitment. The article has been claimed. It's in your library now. It's "yours". You've moved from passive scroller to engaged reader, in your own internal narrative, in the time it took to tap a button. The dopamine hit is similar to actually reading something useful. The cognitive cost is roughly zero.

Reading the article would take 15-40 minutes. It would require sustained attention, no phone interruptions, and the willingness to confront whether you actually understand what the author is saying. The save is much easier and the brain gets to feel the same way about itself.

This is the heart of the read-it-later trap, and Pocket can't be blamed for it. The trap was the human, not the app. We use saving as a way to relieve the small guilt of not reading, without doing the harder thing of actually reading. The save is a coping behaviour dressed as a productive one.

Three things make this worse over time:

One. The bigger the library gets, the less likely any one item gets opened. 200 articles is psychologically harder to face than 20. The larger the graveyard, the more it self-perpetuates.

Two. The save doesn't expire. Articles you saved 14 months ago sit next to articles you saved this morning. The urgency that triggered the save fades, but the article stays in the list as a quiet reminder of past you's good intentions.

Three. Most saves happen in low-attention moments. You save while half-watching TV, or in a meeting, or on the toilet. The save is opportunistic. The reading would need to be deliberate. The contexts don't match.

For more on the brain mechanics under this, see why you forget articles within a week.

Is There Such a Thing as a Read-It-Later App That Actually Works?

A read-it-later app works only if it closes the loop between save and return. Most don't.

The category has been competing on the wrong axis for fifteen years. Save speed. Reader-view typography. Highlight syncing. Tag systems. These are all real features. None of them affect whether you come back. They affect what happens once you do.

The apps that actually move completion rates do something else. They build a reason to open the app on a regular schedule, separate from the moment of saving. They surface old saves actively rather than waiting for you to remember. They integrate with a moment in your day where reading is realistic, like a commute or a walk or doing the dishes.

A few patterns that genuinely close the loop:

Audio playback. If saved articles can be listened to during a commute, walk, or workout, the return doesn't need a free 45-minute slot at a desk. It needs a 20-minute walk you were going to do anyway. The save fills dead time instead of stealing alive time.

Daily digest with limits. A daily email with 2-3 saved articles forces a return at a regular time. The constraint is the feature: you only get a few, they're already chosen, decision cost is low.

Surfacing old saves. "You saved this 47 days ago. Still want it?" prompts make the graveyard visible. Most apps hide it with reverse chronological order. Surfacing forces a decision: read, archive, or admit it's gone.

A short summary first. A 3-bullet summary or 60-second audio preview before the full article lets you decide whether the long read is still worth your time. Sounds like it would replace reading. In practice it filters the graveyard and gets you reading the right things.

Pattern	Closes which gap	What it costs to build
Audio playback	Save-to-return time slot mismatch	High (TTS quality, sync)
Daily digest	Forgotten saves, low return rate	Low (cron job, email)
Old-save surfacing	Graveyard psychology	Medium (UX work)
Pre-read summary	Decision fatigue at return	Medium (LLM cost)

You can build a save tool without any of these. It will look great in screenshots. It will not change how much you actually read. The fix is not in the save flow. The fix is in the return flow.

What Should You Actually Do With Your Pocket Export?

Most advice you'll read this week says "import your HTML into [alternative app]". I want to suggest something else first. Audit it.

When you export from Pocket, you get an HTML file with every saved article. Open it in a browser. Scroll. Read the titles. Notice the years. Pay attention to which ones spark anything: a memory, a feeling, an "oh yeah I really wanted to read that". Most won't. That's the data.

Then ask three questions about each one.

Did I want this 12 months ago, or do I want it now? Past you and current you are not the same person. Articles saved during a job you've left or a project you've finished aren't relevant just because they're in the file. About 60-80% of any old read-it-later library is past-you's intentions, not current-you's interests.

If I had 30 minutes right now, would I read this one? This is the actual test. Not "would I save this", but "would I read this now". Most saved articles fail it instantly. The honest answer is no. That's fine. Now you know.

What context would I need to read this? Some articles need a quiet hour and a notebook. Some need a 20-minute walk and headphones. Some need a Sunday morning and a coffee. If the right context never happens in your life, the save is unread by default.

After that audit, you'll probably have a much smaller list of articles you actually want. Maybe 10-20%. Import only those. The graveyard does not need to migrate with you.

Then ask the harder question: what was missing from Pocket that would have made you actually read those? An audio version? A daily nudge? A 3-bullet summary first? Whatever's missing is what your next tool needs to have. Saving better is not the answer. Returning better is.

How Do You Make Sure Saved Articles Actually Get Read?

Build the return into your day before you build the save into your phone.

The strongest predictor of whether a saved article gets read is whether there's a regular slot in your week where reading is the natural thing to do. Without that slot, no app fixes it. With that slot, almost any app works.

Some structures that work:

The commute slot. Walking, driving, train. 20-45 minutes, hands and eyes often busy, attention available. Audio reading turns this slot into reading time. If your saved articles can play as audio during your commute, your return rate goes up dramatically because the cost of returning is near zero.

The morning slot. 15-30 minutes with coffee before the day starts. One article. No phone notifications. Same time every day. Works for people willing to defend the slot, which most aren't.

The Sunday catch-up. A weekly hour scrolling your saved list and picking one or two long reads. Works for some. The risk: if you miss it, you've lost the only return cue, and the list grows for 30 days uncontested.

Reading with someone. A friend, a partner, a book club. The social commitment becomes the return cue. This is why book clubs work and read-it-later apps don't.

The app is downstream of the slot. No slot, no reading habit. Just a saving habit. They look similar from outside. They produce very different libraries.

This is roughly how I think about Alexandria. We started building it because the read-it-later category had clearly failed at the return half, and the fix wasn't another save button. The product is built around audio playback (commute slot), daily digests of saved articles (return cue), and synced word-by-word highlighting via the FlowRead feature (so the audio actually anchors attention). The same logic applies whether you use Alexandria or anything else.

For the science underneath this, why you forget everything you read covers the memory side. The short version: the brain forgets about 70% of new information within 24 hours unless something brings it back. Read-it-later apps without return mechanisms are saving things straight into that 70%. If you've been moving the same problem between tools, why Notion and Obsidian don't fix the bookmark graveyard either is the closest read.

What Should You Actually Switch To?

This depends on what part of the problem you have, not what the apps are called.

If your Pocket library was small and active, you mostly read what you saved, and you just need a place to keep saving, almost any alternative works. Instapaper is the closest descendant, simple and stable. Raindrop.io if you save more than articles. Matter has a strong reader experience. Readwise Reader if you also want highlights in a knowledge graph.

If your Pocket library was a graveyard (most people), the choice matters more. Look for a return mechanism baked in, not just a save button. Daily digests, audio playback, summary previews, active resurfacing of old saves. Without these, you'll rebuild the same graveyard in a new app within four months.

If you mostly read on commutes, walks, or while doing other things, high-quality TTS or a good audio player is non-negotiable. The save is useful only if the return fits your actual life, and your actual life involves moments where your eyes are busy and your ears are free.

If you don't have a regular reading slot at all, no app will fix that. Build the slot first. Then pick the tool.

Pocket dying is a small inconvenience. Most read-it-later libraries being graveyards is the actual issue, and Mozilla shutting it down doesn't change that. You'll either solve it now, while you're already auditing your saves, or port the same problem to a new logo and notice it again in 18 months.

The shutdown gave you a clean reason to look at the pile. Use it.

Frequently Asked Questions

Why is Pocket shutting down?

Mozilla announced Pocket's shutdown as part of a strategic refocus on Firefox. The service had been declining in active use for years. Mozilla provided a window for users to export their saved articles before data deletion. The shutdown reflects a wider truth: read-it-later, as a category, never really worked as a reading habit.

What is a Bookmark Graveyard?

A Bookmark Graveyard is a saved-articles list that grows much faster than it gets read. The bookmark gets used as a coping action, not a commitment. The graveyard is the gap between intent ("I'll read this later") and behaviour ("I never actually came back"). Most read-it-later accounts are graveyards by month two.

What is the best alternative to Pocket?

Instapaper, Matter, Readwise Reader, and Raindrop.io are common Pocket alternatives. They cover the save-and-strip-clutter need well. The harder question is whether you need another save button at all, or whether you need a system that actually returns saved articles to you so they get read and remembered.

Is read-it-later a useful habit?

Saving an article is only useful if you come back to it. Behavioural research on intention-action gaps shows most saved tasks decay rapidly without a return cue. A read-it-later app without a return mechanism (notifications, daily digest, audio playback during walks) becomes a graveyard. The save is the easy part. The return is the whole point.

How can I export my Pocket data?

Mozilla provides an export tool in Pocket account settings that produces an HTML file of all saved articles. The file includes URLs, titles, and tags. Most read-it-later alternatives accept this HTML import directly. Export your archive before the shutdown deadline; once your account is deleted, the data is gone.

Why do I save so many articles I never read?

Saving an article reduces the immediate guilt of not reading it. The save feels like progress because it pretends to be a commitment. Behavioural psychology calls this a substitute action: doing something easier that resembles the harder thing. Most people aren't building a reading list. They're outsourcing a decision they didn't want to make.

What should I switch to after Pocket?

Switch to whatever closes the loop between save and return. If you save articles but never read them, another save button doesn't fix the problem. Tools that surface saved content actively (audio playback during commutes, daily reading digests, summary cards before you re-read) tend to convert saves into actual reading. The right tool depends on when in your day you'd actually read.

How many articles do most people save and never read?

Industry estimates of read-it-later usage suggest the typical user saves several times more articles than they finish. Pocket itself rarely published completion rates. The pattern is well documented in app analytics across the category: high save rate, low return rate, long tail of stale items. The list grows; the reading does not.