Best Platform for Newsletters I Have Actually Used

You're probably not choosing a newsletter platform from a blank screen. You already have subscribers, old campaigns, payment records, tags, and a sending domain that you can't casually disrupt. The problem usually appears after something breaks: inbox placement slips, a paid subscriber questions the platform fee, or a sponsor asks for reporting your current tool can't provide.

I've migrated lists, rebuilt sending domains, tested paid subscriptions, and sent campaigns through Substack, beehiiv, Ghost, Kit, and LetterBucket. My view of the best platform for newsletters starts with three jobs, not a feature checklist: reaching the inbox, growing a free audience, and converting attention into revenue.

Table of Contents

• Picking a Newsletter Platform While You Are Already Sending
• The Newsletter Platform Market in 2026
  • Newsletter Platform Categories at a Glance 2026
• How I Tested Each Newsletter Platform
  • What I Recorded During Setup
• Deliverability Test Results Across Inbox Providers
• What Migration Between Platforms Actually Looks Like
  • The Migration Sequence I Use
• Which Newsletter Platform I Would Pick by Use Case
  • For Free List Growth
  • For Paid Subscriptions
  • For Sponsorship Revenue
  • For a Simple Social Reader Experience
• The One Question I Ask Before Recommending a Platform

Picking a Newsletter Platform While You Are Already Sending

The hardest time to change platforms is after your newsletter has become real. I learned that while moving a 14,000-subscriber list across two providers. The work didn't happen in one clean export and import. I had to reconcile tags, suppress old unsubscribes, check historical campaign data, validate the new domain, and rebuild automations that looked simple until I tried to reproduce them elsewhere.

That's the part comparison pages usually hide. They show an editor, a landing page, and a pricing card. They rarely show what happens when a sponsor needs a campaign report, a subscriber wants a refund, or your first email after migration lands in Promotions instead of Primary.

My starting point has often looked messy. One spreadsheet held contacts collected through Gmail forms. Mailchimp contained older campaigns. A separate Substack publication held paid readers. Substack made publishing easy, but exporting a complete content and subscriber history for another workflow was more awkward than I expected. On another project, the trigger was a sponsorship deal that needed better acquisition and click reporting than the existing setup could provide.

My practical rule: I don't switch because another platform has more features. I switch when the current platform is failing a job that affects inbox placement, list growth, or revenue.

Before moving anything, I now document the current system. I record the sending domain, signup forms, welcome emails, audience tags, payment provider, sponsor tracking links, and unsubscribe logic. I also keep a clean export outside the platform. That backup matters because an import can preserve contacts while losing the context that makes those contacts useful.

I use a separate subscriber data management workflow to map fields before I upload a file. It prevents a common mistake, importing every historical address without preserving consent status or suppression data.

For the rest of this comparison, I care less about screenshots and more about what appears in the inbox and on the Stripe dashboard. A platform that saves me ten minutes during setup but takes a revenue share forever may be the wrong choice. A platform with better branding but painful DNS work may still be right for a paid publication. The answer depends on the job the newsletter needs to do next.

The Newsletter Platform Market in 2026

I see four broad product categories competing for newsletter operators.

Substack is the social-first publishing network. It combines writing, subscriptions, recommendations, reader discovery, and community features in one hosted environment. beehiiv is the growth-oriented creator platform, built around referrals, recommendations, analytics, advertising, and audience expansion. Ghost sits closer to an open publishing system, with a content management layer, memberships, and newsletters. Kit, formerly ConvertKit, behaves more like a creator-focused email service provider, with automations, forms, commerce, and audience segmentation.

LetterBucket belongs to the newer group of focused newsletter tools. I use it when I want a direct publishing workflow without adopting the broader marketing machinery of a traditional ESP. Its weakness is clear too, the template editor gives me less control than Ghost or Kit.

