Substack Welcome Email Examples for Free and Paid Subscribers

A Substack welcome email should thank the reader, explain what they will receive, and give them one useful next step. For a free subscriber, that might be a representative article or the resource they requested. For a paid subscriber, start with how to use the benefits they have just purchased.

Below are eight original examples, followed by a reader-experience checklist and a measurement worksheet. These are alternatives for different publications, not an eight-email sequence.

By Subshack. Sources checked September 9, 2026. Publication names, resources, schedules, and benefits in the examples are fictional. The setup instructions are based on official documentation, not a live test in your account.

Choose the welcome email that matches the subscription

Write for the decision the reader has already made. Someone who paid needs a different introduction from someone trying your free newsletter.

These writing goals are suggestions. Substack documents four welcome templates, with paid and founding options tied to having payments enabled. Source: welcome-email types.

These are subscriber welcomes, not a reason to send unsolicited pitches to everyone who follows you. Our Substack followers vs subscribers guide explains the distinction.

How to edit your Substack welcome email

Use the publisher dashboard for the correct publication, rather than your personal profile settings.

1. Open Settings, then Emails.
2. Find the welcome email for the subscription type you are editing.
3. Choose Edit, replace the relevant content, and click Save.
4. Reopen it to check your changes, then test the reader experience described below.

The first three steps follow the official setup instructions, updated December 16, 2025. Reopening and testing are our additional checks.

Check the subject in a received email. The subject lines below are proposed copy. Use the editor's title or subject control where available, and confirm the actual inbox result. The setup article does not specify every subject or preview-text control. Do not paste a second “Subject:” line into the message body.

Manual additions need a separate check. Substack's manual-add procedure includes a choice to send a welcome email. Editing that free welcome message changes the template for future free signups too; it is not necessarily a private, one-off message. Source: manually adding a subscriber.

8 Substack welcome email examples to adapt

Replace the fictional publication details with your own. Anything in square brackets is an instruction to replace manually, not a Substack personalization variable. Turn each link placeholder into a working link before saving. These examples do not require automatic first-name insertion.

1. Free subscribers: introduce a practical newsletter

Use this when the publication teaches a recurring skill and has a useful public starting point.

Subject: Welcome to Studio Practice

Email body:

Hi,

Thanks for subscribing to Studio Practice. Every Tuesday, I send one free lesson about freelance client work, with a practical example.

Start with the project-brief checklist. It covers three decisions to settle before you quote: who approves the work, what's included, and how changes are handled.

Read the checklist: [public checklist link]

Glad you're here,
[Your name]

Personalize: The subject, schedule, and description of the resource. Only call something a checklist if that is what the reader will find.

CTA's job: Get the reader to a concrete example of the publication's value, rather than an undirected archive page.

2. Free subscribers: deliver a resource they requested

Use this when your signup invitation promised a particular download or guide.

Subject: Your Small Systems workflow checklist

Email body:

Hi,

Here's the workflow checklist you signed up for: [checklist link]

It helps you map the steps in a repetitive task before deciding whether to automate it. Start with one task you already know well.

You're also subscribed to Small Systems. Every other Friday, I share a practical workflow, including its setup and limitations.

Thanks for joining,
[Your name]

Personalize: Match the exact resource and newsletter commitment shown at signup. Do not add a newsletter commitment that the reader was never told about.

CTA's job: Deliver the promised resource. Do not unexpectedly put it behind a paid upgrade or an additional compulsory survey.

3. Free subscribers: welcome readers to essays or fiction

Not every publication needs to promise a productivity outcome. Show the reader what kind of writing they can expect.

Subject: A good place to begin with Small Observations

Email body:

Hi,

Welcome to Small Observations. I write essays about ordinary places and the things we notice when we stop rushing through them.

A new essay arrives twice a month. Until the next one, start with “The Shop That Never Changes.” It's about a familiar street, an unfamiliar conversation, and what we miss close to home.

Read the essay: [public essay link]

I'm glad you'll be reading,
[Your name]

Personalize: Replace the fictional essay with a real piece that represents your work. For serialized fiction, consider the first installment instead of the latest chapter.

CTA's job: Offer a reading experience, not a long explanation of why the writing matters.

