There is a good chance you used RSS this morning without knowing it. Perhaps an app on your phone checked for new episodes of a podcast you follow. Perhaps a newsletter delivery system confirmed your subscription. Perhaps a content automation tool published a post to your blog. In each case, a small XML file a web feed did the work, unchanged in its fundamental design since engineers at Netscape first proposed it in March 1999.
RSS has been declared dead so many times that obituary writers have grown cautious. And yet the format persists. It persists not as a relic kept on life support, but as active infrastructure underlying the entire podcast ecosystem and an increasingly attractive option for independent publishers seeking escape routes from algorithmic platforms.
A Widget Named RSS
The format that would become RSS was born inside one of the internet's most storied companies as a humble portal feature. Netscape Communications released RSS 0.90 on March 15, 1999, designed to populate personalized content channels on the experimental My Netscape Network portal. Any website owner who used Netscape's nascent XML-adjacent tags to create a feed of their site's updates could have that feed added to a list of 600 or so channels available to portal users.
It was a genuinely early example of a standardized way for a machine to read a site's latest updates, years before "web feed" was a common concept for most internet users, according to PostRSS's comprehensive history of the format. The ambition was modest portal personalization but the underlying insight was profound: websites could publish updates in a structured format that other software could consume automatically.
Netscape would largely abandon RSS to the broader web community, and that community ran with it. Online publishers embraced RSS as an easy way to push their latest content to readers. The format was beautifully simple: any website could publish a feed, and any user could subscribe to it with a reader. No algorithms. No gatekeepers.
The Format Wars Nobody Remembers
What followed RSS 0.90 was a period of competing, incompatible versions that would confuse developers for years. Different groups developed RSS 0.91, RSS 1.0 (built on RDF, a different underlying data model), and later RSS 2.0, each with different capabilities and philosophies.
Industry observers became absorbed in the rivalry between RSS and Atom, an entirely separate but conceptually similar feed format developed around 2003 as a cleaner, more consistently specified alternative to RSS's fractured version history. But this attention obscured a more consequential battle that had already concluded.
"Not many people talk about how or why RSS won the content syndication war because few people are aware that a war ever took place. Everyone was so fixated on the drama over RSS's competing standards that they barely registered the rise and fall of the Information and Content Exchange (ICE) specification, which had been created, funded, and eventually abandoned by Microsoft, Adobe, CNET, and other household names."
That observation, from Ryan Farley's account of RSS alongside ICE, points to a corporate syndication war that RSS won decisively against a technologically superior but commercially compromised rival.
Microsoft and its partners had created ICE the Information and Content Exchange standard nearly a year before RSS emerged. The March 1998 proposal for ICE standardized how data posted to one website could be automatically published on other websites, and it was unapologetically commercial from the start. Unlike RSS's open, community-driven development, ICE promised to expand publishers' electronic sales by making it easier to license the same material to multiple sources.
The parallel to VHS and Betamax is instructive. Betamax had superior resolution and fidelity. VHS was cheaper, offered longer recordings, and was the more open format. Adult film studios did not choose VHS because of any grand theory about openness they chose it because it worked for their business. The same logic applied to syndication: bloggers and independent publishers chose RSS not because it was technically superior in every way, but because it was accessible and free.
"The real story is that while Betamax tapes had better resolution and fidelity, VHS was cheaper, offered longer recordings, and, most importantly, was the more open format," Farley writes. ICE was the Betamax to RSS's VHS more advanced in some respects, more expensive, less open, and unable to counter the overwhelming number of bloggers who flooded the market with DIY-friendly RSS feeds.
The Feed Reader Era and Its Disruption
The mid-2000s to early 2010s marked RSS's most visible mainstream moment. Dedicated feed reader products both desktop and web-based became a genuinely popular way for internet users to follow multiple sites without visiting each one manually. This was the RSS use case most people who remember the format associate with it: a personal reading tool, aggregating updates from favorite blogs and news sites into a single interface.
The peak and the nadir came with Google Reader. Google's discontinuation of Google Reader in 2013 is widely remembered as the moment RSS's mainstream visibility declined sharply. Reader had been one of the most widely used feed reader products, and its shutdown pushed many casual users toward social media as their primary source of updates instead of an RSS reader.
But this characterization misses something important. What actually happened was narrower: one major consumer product shut down, not the underlying format losing technical relevance. The distinction matters. As Sydney Butler wrote for How-To Geek, "This is often mischaracterized as 'RSS dying,' when what actually happened was narrower: one major consumer product shutting down, not the underlying format losing technical relevance."
The Podcasting Secret
While consumer feed-reader visibility declined, RSS quietly became the actual technical backbone of podcasting. Every major podcast platform, including Apple Podcasts, distributes episodes via RSS feeds behind the scenes. This use case scaled enormously through the 2010s podcasting boom, entirely through the same RSS 2.0 format finalized back in 2003.
As Kevin R. Kuhl observed in a February 2026 analysis, "We 'killed' text RSS because it abstracted away the ads and revenue for blogs and news, but audio RSS was baked in due to bandwidth limits and how listening let creators bake ads into the media (unlike blogs)."
This is the great irony of RSS history. The format that became invisible to mainstream consumers of text content never stopped being essential for audio content. Podcasts could not exist without RSS the technology is baked into the distribution infrastructure of every podcasting platform.
The reasons are partly technical. Audio files are large, and streaming them directly from a website would be prohibitively expensive for most creators. RSS solved this elegantly: a podcast's feed contains metadata (title, description, episode notes) and a link to the audio file hosted elsewhere. When a podcast app checks the feed, it downloads only the small XML file and any new episode metadata, then streams or downloads the audio independently.
This separation of content and delivery proved remarkably durable. While social media platforms changed their algorithms, their revenue models, and their content policies with dizzying frequency, podcast RSS feeds continued working exactly as designed.
What This Means for PostsNews Readers
For readers researching publishing workflows, syndication strategies, and media research, the RSS story offers several practical lessons. The first is about format durability. RSS 2.0, finalized in 2003, achieved lasting, widespread adoption and has remained essentially unchanged since. Its simplicity a title, link, and description per item, with a handful of optional extensions meant there was very little to break or need updating over the following two decades, even as the web around it changed dramatically.
This is a rare achievement in technology. When you build a syndication system today, you might reasonably hope it will still function, unchanged, in 2043 not because the web will stand still, but because the problems RSS solves are so fundamental that the solutions remain stable.
The second lesson concerns openness. RSS won its wars not by being the most sophisticated option, but by being accessible. Any individual blogger could publish an RSS feed for free. No licensing fees. No corporate approval. No vendor lock-in. This openness made RSS the format of choice for the grassroots web, and that grassroots adoption made it impossible to displace.
The third lesson involves the value of invisible infrastructure. RSS is most powerful precisely when it is invisible. Podcast listeners never see an RSS feed; they simply receive new episodes automatically. Blog subscribers rarely think about the XML file their reader downloads. The format's success lies in its ability to disappear into the background while continuing to function.
The Pendulum Swings Back
There are signs that RSS may be emerging from invisibility for a new generation of publishers. The growth of newsletter platforms like Substack and Ghost has created renewed interest in syndication tools. Kuhl describes "Subscriber RSS" as a mechanism that lets readers support creators directly while still reading their work in the app of their choice.
"We're seeing a migration from walled gardens (Substack) to owned platforms (Ghost) driven by 'Subscriber RSS' that lets readers support creators directly while still reading their work in your app of choice," Kuhl writes. "404 Media has been particularly effective at demonstrating this approach."
This represents a philosophical return to RSS's original promise: one-to-many communication without algorithmic interference. The format that bloggers adopted in the early 2000s because it let readers subscribe without giving up control is now attracting publishers who have grown frustrated with platform dependency.
The attention economy that dominated the internet from roughly 2005 to 2025 may be giving way to something different. Kuhl sees "the pendulum swinging back to a utility-based economy from an attention-based economy," which he considers "a good thing, even if we're in a moment that's painful for the ad-revenue based paradigm of the 2005-2025 world."
In this environment, RSS's strengths become more valuable more than less. The format is inherently non-adjacent to attention extraction: there are no ads to display in an RSS reader, no engagement metrics to gamify, no algorithm to optimize for. What RSS delivers is simply the content the publisher chose to publish.
RSS and the Question of Preservation
One dimension of RSS that deserves more attention is its role in web preservation. The Internet Archive, known primarily for its Wayback Machine, has recognized the value of syndication formats for maintaining access to changing web content.
The Internet Archive's collection includes educational materials about RSS, reflecting the format's ongoing relevance to digital preservation efforts. Web feeds capture not just the content of a page at a moment in time, but the fact of when something was published and how it was categorized metadata that becomes increasingly valuable as the original pages disappear or change.
RSS feeds archived at a specific point in time can serve as a record of what a site was publishing, when, and under what categories. This temporal dimension gives RSS a preservation value that extends beyond its original syndication purpose.
A Format That Refuses to Leave
RSS has now been in continuous use for 27 years. Its latest official version, RSS 2.0.11, was released on March 30, 2009 17 years ago as of September 2026 and has not required a significant update since. The format's stability is arguably its greatest practical strength.
Compare this to the frenetic pace of change in other web technologies. Social media platforms have reshuffled their algorithms, their publication formats, and their monetization models dozens of times. Content management systems have evolved through generations of architectural redesigns. Only RSS has maintained the same core specification across more than two decades of internet evolution.
The brilliance of this stability lies in what it enables. Publishers can adopt RSS confident that their feeds will continue working indefinitely. Developers can build tools around RSS knowing the specification will not shift beneath them. Listeners can subscribe to podcasts knowing the subscription will survive platform changes, corporate acquisitions, and funding crises.
RSS is not a legacy format. It is not a technology that survived through inertia or corporate obligation. It remains the best solution to a problem that has not changed: how do you automatically notify interested parties when new content is available?
Looking Forward
What comes next for RSS is uncertain, but the trajectory is promising. The format's technical foundation is solid. Its role in podcasting is unchallenged. And the broader cultural moment with increasing skepticism toward platform dependency and algorithmic curation may create new demand for the open syndication model that RSS represents.
The question is not whether RSS will survive. It clearly will, embedded as it is in the infrastructure of an industry worth billions of dollars. The more interesting question is whether more publishers will recognize the value of owning their syndication infrastructure more than renting it from platforms.
For independent publishers, newsletter authors, podcasters, and anyone else creating regular content for the web, RSS offers something increasingly rare: a guarantee of direct access to your audience, independent of any platform's decisions about algorithms, fees, or content policies.
The format invented by three engineers at Netscape in 1999 has outlasted browsers, search engines, social networks, and countless prediction of its demise. Whatever happens next in media, RSS will likely be there, quietly doing its job, waiting to be discovered by the next generation of publishers who need a reliable way to reach their readers.
Where to Read Further
For readers wanting to explore RSS history and current developments in depth, several resources offer more detail than this overview can provide.
The Wikipedia entry on RSS provides a comprehensive technical overview of the format's evolution, variants, and current usage across 73 language editions.
Kevin R. Kuhl's analysis connects RSS's technical history to current debates about platform dependency and the future of web monetization, including the emerging role of AI in content delivery.
Ryan Farley's account of the largely forgotten battle between RSS and Microsoft's ICE specification offers a fascinating case study in how open, grassroots technologies can defeat corporate alternatives through adoption more than technical superiority.
PostRSS's detailed chronology traces the format from its Netscape origins through the Google Reader shutdown to modern automated syndication tools.
For those interested in the broader questions of web preservation that RSS touches, the Internet Archive's collection provides historical context for how syndication formats fit into digital preservation strategy.
Key Milestones in RSS History
| Year | Event | Significance |
|---|---|---|
| 1998 | Microsoft proposes ICE specification | Corporate syndication alternative to grassroots RSS |
| March 1999 | Netscape releases RSS 0.90 | First standardized web feed format deployed |
| 2003 | RSS 2.0 finalized | Stable version achieves lasting widespread adoption |
| 2003 | Atom format introduced | Cleaner alternative to RSS's fragmented versions |
| 2013 | Google Reader discontinued | Major consumer RSS product shuts down |
| 2010s | Podcasting boom | RSS becomes invisible backbone of audio distribution |
| 2026 | Renewed publisher interest | RSS as antidote to platform dependency |
Why RSS Still Matters
Twenty-seven years after its creation, RSS remains one of the few web technologies from the late 1990s still doing real, everyday work. It has survived format wars, corporate competition, platform disruption, and countless pronouncements of its death.
What makes RSS durable is not nostalgia for an earlier internet, nor corporate obligation to maintain legacy systems. What makes RSS durable is that it solved a fundamental problem automatic notification of new content and solved it in a way that requires no ongoing maintenance, no licensing fees, and no platform approval.
For publishers today, that durability offers something increasingly valuable: independence. When you publish an RSS feed, you own that connection to your readers. No algorithm can bury your content. No platform fee can cut into your margins. No policy change can delete your subscriber list.
The format that began as a portal widget for My Netscape Network has become something its creators never anticipated: the invisible infrastructure of the podcasting industry, the syndication standard for independent publishers, and the quiet archive of the web's ongoing conversation.