RSS — the family of XML-based content syndication standards that briefly seemed to be the future of how people would read the web — is one of the more interesting threads in internet history. The standard was foundational to a particular vision of the open web, came close to becoming the default content distribution mechanism, was undermined by commercial forces, and has persisted in a quieter form into 2026 in ways that the headline coverage rarely acknowledges. Worth a retrospective on what RSS did, what happened to it, and where it sits now.

The origins.

The RSS standard emerged from several distinct development threads in the late 1990s. The Resource Description Framework Site Summary (RDF Site Summary) work at Netscape produced an early version. The Rich Site Summary work that followed and the eventual Really Simple Syndication branding refined the standard into a more usable form. The Atom standard emerged later as a related but technically distinct alternative.

The fundamental concept was elegant. A website would publish a structured XML feed listing the recent content — typically the latest blog posts, news articles, or updates. A reader application could subscribe to multiple feeds and aggregate the content into a single view. The user would consume content from many sources in one place without visiting each site individually.

The early adoption.

RSS adoption grew through the early 2000s as the blogosphere expanded and as bloggers and news sites recognised the value of distributing their content in a syndicated form. The major blog platforms — Blogger, Movable Type, eventually WordPress — built RSS feed generation into their default output. The major news sites added RSS feeds to their websites. The standard became a de facto element of any serious content website.

The reader applications proliferated. Bloglines became one of the early popular web-based RSS readers. NetNewsWire was the iconic Mac desktop reader. NewsGator on Windows. The smaller specialist readers covered every operating system and platform. The user could pick a reader that fit their workflow.

The Google Reader era.

Google Reader, launched in October 2005, became the dominant RSS reader through the late 2000s. The Google Reader experience was clean, fast, and reliable. The integration with the broader Google account ecosystem made adoption easy for the user already using Gmail and other Google services. The shared item and social features added a layer of social discovery on top of the syndicated content.

Google Reader at its peak had tens of millions of active users. The product became the default RSS reader for a generation of internet users. The dependency on Google Reader by the broader RSS ecosystem was substantial — many smaller reader applications synchronised through Google Reader’s API.

The decline begins.

The decline of RSS as a mainstream content consumption mechanism started in the early 2010s. The reasons were several.

The rise of social media as a content discovery mechanism. Facebook’s news feed, Twitter’s timeline, and the early social networking platforms began to substitute for the syndicated content stream that RSS provided. The user got a content feed from social media in a different but related form.

The mobile transition. The early smartphone era favoured native apps over web-based syndication. The dedicated app for a news source provided a better experience than the syndicated content from the same source consumed through a third-party reader.

The commercial pressure on publishers. The advertising revenue model favoured driving users to the publisher’s website where the publisher could serve ads and capture data. The syndicated content consumed in a third-party reader bypassed the publisher’s revenue mechanism. Some publishers began to truncate their feeds to summaries only, removing the value of the syndicated experience.

The 2013 Google Reader shutdown.

The 2013 announcement that Google Reader would be discontinued was a defining moment for the broader RSS ecosystem. The reasons given by Google centred on declining usage and competing priorities. The decision triggered a substantial user migration to alternative readers and a substantial public discussion about the implications for the open web.

The user response was mixed. Some users migrated to alternative readers — Feedly was the most successful inheritor of the Google Reader user base. Some users abandoned RSS as a content consumption mechanism entirely and shifted to social media or to direct app consumption. Some users grumbled and reduced their reading volume.

The longer-term effect was structural. The disappearance of Google Reader removed the integration point that many smaller reader applications relied on. The ecosystem fragmented. The market for new RSS reader applications became smaller and more niche.

The quiet persistence.

What is interesting about RSS in 2026 is that the standard has not died. The protocol persists. The feeds continue to be generated by most blogging platforms and many news sites. The reader applications continue to exist and to be maintained.

The user base for RSS reading has stabilised at a smaller but committed segment. The users who use RSS in 2026 are typically more deeply engaged with content than the average social media user. They tend to be technical workers, journalists, researchers, and serious readers of niche content. The user pattern is more “I read 50 specific sources daily” than the mass-market “I scroll through whatever the algorithm shows me”.

The reader applications that have survived have done so by focusing on this committed user base. Feedly is the largest. NetNewsWire was open-sourced and continues to develop. Reeder remains a popular paid option on Apple platforms. A range of smaller and open-source readers continue to be actively developed.

The use cases in 2026.

RSS continues to be useful in several specific ways in 2026.

The serious reader of niche content. The person following 50–100 specific blogs, journalists, or sources finds RSS a more efficient mechanism than checking 50 individual websites. The reader application gives them a unified inbox of content from sources they have explicitly chosen.

The podcast subscription mechanism. Podcasting was built on RSS and remains so. The podcast app on your phone consumes RSS feeds even if the user never sees the underlying mechanism. The continued growth of podcasting through the 2020s has kept RSS as a meaningful infrastructure layer.

The newsletter ingestion. Some readers use RSS to ingest the email newsletters they subscribe to via services like Kill the Newsletter that convert email subscriptions into RSS feeds. The pattern allows reading newsletter content in the reader interface rather than cluttering the email inbox.

The technical and research content. The blogs and content sites read by software developers, researchers, and academics often include RSS as a primary distribution mechanism. The community continues to operate on RSS at a level that is invisible to the broader user base.

The substitute mechanisms.

The major substitute mechanisms for RSS — social media feeds, algorithmic content feeds, email newsletters, dedicated apps — all have meaningful limitations relative to RSS.

Social media feeds are algorithmically curated and the user does not control what appears.

Email newsletters provide some of the same benefit but accumulate in the inbox and create the email-management problem.

Algorithmic content feeds — Apple News, Google News, Flipboard — provide a curated experience but the user does not have direct control over the source list.

Dedicated apps provide a good experience for a single source but the user has to switch apps to consume content from multiple sources.

The RSS approach — user-controlled source list, no algorithmic intermediation, unified consumption interface — remains uniquely suited to certain reading patterns even in 2026.

The legacy and outlook.

RSS in 2026 is a foundational technology that did not become the mass-market consumption mechanism it might have been but did not disappear either. The standard supports podcasting, supports a committed reader user base, and supports a meaningful niche ecosystem of applications and content. The future is more of the same — quiet persistence rather than dramatic resurgence or decline.

The broader lesson of the RSS story is about the fragility of open-web standards in a commercially-pressured ecosystem. The open syndication mechanism that was elegantly designed and broadly adopted lost ground to commercially-controlled alternatives. The standard persisted in the niches where the user base valued open access enough to maintain it. The pattern has been repeated in other parts of the open-web infrastructure and is worth remembering when discussing the resilience of any specific open standard.