The category itself has moved well beyond a niche email-sending toolset. One independent newsletter platforms market report estimates the global market at about $1.8 billion in 2025, with a projection of $3.5 billion by 2034 and a 7.8% CAGR. Another summary estimates the creator newsletter platforms market at $1.76 billion in 2024, forecasting $3.44 billion by 2029 at an 18.2% CAGR. Those are projections, not guarantees, but they show why publishing, payments, delivery, and analytics are converging inside the same products.

The same market report says cloud deployment represented 81.3% of revenue and the software segment held 72.4% of market share. That matches what I see in practice. Most independent operators don't want to assemble a server, email infrastructure, payment layer, analytics system, and publication site separately.

Newsletter Platform Categories at a Glance 2026

Substack remains the historical marker for this shift. It launched in 2017, and public reporting summarized by Newsletter Circle's Substack report says it passed 2 million paid subscribers by February 2023. Later summaries cited there describe more than 35 million active subscriptions and more than 3 million paid subscriptions. The point isn't that every creator should copy Substack. The point is that readers learned to treat newsletters as subscription publications, not merely email campaigns.

How I Tested Each Newsletter Platform

I tested five platforms against the same operating questions: how quickly I could send, how much infrastructure work was required, how monetization worked, and what happened when I needed help. The platforms were Substack, beehiiv, Ghost, Kit, and LetterBucket.

I used a real opt-in campaign for 2,000 contacts I already owned on each platform. I also ran a 14-week paid subscription test on Substack, beehiiv, and Ghost. I didn't judge the tools only from a demo account. I created signup pages, imported contacts, configured sender authentication, built a campaign, and checked the path from reader to payment.

My setup checklist included SPF, DKIM, and DMARC. I treated those as launch requirements, not technical polish. A platform can provide excellent templates and still perform badly if the sending domain isn't authenticated or the audience contains stale addresses.

What I Recorded During Setup

I recorded the time from account creation to first delivered email, the number of screens required to configure a sender, and the steps needed to create a paid offer. I also checked whether I could export subscribers with tags and suppression status intact.

Substack won on simplicity. I could publish quickly, and the reader-facing experience felt familiar. The trade-off appeared when I looked at paid economics. Substack takes 10% of paid subscription revenue, while Stripe processing fees are additional, as explained in this newsletter platform fee comparison.

beehiiv felt more operationally complete for growth. I tested both the free and Scale workflows, including recommendations, referral mechanics, campaign reporting, and monetization tools. Its paid pricing is commonly listed at around $49 per month for Scale and $99 per month for higher tiers, with a free plan for smaller lists, according to this comparison of beehiiv, Substack, and Ghost for local newsletters. I hit a practical limitation when custom-domain access became tied to a 2,500-subscriber paywall in the setup I tested.

Ghost gave me the most control, but self-hosting added maintenance work. Managed Ghost hosting uses a flat monthly plan with no revenue share, and entry pricing is commonly placed around $9 to $12 per month for smaller audiences, based on this Ghost, Substack, and beehiiv pricing comparison. The downside is that ownership also means responsibility for updates, configuration, and troubleshooting.

Kit's forms and automations were useful, especially for creator products and sponsorship workflows. I found the new tier naming confusing, and I had to double-check which automation and commerce functions were available on each plan. LetterBucket was quick to understand, but its limited template editor made branded layouts slower than I wanted.

Deliverability Test Results Across Inbox Providers

Deliverability is the first filter I apply. A beautiful newsletter that lands in spam has no practical value, and an impressive open-rate dashboard can't compensate for poor inbox placement.

I used identical campaign content and split seed addresses across Gmail, Outlook, Apple Mail, and Yahoo. I checked authentication settings and watched where messages appeared. I also used the broader independent benchmark from EmailToolTester's email deliverability testing, which reported Kit at 92.10% overall deliverability, ahead of Mailchimp at 87.52%, GetResponse at 87.50%, ActiveCampaign at 85.79%, Brevo at 83.86%, MailerLite at 77.64%, and Benchmark at 63.88%.

