LabHub

Blog

RSS Readers & Content Syndication 2026 Deep Dive - Feedly AI · Inoreader · NetNewsWire · Reeder 5 · NewsBlur · FreshRSS · Miniflux · FeedBin · Readwise Reader · Matter · Omnivore (sunset) In-Depth Analysis

한국어English日本語

Introduction — May 2026, RSS Has Quietly Lived Through 13 Years

The day Google Reader shut down on July 1, 2013, plenty of writers declared RSS dead. Thirteen years later in May 2026, that verdict turned out to be half right. Algorithmic feeds and push notifications became the default, but a new generation of RSS readers armed with AI summarization and newsletter ingestion has actually grown its user base.

This piece is not a marketing matrix. It honestly answers "which RSS reader belongs where right now". We compare the AI-augmented camp (Feedly + Leo AI, Inoreader, Readwise Reader, Matter), native macOS/iOS clients (NetNewsWire, Reeder 5/6, Unread, Lire 5), web-first curation (NewsBlur, The Old Reader, FeedHQ, Bazqux), self-hosted open source (FreshRSS, Miniflux, tt-rss, Selfoss, Yarr, Commafeed), curated paid services (FeedBin, NewsBoat, Liferea), newsletter inboxes, and ActivityPub/Nostr decentralized readers — with real pricing, platforms, and API shapes.

RSS 2026 Big Picture — Five Distinct Branches

The macro view first. The May 2026 RSS reader market splits into five branches.

  1. AI-augmented SaaS: Feedly + Leo AI, Inoreader + Inoreader AI, Readwise Reader, Matter.
  2. Native macOS/iOS clients: NetNewsWire, Reeder 5/6, Unread, Lire 5, ReadKit.
  3. Web-first curation: NewsBlur, The Old Reader, FeedHQ, Bazqux Reader.
  4. Self-hosted open source: FreshRSS, Miniflux, Tiny Tiny RSS, Selfoss, Yarr, Commafeed.
  5. Hybrid read-later + RSS: Readwise Reader, Matter, Instapaper, Wallabag.

On top of that, Pocket (sunset announced July 2025), Omnivore (sunset November 2024) and Revue (sunset January 2023) — dead or dying products — reshape the landscape. Migration to surviving tools is the big 2025-2026 story.

After Google Reader — 13 Years of Market Realignment

The week after the July 2013 Google Reader shutdown was a gold rush. Feedly (founded 2008, Mozilla DevHQ alum) absorbed a million users in seven days, and The Old Reader (a 2012 effort to clone the Google Reader UI) got crushed by traffic in days.

Over the next thirteen years the survivors sorted out cleanly.

The fallen list is just as long. Bloglines (2010), Google Reader (2013), Digg Reader (2018), AOL Reader (2019), Microsoft Outlook RSS (gradual sunset), and Inoreader's sister app Stoop (newsletter inbox, sunset 2023).

Feedly + Leo AI — The Market Leader and GPT-Powered Triage

Feedly is the undisputed RSS reader market leader as of May 2026. Free for 100 feeds, Pro 9/mo,Pro+9/mo, Pro+ 14/mo, Enterprise on quote. Two core value props.

  1. Leo AI: introduced 2022. Users write natural-language rules ("only Apple news, exclude Vision Pro"), and Leo filters and summarizes every morning. Since 2024 it also calls GPT-4-class models.
  2. Boards & Notes: share curated articles with a team. Auto-push to Slack/Teams.

A Feedly OPML import looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<opml version="1.0">
  <head>
    <title>my-feeds</title>
  </head>
  <body>
    <outline text="Tech" title="Tech">
      <outline text="Hacker News" type="rss"
               xmlUrl="https://hnrss.org/frontpage"
               htmlUrl="https://news.ycombinator.com/" />
      <outline text="Anthropic" type="rss"
               xmlUrl="https://www.anthropic.com/news/rss.xml"
               htmlUrl="https://www.anthropic.com/news" />
    </outline>
  </body>
</opml>

Feedly Cloud API is effectively closed (Enterprise only), but OAuth v3 endpoints are exposed for partner integrations.

Inoreader — Feedly's Strongest Alternative

