How to start a newsletter you actually own

Substack keeps 10 percent of every dollar your paid subscribers send you, and Stripe takes 2.9 percent plus 30 cents a charge plus a 0.7 percent recurring billing fee on top (Substack's published fee schedule; the 10 percent has not changed since 2017, checked August 2026). That is rent. This guide is how to start a newsletter you own outright instead: your name on the domain, a list you can export in one click, and a sender reputation that belongs to you and moves with you.

What owning a newsletter means

A newsletter is owned when it passes three tests. The From address is on a domain you registered. The subscriber list exports to a CSV you can walk away with. The archive lives at URLs you control. Fail any one of them and part of your audience is hostage to somebody else's business decisions.

January 2024 is the case study. Casey Newton's Platformer, then around 170,000 subscribers, left Substack over its refusal to remove pro-Nazi publications and rebuilt on Ghost (Washington Post, January 11, 2024). Molly White's Citation Needed, Ryan Broderick's Garbage Day, and Paris Marx's The Disconnect moved in the same wave. Every one of those exits worked for the same unglamorous reason: email is portable. The leavers exported their lists, kept their Stripe billing relationships, and shipped the next issue from different infrastructure. The churn has since gone fully mainstream. "Substack alternative" ran as a New York Times crossword clue on August 1, 2025. The answer was PATREON.

Do the rent math before you commit to any platform. A newsletter charging $10 a month with 500 paying readers grosses $5,000 a month and hands over about $830 of it in fees, every month, indefinitely: $500 to Substack and about $330 to Stripe (our arithmetic on Substack's published fees, August 2026). The cut grows with your success. The cost of serving you does not.

None of this makes platforms evil, and the last section of this guide covers the cases where starting on one is the right call. The default for anyone playing a long game, though, is the setup below. Seven steps, in the order we would do them.

Step 1: put the newsletter on a domain you own

Register the domain before you pick any tooling. It can be the domain your site already lives on or a dedicated one for the publication; either works, and registration is the cheapest line item in this whole project.

Then wire the DNS that authentication requires, because this stopped being optional. Since November 2025 Gmail hard-rejects unauthenticated mail with a 550 error, and Microsoft has done the same since May 2025 (their bulk-sender enforcement; Google's sender guidelines spell out the requirements). Unauthenticated newsletters no longer drift into spam folders. They bounce.

Three records do the work. SPF lists which servers may send for your domain. DKIM signs each message so receivers can verify it was not altered in transit. DMARC tells receivers what to do when the other two fail, and where to send you reports. They look like this:

Host                                 Type   Value
yourdomain.com                       TXT    v=spf1 include:_spf.yourprovider.com ~all
_dmarc.yourdomain.com                TXT    v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
selector._domainkey.yourdomain.com   TXT    (the DKIM public key your provider generates)

Your sending provider, the ESP relaying your mail, gives you the exact DKIM host and value. Publish DMARC at p=none first so you collect reports without quarantining anything, then tighten the policy once the reports run clean. The record-by-record walkthrough, with verification steps, is in our email deliverability handbook.

Take alignment seriously even when nothing looks broken. In June 2026 we watched Gmail silently reject 73 percent of the mail we were mirroring through a standard forwarding rule, because forwarding breaks DMARC alignment. That number is our own production measurement, and the worst part was the silence: no error ever reached us, the mail just vanished. We replaced the forward with an API-based insert and the failures stopped. Authentication failures are quiet by design, which is exactly why the DNS comes first.

Step 2: send the newsletter from a subdomain

Put the newsletter on news.yourdomain.com and keep the root for everything conversational: your replies, your receipts, and any transactional email like password resets if you run an app. Mailbox providers score reputation per sending stream. When an issue lands badly one week, separation means your one-to-one mail keeps arriving while the subdomain absorbs the dent.

Two honest caveats. A subdomain is isolation, not a wall: sustained bad behavior rolls up to the parent domain's reputation, so treat separation as containment for accidents rather than permission to be sloppy. And a fresh subdomain starts with zero history, which is what the warm-up guidance in step 5 is for.

Once both streams run clean for a few weeks, walk DMARC from p=none to p=quarantine and then to p=reject on each.

Step 3: turn on double opt-in before subscriber number one

Double opt-in means a signup only becomes a subscriber after clicking a confirmation link you email them. Yes, some percentage of signups never click it. Turn it on anyway, from the first subscriber, for three reasons.

It keeps garbage off the list. Typos, bots, and spam-trap addresses stall in the unconfirmed state instead of poisoning your bounce rate, which needs to stay under 2 percent (our send path pauses itself above that line, no human in the loop). It creates a consent record, which matters the day a complaint or a legal question shows up. And it front-loads engagement, because the confirmation click is the subscriber's first positive interaction with your domain.

Reject role addresses at the form while you are at it. info@, admin@, postmaster@, and abuse@ are not people who asked for your newsletter; our own signup validation refuses them outright. Every address that later bounces or complains should land on a suppression list that gets checked before every future send, with hard bounces suppressed permanently.

The stakes are numeric. Google and Yahoo's bulk-sender rules (February 2024, tightened through 2025) want spam complaints under 0.1 percent, and at 0.3 percent Gmail withholds delivery mitigation until you have held under the line for seven consecutive days. A confirmed-consent list is how you live an order of magnitude below those thresholds without thinking about them. The single-versus-double tradeoff has real numbers on both sides; we lay them out in our double opt-in article.

Step 4: write the welcome sequence

Two messages minimum. First the confirmation email: one line, one button, and a subject that plainly says what it is. This is the first subject line your reader ever judges you by, and everything in our subject line guide applies from message one. Then the welcome email, sent the moment they confirm.

The welcome email has four jobs. State what the reader signed up for and how often it arrives, so the promise is explicit. Deliver your single best piece, so their first impression is your strongest work. Ask for a reply, with a real question you intend to answer. And establish the From name and address they will see on every future issue, because a stable sender identity is part of how inboxes learn to trust you.

The reply request is doing more than being friendly. Mailbox providers weight engagement in a strict hierarchy: replies count more than clicks, and clicks count more than opens. A handful of genuine replies in week one tells Gmail more about your domain than a thousand image loads ever will. We collected welcome email examples that earn the reply, with the copy patterns annotated.

Step 5: pick a cadence you can hold for a year

Consistency is a deliverability signal. Mailbox providers build a profile of your volume and rhythm, and both gaps and spikes read as anomalies; our warming playbook treats a missed week as a real cost for exactly that reason. A new domain's reputation matures over 4 to 8 weeks of steady sending, volume should rise no more than 30 percent a day (10 to 20 is better), and Gmail rewards recent engagement while Outlook rewards a long consistent history. Weekly beats daily-then-nothing. Monthly beats weekly-then-burnout. Pick the interval you can still hit in week 40, and put it in the welcome email as a promise.

If you are importing an existing list from a platform, do not blast the whole file from a cold domain on day one. Follow a warm-up ramp. Resend's documented schedule, which we codified into our own send throttle, starts around 150 sends on day one and multiplies by roughly 1.4 daily, reaching about 1,100 a day by day seven. Send to your most recently engaged readers first, the segment that opened or clicked within the last 90 days, and widen from there.

Cadence usually collapses for lack of a plan rather than lack of will. Keep a pipeline of at least eight future issues; our newsletter ideas list is built for exactly that, and how to write a newsletter covers turning an idea into an issue people finish.

Step 6: design for the inbox

Every issue should go out as multipart/alternative: an HTML version and a genuine plain-text version inside the same message. The structure is this:

Content-Type: multipart/alternative; boundary="issue-042"

--issue-042
Content-Type: text/plain; charset=utf-8

The letter itself, readable with no styling at all.

--issue-042
Content-Type: text/html; charset=utf-8

<!doctype html> ...the designed version...

A genuine plain-text part is written for reading, and it is different from the auto-stripped blob of URLs most tools generate. Filters compare the two parts and treat a missing or junk text version as a spam signal, and a minority of your readers will only ever see the text. The full argument, including why we send both on every campaign, is in plain text vs HTML email.

The template rules we enforce on our own sends: at least a 60:40 text-to-image ratio and never image-only, no link shorteners, links living on your sending domain, alt text on every image, and the identical From name and address on every issue. None of this limits good design. Our newsletter design notes walk through the constraints behind the Postcard template our composer ships, and these newsletter examples show how much range fits inside the rules.

Step 7: grow to 500 real subscribers

Never buy a list. The math is short and unforgiving. Gmail's complaint ceiling is 0.3 percent, meaning three spam reports per thousand delivered messages. Nobody on a purchased list asked to hear from you, so it takes only a handful of them pressing Report Spam to push a young domain over the line, and once over it Gmail withholds delivery mitigation until you have stayed under 0.3 percent for seven straight days. Bounces finish the job: brokers cannot promise fresh addresses, and a few percent of dead ones puts you past the 2 percent bounce line. Amazon SES suspends entire accounts at 5 percent bounce or 0.1 percent complaint (their published thresholds). Buying a list is paying money to burn a domain that takes 4 to 8 weeks to warm.

Grow where your work already gets read instead. A signup link in your email signature and social bios. A one-field form on your highest-traffic pages. Guest posts and podcast appearances with the newsletter as the only call to action. Cross-recommendations with adjacent newsletters of similar size, which cost nothing and convert well because the referral arrives with borrowed trust. Five hundred subscribers gathered this way will beat five thousand strangers on every metric a mailbox provider watches.

About those metrics: do not steer by open rate. Apple Mail Privacy Protection preloads images whether or not a human reads the issue, so opens run high and lie to you. Score clicks and replies instead; our open-rate breakdown covers the inflation and the honest way to benchmark. One more myth worth killing: the rules do not wait for Gmail's 5,000-a-day bulk-sender line. The authentication and complaint requirements bite at any volume. We send dozens of messages a day from our own workspace, far under that line, and follow every rule in this guide anyway.

When a platform is the right call

A platform gives you two things your own domain cannot. The first is discovery: Substack's recommendation network sends real subscribers to brand-new publications, and no amount of DNS gives a standalone domain that cold-start distribution. The second is monetization rails: paid subscriptions with checkout, billing, and payouts handled, live in an afternoon, no code.

So here is the honest version of the advice. If your model is paid-first and your audience starts at zero, a platform's cut can be a fair price for those rails while you find your first hundred true readers. Substack's export is genuinely workable, and the January 2024 leavers proved the exit at scale, paid subscribers included. The tradeoff is the 10 percent forever, plus a sender reputation accruing to an address you may not control.

If you start on a platform, keep the exit open from day one. Use a custom domain wherever the platform allows one. Export your subscriber CSV on a schedule, monthly at minimum. And check what your From address is, because that domain is where your sending reputation actually lives. The 10 percent is rent. The list is the part you take with you when you leave.

The launch checklist

Work through these in order; every item is covered above.

1. Register the domain, or pick the subdomain on the one you have.
2. Publish SPF, DKIM, and DMARC at p=none; confirm all three pass on a test send.
3. Point the newsletter at news.yourdomain.com and keep replies on the root.
4. Turn on double opt-in and role-address rejection at the signup form.
5. Wire every bounce, complaint, and unsubscribe into a suppression list checked before each send.
6. Write the confirmation email and the welcome email; ask for a reply in the welcome.
7. Commit to a cadence you can hold for a year, and bank eight issue ideas before issue one.
8. Build the template: multipart with a real text part, 60:40 text-to-image, one-click unsubscribe headers on every send.
9. If importing a list, ramp it: most-engaged first, roughly 1.4x daily growth, no gaps.
10. Send issue one to yourself on Gmail and Outlook and to a mail-tester address before you send it to anyone else.

Reputation only starts accruing once the domain is yours. Register it today and publish the three records; everything else in this guide builds on that.