What Google Reader's Shutdown Taught RSS Users
Published: September 23, 2026. Updated: October 2026 by Andrew Apell, who builds RSS Wrangler and previously built Flookup Data Wrangler
Quick Answer
Google announced Reader's shutdown in March 2013 and closed it that July. My takeaway is to own the subscription list: export it to OPML, prefer open formats and keep the reader close to you, so no announcement can strand years of curation.
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. Many discovered that their carefully built subscription lists lived entirely inside a product about to disappear. The scramble that followed taught me 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 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. 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.
One correction to the story that is usually told. The figure that circulates about how large Reader was, sometimes described as a large share of all feed consumption on the web, comes from estimates rather than published measurement, and Google never released one. I treat the number as an indication of scale, not as a statistic.
The Dates, and Why the Gap Was Costly
The timeline is the part people misremember. The gap between two of these dates is where the damage happened.
- March 2013. The shutdown was announced, with July given as the date. Readers had roughly three and a half months, which sounds generous until you notice what followed.
- July 2013. Reader stopped working. Feed lists became readable through a one-off export, which is the point at which everyone discovered whether they had a copy.
- December 2013. The API that third-party apps used was switched off. That is what broke those apps, rather than the July shutdown itself.
Subscriptions were recoverable. Everything else was not. Starred items, notes, shared items, saved searches and years of read-state history were tied to the product rather than the format, and they went with it. That asymmetry is the whole lesson: the list is portable, the curation is not.
Why the Platform, Not the Format, Was the Problem
Reader died and 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. What died was a set of subscriptions stored in one company’s database, plus a set of apps built on one company’s API.
I hold on to that distinction, because it separates two kinds of dependency. Depending on an open format means depending on a specification. Depending on a reader means depending on a balance sheet, a product roadmap and a deprecation policy. Both look identical right up until the announcement.
Lesson One: Own Your Subscription List
A feed list built over years is personal infrastructure. 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. I export mine regularly and keep a copy somewhere I control, so no shutdown announcement can strand me 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. Open formats outlive every product built on them. When choosing tools, I favour the ones whose data I can take with me 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. 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.
It Has Happened Again Since, and Will Again
Reader is the famous example, not the only one. Read-later services carry the same risk in a different category. Pocket was shut down in 2025 after its owner changed direction, and readers of that genre learned the same lesson about data held on someone else’s servers. Smaller feed services have closed for ordinary reasons, funding or attention. In each case, the people who had exported had an afternoon to recover, while the people who had not had to rebuild.
The pattern to watch is not company size. It is whether the service tells you how to get your data out, and whether that method is a documented format rather than a support request. A service with a one-click open export is telling you it expects to be replaced eventually.
A Five Minute Audit You Can Run Today
- Export from your current reader. Do this before anything else, because if the audit goes wrong you will still have the list.
- Check the format of the export. A documented file you can parse yourself is worth far more than a zip you cannot open without the product.
- Store it somewhere that is not the service. A cloud drive folder or your documents folder both qualify. A note inside the service does not.
- List what you would lose that is not a subscription. Starred items, notes and read states. Then decide whether any of that needs a separate export now.
- Date every backup. The failure people regret is overwriting the only good copy with a later empty one.
Our backup guide covers what each format carries and what it leaves out, including the export format RSS Wrangler itself uses.
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 a file regularly and keep a copy somewhere you control. Any reader worth using offers a one-click export. The format matters more than the frequency: a documented file you can parse yourself will still work in ten years, while a proprietary download may not.
What was actually lost in 2013?
Subscriptions were recoverable through a one-off export. Starred items, notes, shared items and read-state history were tied to the product rather than the format, so they were not. That asymmetry is the lesson: the list is portable and the curation is not.
How many people used Google Reader?
No reliable figure was ever published. The large numbers that circulate are estimates rather than measurement, so treat them as an indication of scale, not as a statistic.
Does using a local browser reader carry the same risk?
Not the same risk. A reader that stores your subscriptions in the browser has no server-side account to be shut down, no list to be lost with a company and nothing to export for its own sake. The trade is that your list lives on that device and its profile, so it still deserves an export to somewhere you control.
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 strand you again.
Related Articles
Keep Your Feeds Where Shutdowns Cannot Reach
RSS Wrangler keeps subscriptions in your browser. No account, no cloud and offline support.
Add to Chrome