What Google Reader's Shutdown Taught RSS Users

Published: September 23, 2026 by Andrew Apell

In March 2013, Google announced that Google Reader would shut down that July. For millions of people it was the only RSS reader they had ever used, and many discovered that their carefully built subscription lists lived entirely inside a product that was about to disappear. The scramble that followed taught RSS users three lessons that still apply to every reader choice today.

What actually happened

Google Reader launched in 2005 and became the default RSS reader almost by accident: it was fast, free and already inside your Google account. By the early 2010s it reportedly served a large share of all feed reading on the web, and a whole ecosystem of third-party apps synced through it rather than building their own infrastructure. When Google retired it, citing declining usage as attention moved to social products, those apps broke overnight and ordinary readers had weeks to rescue years of curation. Alternatives like Feedly, Inoreader, NewsBlur and The Old Reader absorbed the exodus, but only the users who exported in time arrived with their lists intact.

Lesson one: own your subscription list

A feed list built over years is personal infrastructure, and anything that lives only inside someone else's product is borrowed. The survivors of 2013 were the people with an OPML export: one file holding every subscription, importable into any reader in minutes. Export yours regularly and keep a copy somewhere you control, so no shutdown announcement can strand you again. Our guide to finding an RSS feed for any website helps you rebuild anything that goes missing.

Lesson two: prefer open formats over platforms

Reader died but RSS did not, because no company owned the format. Every podcast app still subscribes to feeds under the hood, and the same XML from 2005 parses identically today. Platforms get acquired, degraded or shut down, while open formats outlive every product built on them. When choosing tools, favour the ones whose data you can take with you over the ones that make leaving hard.

Lesson three: keep the reader as close as possible

Every layer between you and your feeds is a layer that can disappear. A cloud reader holds your list on its servers, while a local reader like a browser extension keeps subscriptions on your device, works offline and has nothing to shut down remotely. That is the design RSS Wrangler follows: your feeds live in Chrome with you, not on a server waiting for a deprecation notice.

Reader died but RSS did not, because no company owned the format.

FAQ

Why did Google Reader shut down?

Google retired Reader in July 2013, saying usage had declined as attention moved to social products. The shutdown stranded millions of subscribers at once.

Could a shutdown like that happen again?

Any cloud reader can shut down, which is exactly the lesson. Readers that keep subscriptions on your device and export to OPML leave you with somewhere to go.

How do I protect my feed list today?

Export your subscriptions to an OPML file regularly and keep a copy somewhere you control. Any reader worth using offers one-click OPML export.

Summary

Google Reader's shutdown was painful but clarifying: never build years of curation inside a product you do not control. Own the list, prefer open formats and keep the reader local, and no announcement will ever strand you again.

Keep your feeds where shutdowns cannot reach

RSS Wrangler keeps subscriptions in your browser, with no account, no cloud and offline support.

Add to Chrome