That benchmark also found Kit reached 100% inbox placement in Gmail, Yahoo, and AOL, but only 64.44% in Microsoft inboxes. I take that split seriously. Platform performance isn't uniform across mailbox providers, so I don't treat a single provider's result as a universal verdict.

A separate 5,000-subscriber test list split across Gmail, Outlook, Apple Mail, and Yahoo found Beehiiv and Kit producing 97% to 98% delivery rates and 92% to 94% inbox placement. Ghost and ActiveCampaign were close behind at 95% to 96% inbox placement, while Substack varied from 89% to 96%, according to this independent newsletter platform deliverability test.

The table deliberately avoids pretending that I can attach unsupported exact percentages to every platform and inbox. I use the external benchmarks as directional evidence, then run my own seed tests before a serious migration.

My email deliverability testing process checks SPF, DKIM, DMARC, list hygiene, and provider-specific placement. Authentication took more effort on Ghost and LetterBucket than on Substack, while beehiiv and Kit guided me through the required settings more clearly. None of them removed the need to keep the list clean.

What Migration Between Platforms Actually Looks Like

My working example is a beehiiv to Ghost migration. The first step is a full CSV export from beehiiv, not just a list of active subscribers. I want email addresses, consent status, tags, custom fields, subscription state, and suppression records where the platform makes them available.

I then make a copy and clean it outside the destination platform. I remove duplicates, preserve unsubscribed addresses in a suppression file, rewrite tags to match Ghost's member structure, and map custom fields deliberately. A field called source_referral may not have an equivalent destination field, so I decide whether to preserve it, rename it, or discard it before import.

The Migration Sequence I Use

1. Export the source list. I download the complete audience and campaign data, then keep the original file untouched.

2. Clean the working file. I remove duplicate rows, standardize encoding, check malformed addresses, and separate unsubscribed contacts from active members.

3. Map fields. I translate tags, paid status, acquisition source, and custom properties into the destination platform's available fields.

4. Import a small batch first. I test character encoding, unusual names, commas in fields, and empty values before loading the full audience.

5. Authenticate the sending domain. I configure SPF, DKIM, and DMARC before sending from the new provider. The first campaign shouldn't be the moment I discover that authentication is incomplete.

6. Warm up gradually. I send first to the most engaged readers, then expand in stages while watching bounces, complaints, and inbox placement.

Ghost's import process exposed small problems that weren't obvious in the original CSV. Character encoding affected names with accented characters, and some fields needed rewriting instead of direct mapping. The platform itself wasn't the only variable. The database structure I had built over time carried assumptions from beehiiv that Ghost didn't share.

The first 30 days after cutover produced an open-rate dip in my migration. I recovered baseline placement with a warm-up schedule that started with recently engaged readers, followed with the next active segment, and only then included older contacts. I also sent a re-engagement message before mailing the full list again.

For a list under 25,000 subscribers, I budget roughly 8 to 12 hours of operator work. That estimate covers export, cleaning, field mapping, DNS configuration, test sends, payment checks, and the first monitoring period. It doesn't include rebuilding a complex website or redesigning every historical email.

Migration warning: Never treat an unsubscribe file as disposable. Importing a previously suppressed address can damage trust and create a compliance problem before your new platform has sent its first regular issue.

Which Newsletter Platform I Would Pick by Use Case

I don't have one universal winner. I choose based on how the publication grows and earns money.

For Free List Growth

I'd choose beehiiv for a free newsletter that needs to grow before it monetizes. Its referral program, recommendation network, analytics, and advertising options are closer to the actual work of building a media list than a standard broadcast tool.

The downside is cost and plan pressure. A free plan can help at the start, but the features that matter most for a serious growth operation sit inside paid tiers. I'd also verify custom-domain terms before committing, especially if the list is approaching the 2,500-subscriber threshold described in my test.

For Paid Subscriptions

I'd choose Ghost when the publication sells paid access and the operator wants control over branding, pricing tiers, content structure, and member data. Ghost's managed hosting avoids a platform revenue share, which is materially different from Substack's model.

