Mastodon adds newsletters to reach readers outside the fediverse

Mastodon developers added newsletter support in Mastodon 4.6, giving writers, media groups, and institutions a way to send posts to email subscribers outside the fediverse.

The pitch sounds plain: A reader enters an email address and receives updates from a Mastodon account without joining a server. That matters for Mastodon because audience growth has lagged since the first rush of users left X. TechCrunch reports Mastodon now has about 735,000 monthly active users, down from a peak above 2 million.

The change also pushes Mastodon beyond its role as an X alternative. Email gives creators a route to readers who want updates but do not want another social account. Mastodon accounts can move between servers, so a writer can change hosts and keep an audience tied to the open social web.

Mastodon 4.6 also adds refreshed profiles and Collections, a suggested-follow feature that resembles starter packs on other social platforms. Those changes help discovery inside Mastodon. Newsletters target a different problem: readers who sit outside the network.

The technical bet has limits. Server operators must grant the right permissions, and Mastodon chose against turning newsletters on for all accounts. Email costs money at scale, and servers already carry moderation, hosting, and delivery burdens. A small community server may have little appetite for newsletter traffic.

That makes the first users clear. Mastodon said the feature fits institutions that run their own servers or use Mastodon's hosting and moderation services. A newsroom, university, nonprofit, or independent publisher can treat Mastodon as a public feed, a subscriber list, and a portable social identity.

The best case for Mastodon does not copy Substack or Threads. It gives publishers a smaller set of open tools that work together: ActivityPub for social distribution, email for inbox reach, and account portability for moving between hosts. Readers get fewer account barriers. Writers get less dependence on one platform's feed.

The hard part comes next. Newsletter products compete on editing tools, analytics, payments, deliverability, and list management. Mastodon starts with reach, privacy, and portability. Those strengths will appeal to writers who care about ownership. They may frustrate publishers that expect a full newsletter business stack on day one.

Developers can inspect Mastodon's code on GitHub, and server operators can use the Mastodon documentation to assess hosting trade-offs before enabling email features.

Mastodon has tried to grow through values that many users support but fewer users organize their work around: open protocols, portability, and community control. Newsletters give those values a familiar interface. Readers know email. Publishers know email. Mastodon now has to prove that its servers can handle email without making operators pay for growth they did not choose.