Inoreader was started by Bulgaria's Innologica in 2013. As of May 2026 the tiers are free (150 feeds), Pro 99/yr,Team99/yr, Team 250/yr. The strengths are clear.

Inoreader skews heavily Korean and Japanese in the user mix. Localized UI is solid, and annual pricing comes in below Feedly's Pro.

NetNewsWire — Open Source macOS/iOS Done Right

NetNewsWire is the macOS RSS reader Brent Simmons started in 2002. It changed hands to NewsGator and then Black Pixel before Simmons reacquired it in 2018 and open-sourced it under GPL-3.0. As of May 2026, macOS 6.1 and iOS 6.1 are the current versions.

The most-recommended option among ATP (Accidental Tech Podcast) listeners and Mac power users. One-liner: "free, better-built than most paid apps".

Reeder 5 vs Reeder 6 — Same Developer, Two Branches

Silvio Rizzi's Reeder is the aesthetic peak of macOS/iOS RSS readers. Reeder 5 shipped in 2020; Reeder 6 launched as a separate app in 2024, splitting the lineup.

ATP hosts Marco Arment and John Siracusa bring it up often. The choice between 5 and 6 boils down to "pure traditional RSS" vs "RSS + social in one timeline". Korean and Japanese users still skew toward Reeder 5.

Readwise Reader — Highlights + AI + RSS Integration Newcomer

Readwise Reader launched in beta 2022, GA 2023. Built by Readwise (a book-highlights-sync SaaS since 2017). Pricing is the combined Readwise+Reader subscription at 9.99/moor9.99/mo or 79.99/yr.

The proposition is "one place for all reading".

Highlights sync automatically to Anki, Notion, Obsidian, Logseq, Roam. Expensive if you just want RSS, but rational when consolidating "Pocket + RSS + Anki cards + Notion sync".

Matter — Beautiful Curation + AI Audio

Matter started in 2020 and launched publicly in 2022. Free + Premium $59.99/yr. Center of gravity is iOS/Android/Web; on macOS it runs as a PWA.

Matter is widely regarded as the most beautifully designed RSS + read-later hybrid. The downsides are no native macOS app and higher pricing than Pocket.

NewsBlur — Samuel Clay's 14-Year Solo Run

NewsBlur was started by Samuel Clay in 2009. Open source (MIT) and SaaS ($36/yr) at the same time. Two core value props.

NewsBlur can be self-hosted. git clone https://github.com/samuelclay/NewsBlur && docker compose -f docker-compose.yml up. On Kubernetes a deployment looks like this.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: newsblur-web
  namespace: rss
spec:
  replicas: 2
  selector:
    matchLabels:
      app: newsblur-web
  template:
    metadata:
      labels:
        app: newsblur-web
    spec:
      containers:
        - name: web
          image: newsblur/newsblur_web:latest
          env:
            - name: NEWSBLUR_HOSTNAME
              value: rss.example.com
            - name: DATABASE_URL
              value: postgres://newsblur:secret@pg/newsblur
          ports:
            - containerPort: 8000

Samuel Clay has been committing almost daily on GitHub for 14 years. One of the longest-running single-developer SaaS products in any category.

FeedBin — Backend-Friendly Paid SaaS

FeedBin is the paid RSS SaaS Ben Ubois started in 2013 to coincide with the Google Reader sunset. Single plan at 5/moor5/mo or 50/yr.

Clear identity.

FeedBin positions as "we will not ship clients; we will be the best backend". Reeder 5 + FeedBin is the standard setup among ATP listeners.

FreshRSS — The Self-Hosted PHP Standard

FreshRSS is a GPL-3.0 PHP/SQLite/PostgreSQL self-hosted RSS server. As of May 2026, v1.24.x is current. Runs well from a Raspberry Pi to a large server.

FreshRSS is the canonical answer to "I want one RSS backend on my server and any client on top". Raspberry Pi 4 + Docker + FreshRSS + Reeder 5 is the most common setup.

Miniflux — Go Single-Binary Minimalism

Miniflux is the Go-based RSS server Frederic Guillot started in 2014. Apache-2.0 license. v2.2.x as of May 2026.

The character is "minimalism".

A CLI example.

