Pocket shut down on July 8, 2025. The export tool closed November 12, 2025. If you missed the export window, that data is gone from Mozilla's servers. Even so, the underlying habit didn't go away — I still save five to ten articles a day, and so does everyone I've talked to who used Pocket seriously.

This page is the honest workflow guide I wish someone had written for the post-Pocket period: where to save things today, how to recover what you can, and — most importantly — how to avoid quietly rebuilding the same unread pile in a new tool.

30-second map

The post-Pocket save workflow comes down to two questions:

Do you have a Pocket HTML export? If yes → archive it somewhere durable (Raindrop / Wallabag / a local folder). If no → accept the loss; below for partial recovery options.
Where are you saving new articles today?Browser bookmarks aren't a system. Pick one active queue (Burn / Matter / Readwise / Instapaper) and one archive (Raindrop / Wallabag). Don't let them be the same tool unless you accept the trade-off.

What Still Works for Saving Articles in 2026

The category did not collapse with Pocket. Several tools picked up Pocket refugees and one or two of them actively rebuilt to handle the migration. Here are the five real save surfaces today, with what each one is actually good at:

Apps listed alphabetically.

Save surface	Best at	Honest limit
Instapaper	Closest to Pocket's reading philosophy. Veteran iOS app. Free tier sufficient for most. Summaries on Premium.	No MCP. No AI triage. Reading is the primary verb.
Matter	Typography-focused iOS / iPad / web reader. Real free tier; Premium adds HD TTS, AI Co-Reader, newsletter parsing via dedicated email.	No MCP. AI gated behind Premium.
Raindrop.io	Genuinely unlimited free tier for bookmarks/collections/tags. Native Pocket HTML import. Pro adds AI Assistant + MCP.	Reading mode is secondary; not optimized for deep sessions.
Readwise Reader	Strongest PKM integration (Obsidian / Notion / Logseq). Ghostreader inline AI. Spaced-repetition review.	No free plan — 30-day trial then $9.99/mo annual or $12.99 monthly. Heavy for people who don't highlight.
Burn 451	24-hour Flame timer + Spark/Vault forces a daily decision on every save. MCP exposes the decision loop to Claude / Cursor. Free tier today.	iOS-first; Android on roadmap. Pocket import not yet shipped (planned with V3). Wrong tool if you want a 10k-link archive.

For browser bookmarks: I'm not listing them as a real option because in my experience, they're where intentions go to die. Use them for navigation (your bank, your tax site, the doc you reference daily) — not for "I'll read this later."

Recovery: What If You Don't Have a Pocket Export?

I'll be direct: if you missed the November 12, 2025 export window, your saved Pocket articles are not coming back from Mozilla. The API is disabled. The account data was queued for permanent deletion. No paid recovery service can pull from servers that no longer respond.

That said, here's the realistic recovery matrix — what you can still salvage and from where:

Source	What you might recover	Realistic odds
Firefox sync	If you used Firefox with Pocket integration enabled, some saves may have synced to your Firefox account's bookmark store.	Medium. Worth 5 minutes to check Firefox bookmarks.
IFTTT / Zapier	If you ever set up an automation that mirrored Pocket items to Notion, Airtable, Google Sheets, or another app, that destination still has the URLs.	High if you used automations. Zero if you didn't.
Pocket digest emails	Pocket sent weekly digest emails with linked articles. Search your inbox for `from:getpocket.com`.	Recovers maybe 20% of your library — only the ones the algorithm surfaced.
Browser history	If you read what you saved (or even clicked through to save), the URL is in your browser history. Filter by date range.	Limited window (most browsers cap at 90 days). Mixed with everything else you visited.
Wayback Machine	For specific articles you remember, the Internet Archive may have a cached copy. Useful if the original URL is also dead.	Article-by-article. Not bulk-recoverable.
Anything else from Mozilla	No.	The official Mozilla support page (`support.mozilla.org/en-US/kb/future-of-pocket`) is explicit: data is queued for permanent deletion.

Here's the honest version: most people who missed the export window will recover maybe 10–30% of their library across these sources, mostly from email digests and Firefox sync. Treat the rest as gone and move on. (Counter-intuitive but true: every Pocket refugee I've talked to said losing the pile actually felt like relief once they got past the first week.)

If You Have a Pocket Export: Archive vs Active Reading Queue

The single most useful rule I learned during my own migration: don't put your Pocket export into your new daily reading app.

