← Return to blog

Pocket shut down: what to do with your saved links

Saved links moving from an old reading list into a smaller action-focused workflow

Short answer: Pocket shut down on July 8, 2025. Mozilla's current support page says data export was disabled on November 12, 2025 and Pocket user data entered permanent deletion. You cannot start a new Pocket export now. If you already downloaded the CSV, keep it as your source file. If you did not, rebuild from the links you can still find in browser history, bookmarks, messages, notes, and other apps.

Mozilla documents the current account, app, extension, API, and deletion status in Pocket has shut down: what you need to know. The original Mozilla shutdown announcement also explains why Pocket was phased out.

Start with the copy you still control

Start with the copy you still control, because it is the only one nobody can delete on you. According to Mozilla's announcement, Pocket stopped new downloads on 22 May 2025, shut down on 8 July 2025, and permanently deleted anything not exported by 8 October 2025.

Your next step depends on what survived:

What you have | What to do now

A Pocket export CSV | Keep an untouched backup, then work from a copy. Browser bookmarks or history | Recover only links that still matter to a current project. Links in notes, email, or messages | Move the useful links into one review list before choosing a new app. No surviving list | Do not try to recreate thousands of saves from memory. Start a smaller system from today.

Mozilla says a Pocket export contains the URLs of saved items rather than downloaded article text. It may also contain tags or highlights. That means an export is a map back to the original pages, not a permanent archive of their contents. Some links may now redirect, require a login, or no longer exist.

If you already have the Pocket CSV

If you already have the Pocket CSV, you are in the good case and the work is triage rather than recovery.

  • Save the original file somewhere you back up.
  • Open a duplicate in a spreadsheet.
  • Add one column called decision.
  • Mark each reviewed row act, reference, or discard.
  • Move only the act and genuinely useful reference links into your new system.
Do not bulk-import the entire file just to rebuild the same unread queue. Review the recent items and active-project links first. Stop when the remaining rows no longer support work you still plan to do.

If you missed the export window

Mozilla says it disabled Pocket exports and queued the remaining user data for deletion. No replacement app can recover that server-side Pocket library for you.

You may still find individual links in:

  • your browser history and bookmarks;
  • messages where you shared an article;
  • notes or documents where you pasted a URL;
  • newsletter archives and RSS readers;
  • another service that you connected to Pocket before shutdown.
Treat every recovered URL as untrusted until you open it. Confirm that the destination still matches what you intended to save before you keep it or turn it into a task.

Choose a replacement based on the job

Choose a replacement based on the job you actually do with saved links, not on which interface feels most familiar.

Pocket primarily served a read-it-later job. Your replacement should match what you actually want to do next.

Choose a reading library when you want offline reading, highlighting, full-text search, or a long-term reference collection. Check the provider's current import documentation, export options, pricing, and privacy terms before moving a large library.

Choose a browser bookmark system when you only need dependable folders and links.

Choose a task workflow when a saved item should produce a concrete next step. In that workflow, the URL remains context for the task instead of becoming another item in an endless reading queue.

Turn one recovered link into a task with Glean

Glean is not a Pocket archive and it does not claim to import a Pocket CSV.

Glean accepts saved tweets, YouTube videos, web links, and screenshots as captures. It turns a saved capture into a todo document with a reminder. It can propose a next action from that capture, and the action you accept becomes a plan.

That makes Glean useful for the small set of recovered links you intend to act on. For example:

  • save a tutorial and create a task to try one technique;
  • save a product page and create a task to compare one decision;
  • save a research link and create a task to verify one claim.
Open Glean, save one recovered link, review its proposed next action, and add a reminder to the todo document you keep.

Keep a separate reading or reference tool for material you only want to store. Use Glean when the saved source should help you decide or do something.

A smaller workflow that survives the next shutdown

A smaller workflow survives the next shutdown because it keeps less and exports cleanly.

Keep your source links portable. Prefer tools that let you export your own data, and periodically test the export instead of assuming it works. Keep important files outside any single app.

For each new save, record:

  • the original URL;
  • why you saved it;
  • the next action, if one exists;
  • where you stored any notes you created.
This structure matters more than rebuilding the exact Pocket interface. It gives you a readable source, a reason, and a next step even if you change apps again.

Everything you save becomes a task that gets done.

Capture the source, review the task, and get it done, yourself or with your agent.