Substack vs Beehiiv vs Ghost: UK Journalist Comparison 2026

What each platform does and who it's for

Substack is the easiest platform to start with — sign up, start writing, and publish within minutes. It has a built-in reader discovery network (Substack Recommendations) that can drive new subscribers when other writers recommend you. The downside is the 10% revenue share on paid subscriptions, which becomes significant at scale.

Beehiiv launched in 2021 and was built specifically for newsletter publishers who want to grow. It offers a referral programme (readers can refer friends in exchange for rewards), richer analytics than Substack, and no revenue share. The tradeoff is a less polished writing experience and less built-in discoverability.

Ghost is the most powerful option but also the most technically demanding. It supports membership tiers, custom themes, a full website CMS, and multiple newsletters. Ghost(Pro) is the managed cloud version; self-hosting gives you complete control. Ghost takes no revenue share — you pay a flat monthly fee and Stripe fees only. It suits publications that want a platform they will never outgrow and are comfortable with some technical configuration.

Platform comparison at a glance

Red flags to watch for

• ⚠Locking into a platform without testing the subscriber export process — always export a test CSV before you have thousands of subscribers.
• ⚠Ignoring revenue share at scale: at 1,000 paying subscribers at £10/month, Substack's 10% costs £1,000/month. At that point, Beehiiv or Ghost pays for itself within weeks.
• ⚠Not reviewing the platform's Data Processing Agreement before collecting subscriber data — all three publish DPAs but you need to sign or accept them explicitly.
• ⚠Choosing a platform based on features you do not use — most journalists need email delivery, a subscriber list, and an unsubscribe mechanism. Everything else is optional.
• ⚠Self-hosting Ghost without a technical resource — server maintenance, SSL renewals, and software updates are your responsibility.
• ⚠Assuming paid subscribers can be automatically migrated between platforms — they cannot; migration requires subscribers to re-subscribe.
• ⚠Not setting up a custom domain — newsletters sent from @substack.com or @beehiiv.com addresses look less professional and make future migration harder.
• ⚠Never testing the unsubscribe flow end-to-end — a broken unsubscribe link is a PECR violation.

Platform selection checklist

• I have reviewed the platform's Data Processing Agreement and accepted it.
• I have tested the subscriber export (CSV) to confirm it works and includes email addresses.
• I understand the revenue share model and have calculated the cost at my target subscriber volume.
• I have tested the unsubscribe flow from a real subscriber email end-to-end.
• I have confirmed DKIM and SPF are set up correctly for my custom domain (or that the platform handles this).
• I have reviewed the paid subscription and monetisation options against my editorial goals.
• I have a migration plan if I move platforms — including how I will communicate the change to subscribers.
• I am sending from or plan to set up a custom domain rather than the platform's own subdomain.

Common mistakes

• ›Choosing Substack because it is popular without factoring in the 10% revenue share at projected scale.
• ›Choosing Ghost's self-hosted option without a plan for server management and software updates.
• ›Not understanding that Substack's Recommendations feature surfaces your newsletter to new readers — this discovery benefit has real monetary value that partially offsets the 10% fee for small publications.
• ›Signing up for a paid Beehiiv plan before testing whether the free tier meets your needs (it often does for the first 2,500 subscribers).
• ›Migrating between platforms without exporting subscribers first and without informing subscribers of the move.
• ›Assuming that all three platforms handle DKIM/SPF automatically — Ghost self-hosted requires you to configure this yourself.
• ›Not reading the DPA before collecting subscriber data — the DPA specifies how each platform handles your subscribers' personal data under UK GDPR.
• ›Building an audience entirely on a platform without ever testing a migration path — lock-in risk is real even when subscriber export is technically available.

Related guides

Primary sources

Frequently asked questions