A Graveyard of Saved Links: Delicious, Google Reader, Pocket, Omnivore

Every few years, a service that millions of people trusted with their reading list posts a short, polite blog entry and sets a date. Then the date arrives and a decade of saved links stops existing.

This has happened enough times now that it's not bad luck — it's the normal life cycle of a bookmarking service. It's worth walking the graveyard, because the headstones have a pattern on them, and the pattern tells you exactly how to save things so the next one doesn't take anything from you.

Delicious (2003–2017): the one that invented this

Delicious — originally del.icio.us — launched in September 2003 and basically invented social bookmarking and tagging as we know it. At its 2008 peak it had over five million users and a reported 180 million bookmarked URLs. It was the web's shared memory.

Then it went through four owners in twelve years: Yahoo bought it in December 2005, a leaked Yahoo slide marked it for "sunset" in December 2010, YouTube's co-founders bought it via AVOS in April 2011, it changed hands twice more, and in June 2017 Pinboard acquired it and turned the lights off.

Nobody killed Delicious on purpose. It was passed around until there was nothing left, which is a slower and more common death than a shutdown announcement.

Google Reader (2005–2013): size is not safety

Google announced Reader's retirement on March 13, 2013 and closed it on July 1 — about three and a half months. To Google's credit, Takeout let you export your subscriptions, and a lot of people did.

The lesson people took away at the time was "don't depend on a free product from a company that doesn't charge you for it." That's part of it. The bigger lesson is that Reader was owned by one of the largest companies on earth and still had a fixed end date. Scale isn't a promise. Neither is popularity — the shutdown petition got tens of thousands of signatures and changed nothing.

Google made the same call again in September 2021, when the separate Google Bookmarks service — running since 2005 — was quietly discontinued.

Pocket (2007–2025): the long goodbye that still ended in deletion

Pocket started life as Read It Later, became the default read-later app for a generation, and was bought by Mozilla in 2017. On May 22, 2025, Mozilla announced it was ending. The service stopped working on July 8, 2025 and flipped to export-only. The export deadline was extended twice, finally landing on November 12, 2025 — after which exports and the API were switched off and the accounts were queued for deletion.

Pocket handled its ending about as well as a shutdown can be handled: months of notice, repeated extensions, refunds for Premium subscribers. And it still ended with a large number of people permanently losing their libraries, because the part that requires you to act at a specific time is the part that fails.

We wrote a full guide for people still sorting this out: Pocket shut down — where to move your saves.

Omnivore (2023–2024): open source is not a guarantee

Omnivore was the one technical readers chose specifically to avoid all of the above. Open-source, highlight-first, real API, clean export — everything you'd put on a checklist to not get burned.

ElevenLabs acquired the team on November 1, 2024 and the service shut down on November 15. Two weeks. Saved articles, highlights and notes were deleted after that window closed. The code being open didn't help, because what people actually needed was the hosted service and the data inside it.

More on the Omnivore shutdown and what to look for in a replacement.

The pattern on the headstones

Line those four up and the same three things are true every time:

1. The warning window keeps shrinking. Google Reader gave three and a half months. Omnivore gave two weeks. You cannot count on having time to research a replacement after the announcement.

2. Nothing protects you structurally. Big company, small company, paid, free, open-source, beloved — every category is represented in the graveyard. The only thing that's ever protected anyone is having their own copy already.

3. The export is a URL list, not your library. This is the part almost everyone underestimates. Say you exported Pocket in time. You have an HTML file of links — and a meaningful share of the pages those links point to are already 404s, parked domains, or paywalls, because links rot on their own whether or not the service hosting them survives. A shutdown is one loss stacked on top of another one that's been happening quietly the whole time.

The routine that actually works

Not "be more careful." A routine, in rough order of how much it buys you:

Save the content, not just the link. If what you keep is only a URL, you're betting that a stranger will keep paying to host something forever. Use something that stores the readable text of the page at save time.

Export on a calendar, not on an announcement. Put a recurring quarterly reminder in your calendar to export whatever tool you use. The people who lost Pocket libraries weren't careless — they were waiting for a deadline they eventually stopped seeing in their inbox.

Restore your export once. An export you have never successfully imported somewhere else is a backup you don't have. Rich proprietary formats are the trap here: a ZIP full of a service's own schema can be technically "an export" and still be a nightmare to actually use somewhere else. Test it while the service is still alive and you can re-export.

Prefer open formats and a real API. Standard bookmark HTML, JSON, Markdown — boring formats every tool can read. An API means you can automate the backup instead of remembering it.

Where Cowpin fits — and the honest caveat

We built Cowpin after losing our own libraries to this graveyard, so the design assumptions are the ones above:

• Auto-archive on save. Cowpin captures the readable content of pages you save, so a dead original doesn't erase what you kept it for — and everything stays full-text searchable.
• One-click import of standard bookmark exports, including Pinboard and Pocket files, with tags, privacy settings and read-later state preserved.
• Export any time, in Pinboard-compatible JSON, Netscape HTML, and Markdown for Obsidian or Notion. The door is unlocked in both directions, permanently.
• A Pinboard-compatible API, so you can script your own backups rather than trusting anyone's goodwill — including ours.

And the honest caveat, because a post about shutdowns shouldn't end with "trust us forever": Cowpin is young. The correct response to everything above is not to find a service you believe is immortal — there isn't one. It's to keep the content rather than just the links, and to only use tools that make leaving trivial. We'd rather earn the second visit than lock the first one in.

Cowpin is free while we're finding our first users — every feature, no limits. Got an export sitting in a folder from a service that died? Bring it over.