Here's why. Pocket conflated two very different things — it was both your reading queue (stuff you hoped to read this week) and your archive (stuff you wanted to keep forever, or just couldn't bring yourself to delete). Most people's exports are 80% archive and 20% queue, but those two need different tools.

A Real Daily Save Workflow (Post-Pocket)

Here's the four-step loop I actually run after Pocket. Adapt the tool names — the structure is what matters.

Capture (any time, low effort).iOS share sheet, Chrome extension, or paste a URL into your active-queue tool. Don't think — capture is for later.
Triage daily (5–10 min).Open the queue once a day with coffee or on the commute. Read it, vault it for permanent keeping, or let it expire. If your tool doesn't have an expiration mechanic, set a manual rule: anything older than 7 days gets deleted unread.
Read deep (one session, no app switching). What survives triage gets a real reading slot.
Surface later (optional).Whatever ended up in your archive becomes queryable via MCP (Burn / Raindrop Pro / Karakeep) or search. The point of archive is "findable later," not "readable now."

The trick is step 2. Pocket let everyone skip this — saves accumulated forever, no pressure. That was the feature people loved and also the reason their lists became unreadable. Whichever tool you pick post-Pocket, build step 2 into your week or it'll happen again.

How Not to Recreate the Pocket Pile in a New Tool

Five mistakes I've watched people (and myself) make in the post-Pocket year. Each one has a fix.

1.Treating the new tool as "Pocket but with extras." Different shape, different defaults. Don't carry over your old habit of saving 50 articles a week to read "eventually."
2.Importing the whole Pocket export into your active queue. Now you have 1,200 unread items on Day 1 in a brand new app. You will not feel like opening it. Send the export to archive instead.
3.Skipping daily triage.Without a regular decision pass, any queue grows. Tools with built-in expiration (Burn's 24h Flame) or surfacing (Readwise spaced repetition) do this for you; the rest require manual discipline.
4.Saving from three different surfaces. Pocket extension + Instapaper extension + browser bookmarks + email-to-myself = four queues, none of which you process. Pick one save destination.
5.Buying Premium without using its differentiator. Readwise Premium without highlighting, Matter Premium without listening, Burn Pro before hitting the free quotas — wait until your usage actually hits the wall. Free first, upgrade only when the workflow proves itself.

Where Burn 451 Fits (And Where It Doesn't)

I built Burn 451 specifically around the failure mode Pocket left behind — a queue that grew faster than you could read it. The 24-hour Flame timer forces a decision on every save: read it now, send it to Spark (a 30-day "maybe later" shelf), vault it for permanent keeping, or let it burn. There is no passive accumulation by design.

For the post-Pocket workflow specifically:

Save from the iOS share sheet, Chrome extension, or paste a URL.
Triage happens automatically because the timer creates pressure — you either act or it expires.
Vaulted itemsbecome queryable from Claude / Cursor via Burn's MCP server. "What did I save about X?" returns real saved items as context, not copy-paste.
Pocket import is on the V3 roadmap — until then, paste URLs or use the Chrome extension for new saves. For the bulk Pocket archive, Raindrop is the easier landing pad.

When Burn is the wrong tool for you:

You want a passive archive of 10,000 links. Burn's timer will annoy you. Use Raindrop or a local HTML folder.
You highlight constantly and live in Obsidian. Readwise Reader's PKM sync is far ahead of Burn here.
You're Android-primary. Burn ships iOS + Web + Chrome in 2026; Android is roadmap.
You hate opinionated software.Burn is opinionated by design. If "why is this telling me to decide today" bothers you, pick Raindrop free or Instapaper.

TL;DR — The Two-Tool Stack

Post-Pocket workflow in one paragraph

Send your Pocket HTML export (if you have one) to archive— Raindrop free, Wallabag self-host, or a local HTML folder. Don't open it daily.
Pick one active reading queue— Burn 451 if your pain is "save and never read," Matter if you want a calm reader, Readwise Reader if you highlight, Instapaper if you want Pocket-like simplicity.
Save new articles only to the active queue. Triage daily. Vault the keepers, let the rest expire.
Wait until the free tier of your active queue tool actually hits the wall before upgrading.

For the broader category (which read-later app to pick, AI/MCP differences, offline reading), see the read-it-later app guide. For Pocket-specific replacement options, see Pocket Alternative 2026.