The trade-off is setup. Self-hosted Ghost requires technical maintenance, and even managed hosting still asks me to understand the publication stack. If I want to write and sell without touching configuration, Ghost may feel like too much work.

For Sponsorship Revenue

I'd pick Kit for a creator newsletter built around sponsorships, products, and automations. I like being able to connect subscriber actions to sequences and commerce events. Its sponsorship marketplace and creator-focused workflows are more relevant here than a basic publishing editor.

Kit's weakness is complexity. The newer plan names make comparisons slower, and I have to inspect the exact limits before building a workflow. Independent testing also shows that deliverability can vary sharply by mailbox provider, especially Microsoft inboxes.

For a Simple Social Reader Experience

I'd choose Substack for a solo writer who wants to publish quickly, benefit from a reader network, and accept platform dependency. The writing and subscription flow are straightforward, and the social layer can matter when the creator doesn't want to build discovery from scratch.

The cost is control. Substack's 10% paid subscription fee, plus Stripe processing fees, can become meaningful as revenue grows. Free plans also don't offer the same custom-domain control I get from a self-owned publication.

For a broader decision framework, I use these newsletter use cases rather than asking which platform has the longest feature list.

I also keep LetterBucket in my stack for focused newsletter operations. I like its direct workflow, but I wouldn't choose it for a publication that depends heavily on advanced design systems or complex automation. The editor is the limitation I notice first.

The publisher behind this site also offers Grow and monetize your newsletter, which combines newsletter growth and monetization guidance for operators who want a separate layer of tactics alongside their sending platform.

The One Question I Ask Before Recommending a Platform

I ask one question before I ask about subscriber count:

How will this newsletter make money, or does it need to make money at all?

That answer usually removes most of the confusion.

If the answer is not yet, I look for low-friction publishing, list ownership, deliverability controls, and a growth loop. beehiiv is my usual choice when referrals, recommendations, and advertising may matter later. Substack works when the writer wants the simplest possible publishing and discovery experience. LetterBucket can suit an operator who wants a focused workflow without adopting a larger marketing suite.

If the answer is paid subscriptions, I compare the platform fee against the value of control. Substack is easy, but its 10% platform fee is a permanent cost on paid revenue, with Stripe fees added separately. Ghost demands more setup, but its managed hosting uses a flat monthly model without revenue share.

If the answer is sponsorships, I prioritize audience segmentation, sponsor reporting, ad insertion, and the ability to run repeatable workflows. Kit fits that job better than a minimalist publishing system, although its tier structure needs careful checking. beehiiv is also strong when sponsorship operations sit alongside referral growth and media-style analytics.

If the answer is multiple newsletters or a small media operation, I care about repeatability. I need consistent domains, clean subscriber movement, campaign reporting, and a way to separate audiences without creating a maintenance nightmare. That may push me toward Kit, beehiiv, or Ghost depending on whether the main revenue comes from ads, subscriptions, or owned products.

Decision rule: Subscriber count tells me how much a platform may cost. Revenue intent tells me whether the platform is worth using.

Before I migrate, I write down five answers:

• Revenue model: Is the next dollar coming from subscriptions, sponsorships, products, or nowhere yet?
• Ownership: Can I export contacts, suppressions, tags, and payment records?
• Inbox requirements: Have I tested Gmail, Outlook, Apple Mail, and Yahoo separately?
• Migration cost: Can I spare the operator time for cleanup, DNS, testing, and warm-up?
• Exit plan: If the platform changes its pricing or product direction, can I leave cleanly?

My personal default is beehiiv for free-list growth, Ghost for a control-heavy paid publication, Kit for sponsorship and creator-business workflows, and Substack for simple writer-led publishing. I use LetterBucket when a focused newsletter workflow matters more than a deep template editor. Pick the platform that matches your revenue path, export your data before you need it, and run a small authenticated test campaign before moving your full audience.

If you're choosing today, write down your monetization model first, then test two platforms with a small opt-in segment. Check inbox placement, export quality, payment flow, and the exact cost of your next stage of growth before you migrate the full list.