The annoying truth about email newsletters is that the inbox is a terrible reader. Substacks are buried under receipts, calendar invites, and shipping notifications. You open the app on Monday morning, see 47 unread newsletters, declare bankruptcy, and Archive All. Three weeks later you realize you missed a piece you actually wanted to read.
The fix is older than the problem: pull the Substack into an RSS reader, where it sits alongside the rest of your reading queue, gets read on your schedule, and never sends you a "we miss you" re-engagement email. Substack supports this out of the box — every publication ships a public RSS feed — but the company does not advertise it because RSS subscribers do not show up in their growth dashboards. This post is the 5-minute walkthrough they will not write themselves.
Every Substack Has a Hidden /feed URL
The convention is simple: append /feed to any Substack URL. That's it.
https://shenhuang.substack.com → publication homepage
https://shenhuang.substack.com/feed → RSS feed (Atom 1.0)
This works for every publication on the platform — paid, free, custom domain, default subdomain. If the publication is on a custom domain like byline.example.com, you still add /feed to the root and it resolves. There is no API key, no signup, no rate limit you'll realistically hit as a reader.
A few quick verifications:
https://stratechery.com/feed(custom domain) — works.https://platformer.news/feed(custom domain) — works.https://noahpinion.substack.com/feed(default) — works.https://www.notboring.co/feed(custom domain, Substack-hosted) — works.
If the URL returns a 404 you are probably on the wrong domain. Check whether the publication migrated off Substack (Ghost, Beehiiv, and Buttondown all use their own feed conventions) by viewing page source and searching for link rel="alternate" type="application/rss+xml" — that's the universal way to find the canonical feed URL on any blog.
Paid Substacks: The Private RSS URL
For paid newsletters where you have a subscription, the public /feed URL only contains free posts and previews. To get paid content you need your personal RSS URL, which embeds an auth token. Find it under:
https://substack.com/account/reading
Look for the "Get private RSS feed" section. The URL looks like:
https://your-handle.substack.com/feed/private/<long-token>
Treat this URL like a password. Anyone who has it can read your paid subscriptions. Do not commit it to git, do not paste it in a Slack channel, and do not use it in an RSS reader you do not trust. Cloud RSS readers (Feedly, Inoreader) will store it on their servers. Local RSS readers (Reeder, NetNewsWire, miniflux self-hosted) keep it on your device.
Consuming the Feed: Pick a Reader
Once you have the URL, the only decision is which reader catches it. The good options in 2026 split into four camps:
Cloud sync, polished mobile: Feedly, Inoreader, NewsBlur. All charge ~$8–15/month for the features power users actually want (folder tagging, search, mute filters, full-text extraction). Free tiers exist but cap feeds at 100. Inoreader is the most powerful, Feedly the most polished, NewsBlur the cheapest.
Native Apple, fast: Reeder 5 ($10 one-time, syncs via iCloud) is the gold standard if you live in Apple's ecosystem. It does not need a cloud account — feeds sync between your devices via iCloud Drive. Beautiful typography, fluid swipe gestures, no upsell. The Mac and iOS versions are separate purchases.
Self-hosted, geek: Miniflux (single Go binary, Postgres) or FreshRSS (PHP, MySQL/SQLite). Both run on a $5 VPS for a decade. You own the data and the uptime. Pair with Reeder via Fever or Google Reader protocol.
Aggregator-style, summary-first: OrangeBot does not require you to add feeds at all — it pulls 8 source streams (Hacker News, Hugging Face, Product Hunt, etc.) and ships a daily digest with summaries, so you read the day instead of N individual posts. Closer to a curated newsletter than a traditional reader.
If you are coming from "I just want my 6 newsletters in one place," start with Reeder + iCloud or self-hosted Miniflux. Skip the cloud subscription unless you genuinely need cross-device sync, search across years of archives, or team sharing.
Validating a Substack Feed Programmatically
If you are wiring the feed into a script (custom dashboard, automation, LLM digest), the contract is Atom 1.0 — not RSS 2.0 despite the /feed path. Most parsers handle both transparently. Quick validation:
curl -sSL https://shenhuang.substack.com/feed | head -40
# Should start with <?xml version="1.0"
# Root element: <feed xmlns="http://www.w3.org/2005/Atom">
For Node:
import Parser from 'rss-parser';
const parser = new Parser();
const feed = await parser.parseURL('https://shenhuang.substack.com/feed');
console.log(feed.items.map(i => ({ title: i.title, date: i.isoDate })));
For Python:
import feedparser
feed = feedparser.parse('https://shenhuang.substack.com/feed')
for entry in feed.entries[:5]:
print(entry.title, entry.published)
Substack feeds include the full post content in the <content> field by default, so you can extract the body for further processing (LLM summarization, search indexing, Pocket-style read-later). The feed updates within minutes of a new post going live.
When RSS Beats the Inbox (and When It Doesn't)
RSS wins when you read on your schedule, want to batch-process a list of publications, or refuse to give an email address. It is also strictly more searchable — once posts are in your reader, they are indexed locally forever, not dependent on whether the publication still maintains its archive.
The inbox wins when you actually want urgency — daily-trading newsletters, breaking-news alerts, anything you would set up a notification for. RSS readers can push notifications but it's clunkier than a real email or Slack channel.
The boring conclusion: use both. Subscribe by email to the 2–3 newsletters whose every post you want to read the day it ships. Subscribe via RSS to the 20+ publications whose posts you want to browse on a slow Sunday. The 80/20 of your reading attention should be in RSS where you can control the rhythm.
FAQ
Does Substack rate-limit RSS polling? Soft yes. Polling every few minutes is fine. Polling every second from one IP will eventually 429 you. Most readers default to 30–60 minute intervals; that's safe.
Will my Substack subscriptions know I'm reading via RSS? No. Substack tracks email opens, not RSS reads. If you're a paid subscriber the author's revenue is unaffected by whether you read in email, web, or RSS.
Can I get only free posts from a paid Substack?
Yes — the public /feed URL returns free posts and free preview snippets of paid posts. You won't get the full paid content without the private URL.
What if a Substack disables RSS?
A few publications have toggled RSS off historically (Substack added the toggle in 2022). If /feed returns 404 or an empty feed, the author has disabled it — there is no workaround other than asking them or scraping the site (against ToS).
How is this different from OrangeBot? OrangeBot is an aggregator across 8 sources with daily AI-summarized digests. Substack RSS gives you raw individual posts from one publication. They solve different problems — use OrangeBot for daily-news situational awareness; use RSS for following specific writers.
If you've been drowning in newsletter email, the move is to pull every Substack into an RSS reader this weekend and unsubscribe from the email list. Two related reads: OrangeBot vs Feedly compares the aggregator vs reader approach head-to-head, and the Sources directory lists the 8 tech-news feeds OrangeBot pre-bundles so you don't have to add each one yourself.