4. Free subscribers: ask one useful question

Use this when learning about readers will help you choose coverage and you have time to review replies.

Subject: Welcome to Town Ledger. What should we cover?

Email body:

Hi,

Thanks for subscribing to Town Ledger. Every Thursday, I explain one local decision and what it could mean for people living here.

A question before the next edition: which local issue would you most like explained clearly?

Reply with a topic or question. A sentence is enough. It could be a transport change, a council decision, or something you keep hearing about but can't make sense of.

Thanks,
[Your name]

Personalize: Ask a question you can genuinely use. Do not promise to cover every suggestion or reply personally to everyone unless you can do that.

CTA's job: Start a relevant conversation. This version intentionally has no competing article or upgrade link. Substack itself describes asking readers to reply as one possible welcome-email approach. Source: Substack's editorial guidance.

5. Paid subscribers: make the purchased benefits easy to find

Use this when paid membership provides a defined library, recurring resource, or other practical benefit.

Subject: Your Studio Practice member library

Email body:

Hi,

Thank you for becoming a paid Studio Practice subscriber.

Your membership includes the full template library and one new template each month. The member index explains what each template is for and links to the latest versions.

Open your member library: [member index link]

I suggest starting with the project-brief template. You can use it to organize the questions for your next client conversation.

If access doesn't look right, reply and let me know.

Thank you,
[Your name]

Personalize: List only the benefits this plan actually includes. Test the destination using a reader with the relevant access, not just your publisher account.

CTA's job: Help the reader use the purchase. The access-help sentence is a service instruction, not another promotion.

6. Paid subscribers: acknowledge support without inventing exclusives

Use this only when the paid offer supports public work rather than providing a separate paid-content package.

Subject: Thank you for supporting Small Observations

Email body:

Hi,

Thank you for becoming a paid supporter of Small Observations. Your contribution supports the time I spend reporting, writing, and editing these essays.

The essays remain public. There isn't a separate set of paid-only posts to keep up with; supporting the work is what this subscription is for.

Here's a piece that reflects the writing you're helping me continue: [essay link]

Thank you for making room for it,
[Your name]

Personalize: Make sure this accurately describes the offer the reader purchased. Do not use it for a plan that promised exclusive posts or other benefits.

CTA's job: Connect the payment to the work without creating a new obligation for either reader or writer.

7. Founding subscribers: clarify what the higher contribution includes

This example assumes the founding plan adds financial support, not extra deliverables. Rewrite it when your founding plan includes distinct benefits.

Subject: Thank you for becoming a Studio Practice founding member

Email body:

Hi,

Thank you for choosing a founding membership. Your additional support helps fund the time behind Studio Practice.

This plan includes the same template library and monthly resources as the standard paid membership. It doesn't include separate events or private consulting.

Start with the member index: [member index link]

I appreciate your support,
[Your name]

Personalize: State the actual difference between founding and standard paid membership. A warmer thank-you is appropriate; imaginary office hours, consultations, or access are not.

CTA's job: Make the plan understandable and give the reader a place to start.

8. Imported subscribers: explain a move, not a new signup

Use this for an existing, opted-in free newsletter moving to Substack. Substack requires confirmation that imported subscribers opted in to receive email. An address in your contacts is not enough. Source: Substack's import procedure.

Subject: Town Ledger is moving to Substack

Email body:

Hi,

You're receiving this because you signed up for Town Ledger through [previous signup location]. I'm moving the same newsletter to Substack.

The subject and schedule aren't changing: one explanation of a local decision every Thursday. The next edition will come from this publication.

I've put a short explanation of the move here: [migration information link]

Thanks for continuing to read,
[Your name]

Personalize: Name a signup context your readers will recognize. Explain actual changes rather than saying everything is unchanged when it is not. Keep subscription-management options easy to find.

CTA's job: Explain why the message arrived and resolve confusion about the move. This is not a template for introducing an unrelated newsletter to an old list.

Paid migrations need separate checks. Do not add “your billing and access have transferred” without verifying both. Substack documents additional steps for moving paid members; changing the welcome text does not carry out those steps. Source: moving a publication from another platform.

Should a free welcome email ask readers to upgrade?

It can, but it does not have to be the main action.

