Independent software research · October 2026

beehiiv vs Substack: what changes when readers start paying?

A paid newsletter can have a healthy audience and still make very little money. Before comparing platform fees, decide whether readers are paying for an ongoing publication, a community, or access to something you already sell. That choice matters more than the size of a free subscriber allowance.

Our judgment: Substack deserves a serious look when you want to publish without a recurring platform bill and its reader-facing network suits your work. beehiiv becomes more compelling when you want its publishing workflow and the cost of the required plan makes sense against your actual subscription revenue. Moving an established publication needs a separate migration decision. A favorable fee calculation does not establish that your paid readers and archive will transfer cleanly.

Disclosure: StackEvidence has a beehiiv affiliate relationship. We may earn a commission from an eligible purchase through our labeled referral link. This guide is based on official documentation and reproducible examples, not matched hands-on testing of these platforms. Substack remains a legitimate choice.

Start with the publication you can sustain

Picture two writers with 2,000 email subscribers. One sends a free monthly essay and has no immediate plan to charge. The other publishes a weekly specialist briefing and already has 100 paying readers. Their contact counts match. Their software economics do not.

For the first writer, a paid feature checklist can be a distraction. The useful questions are whether writing and publishing feel manageable, whether readers can subscribe easily, and whether the archive presents the work well. Paying to remove a revenue share before there is revenue creates an expense without the corresponding saving.

The second writer needs a closer account of billing, reader access and recurring cost. A publication with annual subscribers also has obligations extending beyond the month it changes software. The unused portion of a reader's subscription is a service commitment, not spare cash available to fund a move.

Neither platform supplies the reporting, judgment or publishing discipline that makes a newsletter worth paying for. Evaluate the operational job you need it to do.

The fee comparison, with the missing costs left visible

Substack's official fee policy says free publishing has no platform subscription charge. When readers pay, Substack retains 10% of subscription revenue and payment-processing charges also apply. beehiiv advertises no platform percentage on paid subscription revenue, but the relevant paid subscription functionality requires an eligible plan. [Sources: Substack fees; beehiiv pricing.]

That creates a useful first calculation:

Monthly platform-only crossover = the required fixed monthly platform cost ÷ 0.10.

The result is a comparison of platform charges. It is not profit, the number of readers you will acquire, or a promise that moving saves the difference. Add processing, taxes where applicable, extra tools and migration work before making a decision.

A reproducible example

Use a hypothetical fixed software cost of $60 per month. This is an illustration, not a beehiiv quote. Suppose each paying reader pays $10 monthly, without discounts or refunds.

The crossover is $600 of monthly gross receipts: $60 ÷ 0.10. At a $10 monthly subscription, that corresponds to 60 paying readers. Nothing in this example predicts that 60 people will pay.

Now add a one-time $240 migration effort, valued by the publisher. If the fixed-fee option saves $40 monthly after comparable ongoing costs, the simple recovery period is six months. If you only expect to continue for three months, the move is harder to justify. If migrating adds another $15 recurring tool, the monthly saving becomes $25 and recovery takes 9.6 months. These are arithmetic scenarios, not forecasts.

Processing fees do not disappear

Keep payment-processing percentages and fixed per-payment charges on separate lines. The Substack fee page lists both Stripe card processing and a recurring Billing charge for the example US arrangement. beehiiv's pricing FAQ also identifies processing charges. Country, payment method, currency and the actual arrangement can change the result. Do not assume both platforms have identical processing totals merely because both use Stripe.

Annual subscriber payments also change cash timing and the number of payment transactions. A reader paying $100 once a year is not twelve $10 transactions. Compare annual cash obligations with annual receipts, then use monthly equivalents only to understand the ongoing burden. A discounted annual platform rate is normally an upfront commitment, not permission to pay that smaller amount monthly.

What October's beehiiv plan changes mean for this decision

beehiiv's October 1 announcement maps Launch to Free, Scale to Lite and Max to Pro. New-customer pricing applies from October 1; existing customers move at their first renewal on or after November 1. Some cached versions of the public pricing page still show former names, so compare the actual plan selector and checkout before buying. [Source: beehiiv plan announcement.]

A plan's maximum supported audience is not the audience included in its cheapest quote. Record your subscriber count, billing cadence and required features alongside the price. This guide deliberately does not turn an entry-tier price into a universal beehiiv bill.

For context, beehiiv's October 13 pricing guide lists Lite at $59 month to month, or a $49 monthly equivalent with yearly billing, at 1,000 subscribers. That is a dated entry quote, not a price for a 100,000-person list. Confirm the current selector and total amount due before committing. [Source: beehiiv current pricing guide.]