# Run via Docker
docker run -d --name miniflux \
  -p 8080:8080 \
  -e DATABASE_URL="postgres://miniflux:secret@db/miniflux?sslmode=disable" \
  -e RUN_MIGRATIONS=1 \
  -e CREATE_ADMIN=1 \
  -e ADMIN_USERNAME=admin \
  -e ADMIN_PASSWORD=changeme \
  miniflux/miniflux:latest

# Add a feed via REST API
curl -u admin:changeme -X POST http://localhost:8080/v1/feeds \
  -H 'Content-Type: application/json' \
  -d '{"feed_url": "https://www.anthropic.com/news/rss.xml", "category_id": 1}'

Users who prefer minimalism pick Miniflux over FreshRSS. The two effectively compete for the same slot with different philosophies.

Tiny Tiny RSS · Selfoss · Yarr · Commafeed — Other Self-Hosted Options

The two above own ~80% of the self-hosted market, but the alternatives survive.

For a single home machine, Yarr or Miniflux fits. For a serious server, FreshRSS or Miniflux are the common choices.

NewsBoat · Liferea · Lire 5 — Desktop Native Survivors

Web and mobile own most of the market, but native desktop clients are still alive.

A NewsBoat configuration fits in one text file.

# ~/.newsboat/urls
https://hnrss.org/frontpage  hacker-news
https://www.anthropic.com/news/rss.xml  anthropic
https://martinfowler.com/feed.atom  fowler

# ~/.newsboat/config
auto-reload yes
reload-time 60
browser firefox
notify-program "/usr/bin/notify-send"
bind-key j down
bind-key k up

NewsBoat is the near-standard for TUI users, and combined with system-tray notifications it can match Telegram bots.

Newsletter Inbox — The Fusion of RSS and Email

The biggest shift in the 2024-2026 RSS scene is newsletter ingestion. As Substack, Beehiiv, and Ghost have driven a newsletter explosion, email inboxes broke, and "read newsletters inside the RSS reader" became a routine pattern.

To subscribe to a Substack via RSS, append /feed/ to the publication URL, e.g. https://stratechery.com/feed/. Beehiiv works the same way.

YouTube · Podcasts · Social via RSS

Most readers offer integrations to pull non-RSS content.

Thanks to these integrations, RSS readers are gradually turning into "one place for all content" tools.

Read-Later — Instapaper · Pocket (sunset) · Omnivore (sunset) · Wallabag

The read-later market went through upheaval in 2024-2025.

As of May 2026, Instapaper is effectively the only remaining free read-later, with everything else split into paid (Readwise/Matter) or self-hosted (Wallabag, Readeck) camps.

RSS · Atom · JSON Feed · WebSub — Spec Walkthrough

RSS readers consume four kinds of specs.

A minimal JSON Feed looks like this.

{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "My Example Feed",
  "home_page_url": "https://example.org/",
  "feed_url": "https://example.org/feed.json",
  "items": [
    {
      "id": "2026-05-16-1",
      "url": "https://example.org/2026/05/16/post-1",
      "title": "Hello",
      "content_html": "<p>Body</p>",
      "date_published": "2026-05-16T09:00:00+00:00"
    }
  ]
}

Unlike RSS, JSON Feed has no namespace hell and is a one-liner to emit from a static site generator (Eleventy, Hugo, Astro).

ActivityPub · Nostr — Decentralized Content Syndication

The generation after classic RSS is decentralized protocols. Two threads have hardened by 2026.

Subscribing to an ActivityPub actor directly from an RSS reader became real in 2024-2026. Reeder 6 treats an ActivityPub actor as a first-class citizen — paste a Mastodon handle like @<user>@<instance>.<tld> and it works.

For Nostr, a bridge like rsslay converts RSS into Nostr events. The reverse direction (Nostr-to-RSS) is handled by nostr-rss-bridge.

Korea RSS Scene — Daum / Naver / Tistory / Brunch

In Korea, RSS has settled as follows.

The most common Korean setup is "Inoreader Pro ($99/yr) + Naver Blog + Tistory + Brunch + English-language tech publishers". Self-hosting overwhelmingly means FreshRSS.

Japan RSS Scene — Hatena · NewsPicks · SmartNews · Gunosy