Substack's own editorial guidance recommends presenting paid benefits and an upgrade invitation early. That is a recommendation, not a requirement for every publication. Source: Substack on welcoming new readers.

Our recommendation is to honor the reason someone subscribed first. If you promised a free checklist, deliver it. If they came for essays, give them a representative essay. Mention paid membership when its value is clear, rather than making the free subscription feel like an incomplete transaction.

For example, a brief, optional note could say:

The Tuesday lessons are free. Paid members also receive the template library and a new template each month. Membership details: [plan link]

That is fictional offer copy. Use it only when the distinction is accurate. Do not add urgency, discounts, or testimonials you cannot substantiate.

The same principle applies to length: include what this reader needs now. A welcome email does not need your complete About page, publishing history, and every social link.

Test the welcome email as a reader

For your own publication's free welcome, a practical end-to-end check is to subscribe through the public signup flow with a separate inbox you control that is not already subscribed. Inspect what arrives and follow the primary action.

Do not treat a free signup as proof that the paid, founding, import, or upgrade route works. Verify the relevant route separately when you use it. A manually added trial should not be assumed to behave exactly like a paid purchase.

If the message is missing, check the address and the inbox's spam or Promotions folder. Substack also provides a reader-side email-delivery test at /account/email-test on the publication. That test checks delivery; it is not evidence that a particular welcome template or paid trigger is configured correctly. Source: Substack's email-delivery troubleshooting.

A successful test is evidence for that inbox and route. It does not guarantee inbox placement for every subscriber.

Check survey links before removing or replacing them

Untouched default free and paid welcome templates may include the New Reader survey. You can remove its button from a welcome email without deleting the survey itself. Source: Substack's survey documentation.

Keep it when the questions support a real editorial decision. Remove it when it competes with the action you actually want, or rewrite the questions before asking readers to answer them.

Removing a button and deleting a survey are different actions. Substack warns that deleting the survey removes its questions and responses and breaks existing links to it. Audit those links before deleting anything. Source: survey deletion behavior.

Can these templates become an automated welcome sequence?

These templates are individual welcomes, not an automatic day-two or day-seven series. Delayed, multi-message welcome sequences were not verified for this guide.

Substack also documents dynamic subscriber segments and targeted email sends. A saved audience that updates automatically is not, by itself, an instruction to send each person a message a fixed number of days after signup. Verify the sending controls separately before promising a sequence. Source: subscriber segments and targeted sends.

Start by making one welcome useful and checking the result. Add follow-up messages only when they have a distinct purpose and a verified delivery method.

Measure the action, not an assumed welcome-email benchmark

Choose a result that matches the email. For a reply-led welcome, review relevant replies. For a survey-led welcome, Substack provides a way to view and export responses. For a resource-led welcome, use clicks or resource visits only where your tools actually expose them. Source: viewing survey responses.

We did not verify a dedicated welcome-email analytics dashboard for this guide. Do not substitute the open rate of a regular newsletter post. If you cannot establish how many welcome emails were sent or delivered, keep outcome counts rather than inventing a response rate.

A shared survey or resource may also get visits from elsewhere. Unless you can distinguish those sources, its total is not a welcome-email result.

Copy this worksheet when you change a template:

Template and version:
Subscription type:
Date the version was saved:
What the reader was promised at signup:
Primary action and destination:
Reader route tested and result:
Observation period:
Outcomes actually observed:
How those outcomes are linked to this welcome, if known:
Sent or delivered count, if available:
Other changes during this period:
What the data cannot establish:
Next change to test:

A before-and-after improvement can suggest what to keep testing. It does not prove that the new wording caused better retention or more paid subscriptions, especially if acquisition sources or the offer changed too.

Keep the welcome consistent with the signup promise

Compare the welcome email with the public description that led someone to subscribe. The subject, frequency, and benefits should describe the same publication.

Our free Substack profile audit can help review public-facing positioning and the stated reason to subscribe. It is Subshack's own tool. It does not inspect private welcome emails or test their delivery, so use it for the public promise and perform the email checks separately. Source: what the profile audit reads.

For the wider acquisition plan, continue with our Substack growth strategy guide.

A good welcome makes the next step clear. It does not ask a new reader to do everything at once.