RSS was declared dead enough times that the obituaries became a genre. In 2005 RSS was supposed to be killed by web aggregators. In 2010 by Twitter. In 2013 when Google Reader shut down by social platforms generally. In 2018 by algorithm-driven content discovery. The premise of each obituary was that something newer and more convenient would replace the old standard.

In 2026, RSS is still here. The user base is smaller than it was at peak. The mainstream consumer awareness is low. The ecosystem of clients, publishers, and aggregators is smaller than it once was. But the standard is operational, the content publishers are still producing feeds, and a substantial group of users still consumes their information through RSS.

The story of why is worth telling because it has implications beyond RSS itself.

The origin

RSS originated in 1999 as RDF Site Summary, a format developed at Netscape for syndicating news content. Multiple parallel developments through the early 2000s produced the various versions of RSS (0.91, 0.92, 1.0, 2.0) and the eventual Atom format that competed with and complemented RSS.

The standard was simple. A publisher created an XML feed that listed recent content with titles, descriptions, links, and timestamps. A reader application polled the feed and presented new items to the user. The information flowed without the user having to visit each publisher’s website directly.

The simplicity was the strength. RSS solved one specific problem — getting notified about new content from sources you cared about — and solved it cleanly without requiring sophisticated infrastructure on either the publisher or the reader side.

The peak years

The mid-2000s were the peak of RSS adoption. Several specific factors drove the growth.

The blog era was at its height. Bloggers wanted ways to track multiple other bloggers’ output without manually visiting each blog. RSS solved this elegantly.

News organisations realised that syndication was strategically important. Most major news sites adopted RSS feeds and the volume of feed-published content grew dramatically.

Reader applications proliferated. Bloglines, NetNewsWire, FeedDemon, and dozens of other readers competed for users. The space was active and innovative.

Browser integration emerged. Internet Explorer 7 added RSS support directly. Firefox had Live Bookmarks. The standard became visible to mainstream users.

The user numbers grew through the late 2000s. Not to the scale of social media platforms, but to a substantial active user base across the engaged web population.

Google Reader and the shift

Google Reader launched in 2005 and rapidly became the dominant RSS client. The cloud-based model was a meaningful improvement over desktop readers. The interface was clean. The performance was reliable. The ecosystem of mobile clients and integration tools that built around Google Reader’s API extended its reach further.

By the early 2010s, Google Reader was effectively the RSS infrastructure for a generation of users. Other readers existed but Google Reader was the centre of gravity.

Google’s decision to shut down Reader in 2013 was the most disruptive event in RSS history. The user base that had standardised on Google Reader had to migrate or stop using RSS. Many migrated. Many stopped.

The shutdown also damaged the perception of RSS itself. The narrative became that “even Google killed RSS, so the standard must be dying.” The actual situation was that Google had made a corporate decision about a non-strategic product, but the perception was that the standard had been declared obsolete by an authority.

The recovery

The recovery from the Google Reader shutdown happened differently than the obituary writers expected.

A new generation of cloud-based readers emerged. Feedly, Inoreader, Newsblur, and others stepped into the gap left by Google Reader. The user base distributed across these competitors rather than consolidating on one again.

The desktop reader category continued. NetNewsWire was open-sourced and became a meaningful Mac and iOS client. Other desktop and mobile clients persisted.

Self-hosted readers grew. Tiny Tiny RSS, FreshRSS, and other self-hosted options found a user base that valued data ownership and resilience over convenience.

The publisher side held up better than predicted. Most publishers that had RSS feeds in 2013 still had them in 2018, 2022, and 2026. The cost of maintaining a feed is low. The audience that uses feeds is small but consistent. There’s no compelling reason for most publishers to remove the feed.

Why RSS survived

A few specific factors explain why RSS survived when many of its contemporaries didn’t.

The standard is open and not controlled by any single entity. There’s no corporate gatekeeper that can shut down the protocol. Publishers and readers can continue regardless of any specific company’s decisions.

The implementation requirements are minimal. A working RSS feed can be generated with a few lines of code. A working RSS reader can be written by an individual developer in a weekend. The barrier to entry is essentially zero.

The user need RSS addresses persists. People still want to follow specific sources. People still want chronological access to information rather than algorithmic curation. People still value the absence of advertising and recommendation systems. RSS continues to serve these needs better than the alternatives.

The audience that values these properties is small but committed. The user base that uses RSS in 2026 is not casual. They’ve made deliberate choices about how they want to consume information. They’re unlikely to abandon RSS for the latest social platform.

Where RSS is in 2026

The 2026 picture for RSS is one of stable but smaller-scale operation.

The major news publishers still maintain feeds. The blogs that survived from earlier eras still publish feeds. New independent publishers — Substack newsletters, individual writer sites, niche professional publications — frequently publish RSS feeds, often as a nod to their audience’s preferences rather than as a primary distribution channel.

The reader market is stable. Feedly remains the dominant cloud reader. Inoreader has a committed user base. The self-hosted options have a smaller but devoted following. Mobile RSS clients exist and work well.

The integration with other tools has improved. Many newer reading and note-taking applications support RSS as an input. Webhooks and IFTTT-style automation tools work with RSS feeds. The ecosystem is less visible but more sophisticated than it was at peak.

The mainstream visibility is low. Most consumer software doesn’t surface RSS as an option. Browsers don’t promote it. Operating systems don’t integrate it. The user has to deliberately seek out RSS to use it.

What RSS does well

The properties that have made RSS endure are clearer in retrospect.

Chronological order without algorithmic curation. The user sees recent content from chosen sources in time order. There’s no ranking, no “what we think you’ll like,” no advertising injection. The user controls what they see and when.

No tracking. The publisher knows the feed has been polled, but doesn’t know which items the user actually read, in what order, or for how long. The privacy model is much better than algorithmically driven feeds.

Resilience to platform decisions. The user’s reading list is independent of any platform. If the reader application changes pricing or shuts down, the OPML export and re-import to another reader is a few minutes of work. There’s no platform lock-in.

Source-level control. The user explicitly chooses each source they follow. There’s no algorithm pushing similar content. The signal-to-noise ratio is determined by the user’s curation, not by an opaque ranking system.

These properties are valuable to a specific kind of information consumer. The fact that the consumer base is smaller than the social platform user base doesn’t make these properties less valuable to the people who care about them.

Where this goes

RSS is unlikely to have a dramatic resurgence in mainstream adoption. The factors that have kept it niche are unlikely to reverse. The audience is stable but small.

The continued operation of RSS for the people who use it is, however, reasonably secure. The infrastructure is decentralised. The standards are open. The reader ecosystem is diverse enough that no single failure can break it. The publisher base is stable.

For 2026 and beyond, RSS will probably continue to be the way a small but committed set of users consumes information. It outlasted Google Reader. It will probably outlast many of the platforms that supposedly replaced it.

The lesson from RSS history is one about the durability of open standards that solve specific problems well. The flashier replacement technologies have flashier marketing and bigger user bases. RSS just keeps working. Sometimes that’s enough.