Also separate Free from temporary paid-feature access. beehiiv's trial guide describes limited Pro-feature access and says the account remains Free without an upgrade. Paid-subscription setup and website-domain connection are excluded during that trial. A successful trial workflow may still need a paid plan afterward. [Source: beehiiv trial documentation.]

For a newsletter that stays free, compare the actual free publishing workflow first. A revenue-share advantage has no immediate monetary value when there are no paid subscriptions.

Reasons to choose Substack even when a fixed fee looks cheaper

Substack's official migration guide points readers toward its Recommendations and Notes environment. If conversations and introductions there are already part of how people find your work, include that in the decision. Exporting email addresses does not carry a social relationship into another platform. [Source: Substack's beehiiv migration guide.]

This is a reason to investigate your own acquisition evidence, not to assume a network supplies customers. Look at where recent subscribers actually came from and what they subsequently read or bought. An audience that mostly arrives through your own website may be less dependent on a platform's social features. A writer who regularly gains engaged readers through those features may value them more than a modest fee difference.

Staying can also be the sensible choice when your current publishing routine works and a move would interrupt a promised series. Reducing a percentage fee is less attractive if it delays the work people are paying to receive.

Reasons to shortlist beehiiv

Shortlist beehiiv when the product fits how you intend to operate a publication and the required plan fits your budget. Its documentation covers publication content, subscriber records and paid-access migration as separate jobs. That makes it possible to ask specific implementation questions instead of assuming a list import accomplishes everything.

A publisher with dependable paid revenue can model a fixed software bill more usefully than a new writer guessing at a future conversion rate. A team wanting to evaluate publishing, automation and other supported capabilities together can also benefit from one documented test plan. Check the exact features you need rather than buying the larger plan for a vague expectation of growth.

Keep ad-network or recommendation earnings out of the base budget unless you have actual eligible activity to support them. Availability of monetization tools is not a revenue guarantee, and a vendor's illustrated earnings are not your expected results.

Migration: inspect access before moving money

beehiiv's Substack migration instructions warn that paid-content setup matters before import. Without its specified Stripe connection and paid tier, imported paywalled content can become visible to nonpaying readers. The guide also explains that precise paywall placement does not simply transfer. That is a more consequential risk than a slightly different template. [Source: beehiiv Substack migration guide.]

Use a private migration inventory with four separate counts: free subscribers, paying subscribers, content items and special access arrangements. Keep unsubscribed or suppressed addresses out of an ordinary active-subscriber import. Reconcile permissions and paid access before resuming sends.

The same migration guide treats complimentary, gifted and iOS subscriptions separately from Stripe-paid subscriptions. It describes additional work to preserve access for those groups. Do not turn that into a blanket promise that every reader's billing transfers automatically.

These checks are worth completing before committing to a move:

1. Reader access: Can a free reader and a paying reader see the right material after a controlled import?
2. Payment continuity: Which existing subscriptions can continue, and which require a different process? Who prevents duplicate billing?
3. Content: Are previews, images, old links and selected dates intact? Keep the originals while checking.
4. Consent and suppression: Can you preserve who may receive mail, including people who unsubscribed?
5. Communication: Can you explain the change without telling readers to enter payment details through an unfamiliar, unverified link?

For a move in the opposite direction, Substack's own guide says its ordinary subscriber import creates free subscribers and describes limits around importing beehiiv premium content. Do not assume reverse migration is a one-click restoration of the same paid business. [Source: Substack's beehiiv migration guide.]

A decision you can make before starting a trial

Write down three numbers: current gross paid-subscription receipts, the fixed cost of the plan you would actually need, and your best estimate of one-time migration work. Then name the one workflow that could justify switching even if the charges were equal.

If there is no meaningful paid revenue and no necessary paid feature, begin with the free option that makes publishing sustainable. If Substack's environment is working for you, keep that value in the comparison. If beehiiv offers a better workflow and the arithmetic still works after costs and transition effort, it deserves a closer evaluation.

You can also keep your current platform. An unanswered migration question is a reason to investigate before moving, not a reason to gamble on your subscribers' access.

Continue your research

Our email-platform migration checklist covers broader transition planning. The email marketing software guide puts publication platforms beside other email-software use cases.

Considering beehiiv? Review beehiiv through StackEvidence's affiliate link. We may earn a commission from an eligible purchase. Compare the official plans and Substack's fees before deciding.

Sources and research limits

Official sources checked October 20, 2026, U.S. Central: beehiiv pricing; October plan announcement; trial guide; Substack-to-beehiiv migration guide; Substack fee policy; Substack's beehiiv migration guide. Full URLs appear in the source list below. Calculations use stated hypothetical inputs and exclude unmodeled costs. No new account, live migration, deliverability comparison, checkout or paid subscription was tested for this article. Renewal and account-specific offers still need checking when you buy.