RSS vs Email Newsletters: Which Should You Actually Use?

Anyone who used RSS in its heyday has, at some point, watched the newsletter boom with a certain irritation. We already had a way to follow writers without an algorithm deciding what we saw. It was open, it worked, and then everyone moved to email — which is worse in several obvious ways.

That reaction is fair and also incomplete. Email won for reasons that aren't stupid, and the two formats are good at genuinely different things. Here's the honest comparison.

For anyone who missed the format entirely: RSS is a file a site publishes listing its recent posts. A feed reader checks those files and shows you what's new. No account, no address, no middleman — you pull the content when you want it rather than having it pushed to you.

What RSS is better at

You control the sorting. A feed reader is your interface. You group, filter, mark read and skim on your terms, and no sender can influence placement. Email clients are converging on this with categories and filters, but the reader was designed for it.

Nothing about you leaks. Subscribing to a feed typically involves no account, no address, and no record on the publisher's side of who you are. Compare that with email, where the publisher knows your address, roughly where you opened the message, and which links you clicked.

Zero inbox cost. Adding a feed costs you nothing in your primary attention stream. Adding a newsletter costs you inbox space, which is why people are so much more cautious about subscribing.

No unsubscribe problem. Removing a feed is one click with no confirmation, no preference centre, and no chance the sender keeps mailing you.

It can't be taken away. A feed is a file on a server. There is no platform in between to change its terms.

What email is better at

It reaches people. This is the whole story of why email won. Everyone has an inbox and checks it. Asking a reader to install a feed reader first loses most of them, and writers noticed.

It supports a business. An email list is an asset a writer owns and can monetise — paid tiers, sponsorships, a direct relationship. RSS gives you readers you cannot count, contact, or charge. That difference funds a large share of the independent writing that exists today, including most of what a feed reader would be full of.

It arrives. A newsletter turns up whether or not you remember to open an app. For anything you genuinely don't want to miss, push beats pull. Feed readers are famous for the moment you open one after three months to find 4,000 unread items.

The format encourages a different kind of writing. Newsletters tend to be more personal and more finished than blog posts, because the writer knows it lands in your inbox and can't be edited afterwards. That constraint produces better writing more often than it produces worse.

The reader's real trade-off

Stripped down, it's push versus pull, and the correct answer depends on the content rather than on your principles.

Push is right for a small number of things you'd be annoyed to miss. The interruption is the feature — it means you never need to remember to check.

Pull is right for a large number of things you want available but don't need promptly. Fifty feeds you dip into is a perfectly healthy setup. Fifty newsletters is a problem, and it's the same volume of content.

This is why the number of things you follow should determine the format, not the other way round.

The hybrid setup

Most people who use both end up somewhere like this, and it's worth stealing.

Three to six newsletters by email — the ones with a voice you actively want to hear from, where the arrival is welcome. Everything else in a feed reader: news sites, company blogs, release notes, anything you want access to rather than delivery of.

Two techniques make this work better than either alone. Many newsletters publish a web archive with a feed, so you can follow them by RSS instead of email if you want them in the pull pile — worth checking before subscribing to something you're unsure about. And several feed readers offer a per-user email address, so a newsletter that has no feed can still be routed into the reader, which gives you email's availability with RSS's interface.

What happened to RSS, briefly

The usual story is that Google Reader's shutdown in 2013 killed RSS. That's part of it, but it flatters the format to leave it there.

RSS lost because it was built for readers and gave publishers nothing. You couldn't measure your audience, contact them, or make money from them, and full-text feeds actively removed the reason to visit a site that sold advertising. So publishers truncated their feeds, then neglected them, then quietly dropped them. The format didn't fail technically — its economics never worked for the people who had to publish it.

Email inverted every one of those. A subscriber is a countable, contactable person with a plausible path to revenue. That is why independent writing moved to newsletters, and it's worth understanding before treating the shift as a collective lapse in judgement.

The encouraging part is that RSS never actually went away. Most publishing systems still emit a feed by default, including most newsletter platforms, and the reader ecosystem is small but healthy. It just stopped being where the writing was announced.

If you want to try RSS

It's in better shape than its reputation suggests. Feed readers are actively maintained, most sites still publish feeds even when they don't advertise them, and several readers will find a site's feed from its homepage URL alone.

Start with ten feeds, not a hundred. The classic failure is importing an enormous list, drowning, and abandoning it — which is precisely the same failure people have with newsletters, for the same reason. The format changes nothing about how much you can actually read.

That last point deserves emphasis, because it's the thing both camps get wrong in the same way. Neither RSS nor email creates reading time. If your problem is volume, moving between them accomplishes nothing; you need to follow fewer things or read on a schedule. We cover the schedule half in building a reading routine.

A note on newsletters that also publish feeds

More do than you'd expect. Most newsletter platforms generate a feed for the web archive automatically, even when the writer has never mentioned it, and it's often at a predictable path — try appending /feed or /rss to the archive URL, or simply paste the homepage into a reader and let it look.

This is genuinely useful for newsletters you're curious about but not ready to give inbox space to. Follow by feed for a month, see whether you read it, and subscribe by email only if the answer is yes. It's the cheapest possible trial, and the writer still gets a reader.

Where we land

Use email for the handful of writers whose next piece you actively want. Use RSS for breadth. Don't treat the choice as a matter of principle — the writers you like need to be able to make a living, and for many of them the email list is how that happens.

If you're building out the email side, the awkward part is discovery and bookkeeping: newsletters are hard to find because they live inside inboxes, and easy to lose track of because every signup is a separate form on a separate site. That's the gap Subscribeam fills — browse a curated directory, pick what you want, enter your email once, and keep every subscription in one place you can prune later.