Japan's split between RSS and curation apps is more pronounced than Korea's.

Japanese users skew toward Inoreader and Feedly too, but Hatena Bookmark occupies a "one tier above" slot, so users tend not to migrate directly into an RSS reader. Self-hosting splits roughly evenly between FreshRSS and Miniflux.

Newsletter Platforms — Substack · Beehiiv · Ghost · Buttondown · Kit

While RSS readers absorbed newsletters from one side, newsletter platforms have universally exposed RSS from the other (with some overlap with the iter53 blog-platforms post).

Most publishers run on Substack or Beehiiv, both of which expose RSS automatically — so "subscribe to 1,000 Substack authors" is feasible inside Feedly/Inoreader.

AI Features 2026 — Summarization · Classification · Translation

In 2024-2026 the consistent differentiation point for RSS readers has been AI features.

The most aggressive AI users tend to be readers who ingest email newsletters via RSS. They process 200 newsletters a day in 30 minutes via topic filters and summaries.

OPML — The Common Currency for Migration

OPML (Outline Processor Markup Language) is the common currency for reader-to-reader migration. Essentially every reader supports import and export.

<?xml version="1.0" encoding="UTF-8"?>
<opml version="2.0">
  <head>
    <title>OPML Export</title>
    <dateCreated>Sat, 16 May 2026 12:00:00 +0000</dateCreated>
  </head>
  <body>
    <outline text="Engineering" title="Engineering">
      <outline type="rss"
               text="Martin Fowler"
               xmlUrl="https://martinfowler.com/feed.atom"
               htmlUrl="https://martinfowler.com" />
      <outline type="rss"
               text="HN Frontpage"
               xmlUrl="https://hnrss.org/frontpage"
               htmlUrl="https://news.ycombinator.com" />
    </outline>
    <outline text="Newsletter" title="Newsletter">
      <outline type="rss"
               text="Stratechery"
               xmlUrl="https://stratechery.com/feed/"
               htmlUrl="https://stratechery.com" />
    </outline>
  </body>
</opml>

A standard migration looks like this.

  1. Export OPML from the old reader.
  2. Import OPML into the new reader.
  3. Verify category/tag mapping.
  4. Sync unread state (service-dependent; sometimes not supported).
  5. Reconnect API keys and external clients.

After the Pocket sunset announcement, the dominant migration paths were "Pocket to Readwise Reader" and "Pocket to Wallabag (self-host)".

Combination Patterns — How Real Setups Get Built

Common real-world setups people gravitate toward.

The throughline is "separate backend from client". Once you pick a backend (FeedBin/FreshRSS/Inoreader), you can swap clients freely.

Adoption Roadmap — From Zero to Daily RSS User

When introducing an RSS reader for the first time, the safest order is:

  1. Start with about 20 feeds. Favorite blogs + company blogs + 5 newsletters.
  2. Run for a month on free NetNewsWire (iOS/macOS) or free Inoreader.
  3. After a month, refine to the 30-50 feeds you really read daily.
  4. At that point migrate to a paid SaaS (Feedly Pro, Inoreader Pro, FeedBin) or self-host (FreshRSS).
  5. Automate OPML backups monthly.
  6. Add AI rules (Leo AI, Inoreader rules) 1-2 per week.
  7. Read-later tools (Readwise Reader, Instapaper) come after RSS is settled.

Trying to integrate 8 tools on day one means quitting within a month. Add one tool at a time.

Closing — May 2026, "RSS Quietly Returned for a Second Youth"

The takeaway is that "13 years after Google Reader sunset, RSS did not die". But the shape changed a lot. From a simple polling tool, it became the conduit into AI summarization + newsletter ingestion + decentralized protocols.

The two biggest shifts are: first, the newsletter explosion regrew RSS. Substack/Beehiiv/Ghost auto-exposing RSS turned "broken inbox to RSS reader" into the new standard. Second, AI summarization became the top differentiator. Feedly Leo, Inoreader AI, Readwise Ghostreader essentially compete on the same feature.

Don't agonize over tool selection. Whatever combination you pick, "OPML backup + backend separation + a month of refinement" gets you 90% of the way. The rest is taste.

References

Comments

No comments yet.

Sign in to leave a comment