The short answer: to turn a podcast episode into a newsletter, don't announce the episode. Pick one idea from it and write 200 to 300 words about that idea, with a subject line that names it, a line of preview text that adds to it, and a single link to listen. Choose one angle per email: the guest, a surprising point, or what the reader will learn.
Most podcast newsletters are a title, a cover image, a paragraph of show notes and a "listen now" button. They get opened by the people who were going to listen anyway, and ignored by everyone else. Your list deserves better than that, because it is the one audience you own. Email gives you a direct subscription relationship, but inbox filtering and deliverability still affect who sees the message. The subject line helps readers decide whether to open it.
This guide covers how to write an episode newsletter that people open, read and reply to, with templates you can reuse every week.
Why the newsletter is worth the most effort
Of everything an episode can become, the newsletter is the piece most worth doing well:
- You own the list. A platform can change what it shows people overnight. Your email list stays yours.
- Subscribers opted in. They already said yes to hearing from you, which makes them the warmest audience you have.
- Replies happen here. For B2B shows especially, the reply to a newsletter is often where a conversation, and sometimes a deal, starts. Nobody replies to a feed post the way they reply to an email.
- It sends people to the episode. A good newsletter gives people one idea and a reason to hear the rest.
If you only have time to repurpose an episode into one thing, a strong newsletter is a good choice. If you want the whole set, the complete podcast repurposing workflow covers every format.
Three angles that work
Every episode can be framed several ways. For newsletters, three angles cover almost every case. Pick one per email and commit to it.
The spotlight
Lead with the guest or the main topic: who they are, why they are worth listening to, and the one thing they said that made the episode. This suits interview shows and guests with a strong name.
Subject: [Guest] on [the topic, in plain words]
Preview: [What they did that makes them worth hearing]
[One line on who the guest is and why you asked them on.]
[The single best thing they said, quoted or close to it.]
[Two or three short paragraphs on why it matters
to your reader.]
[One link: Listen to the conversation]
The curiosity
Lead with the most surprising point in the episode, and hold back just enough that the reader wants the rest. This is the angle that usually gets the most opens, and the one most easily overdone. The surprise has to be real and it has to pay off in the email itself.
Subject: [A surprising claim or a real question]
Preview: [Half a step further, without giving it all away]
[Open with the claim, stated plainly.]
[Why it runs against common sense.]
[What the guest, or you, actually meant by it.]
[One link: Hear the full argument]
The value
Lead with what the reader will learn: two or three concrete takeaways they can use without listening. This suits educational shows and newer subscribers, who do not yet know why they should care about your guests.
Subject: [Number] [things] from [topic or guest]
Preview: [The most useful one, in a few words]
[One line on the problem these solve.]
1. [Takeaway, one or two sentences]
2. [Takeaway]
3. [Takeaway]
[The one we went deepest on, and where in the episode.]
[One link: Listen to the episode]
The anatomy of an episode newsletter
Whichever angle you pick, the parts are the same:
| Part | Length | Job |
|---|---|---|
| Subject line | 40 to 60 characters | Say what the email is about, specifically enough to earn the open |
| Preview text | 40 to 90 characters | Add to the subject line, never repeat it |
| Opening line | One sentence | Deliver something immediately |
| Body | 200 to 300 words | One idea, short paragraphs of two or three sentences |
| Call to action | 2 to 5 words, once | Send them to the episode |
A few reasons behind those numbers:
- Subject lines get cut off on phones. Somewhere around the 40 to 60 character mark, most inboxes truncate. Put the important words first.
- Preview text is free space. If you leave it empty, the inbox fills it with whatever comes first in the email, which is often "View in browser". Write it on purpose.
- Short bodies get read. People scan emails. Two or three hundred words is enough for one idea and short enough to finish.
- One link, not five. Every extra link splits attention. The episode is the point, so make it the only thing to click, apart from replying.
Writing it from the transcript
Here is the process I would follow by hand:
- Read the transcript, not your memory of the episode. You will remember the moments that felt good while recording. The transcript shows you the moments that read well.
- Pick the one idea. Which single point would you most want a subscriber to walk away with, even if they never listen? That is the email.
- Choose the angle. A big-name guest suggests spotlight. A counterintuitive point suggests curiosity. A practical episode suggests value.
- Pull the exact words. Quote the line that carries the idea. Your guest's real phrasing is more convincing than your paraphrase.
- Write the body in your own voice. Write as if you were emailing one subscriber you know. "You", not "our listeners".
- Write three subject lines, then pick one. The first one you write is rarely the best. If your email tool supports it, test two.
- Write the preview text last, once you know what the subject line promises.
- Cut. Remove every sentence that restates something already said. Most first drafts lose a third on this pass.
Subject lines from one episode
To make the angles concrete, here is how the three might play out for a real public episode: Lenny's Podcast with Elena Verna, on how Lovable reached $200M ARR in a year. These are examples of the shape, not a guarantee of opens.
- Spotlight: "Elena Verna on how Lovable grew to $200M ARR"
- Curiosity: "Why she spends only 5% of her growth time optimizing"
- Value: "Word of mouth, and the one way to earn it"
Each one is specific, fits on a phone and promises something the email can deliver. Compare them with "Episode 214 is live!", which tells the reader nothing about why they should care.
Newsletter, show notes and blog article: three different jobs
These three get confused, and they should not be the same text.
- Show notes are for people deciding whether to listen: a summary, chapters with timestamps, takeaways, links. They live on the episode page and help it get found in search. Our show notes generator page shows a full set.
- The newsletter is for people who already follow you: one idea, in your voice, with one link.
- The blog article is for people who will never press play: the main argument, written to be read, with headings.
Pasting your show notes into an email is the most common shortcut, and the reason so many podcast newsletters go unread.
When to send it, and how to grow the list
Timing: send it the day the episode comes out, or the day after. The point of the email is to be the first place your subscribers hear the idea. Then keep a steady rhythm. For a weekly show, a weekly email is the obvious fit.
Growing the list from the show:
- Mention the newsletter on the episode itself, near the end, with one reason to sign up.
- Offer something small that ties to the episode's topic: a checklist, a template, the framework written out. Link it in the show notes.
- Put the sign-up link in your show notes and in the first comment of your social posts.
- Every so often, write a post that is just one of your best newsletter emails. It shows people what they would get.
Mistakes that get podcast newsletters ignored
- Announcing instead of delivering. "This week's episode is live" gives the reader nothing to keep. Lead with the idea; the episode is the follow-up.
- Covering the whole episode. Five topics in 300 words means none of them land. Pick one and let the episode hold the rest.
- A subject line that is the episode title. Episode titles are written for podcast apps and search. Subject lines are written for one person deciding in a second whether to open.
- Too many links. Episode, YouTube, Spotify, Apple, the guest's site, your socials, a sponsor. One link to the episode, and the reply button, is enough.
- Writing as "we" to "our listeners". A newsletter lands best when it reads like one person writing to another. Write to one reader.
- Sending only when you remember. An irregular newsletter trains people to stop expecting it. Tie it to the episode schedule so it goes out every time without a decision.
- Never asking for replies. A single question at the end ("What would you have asked her?") turns a broadcast into a conversation, and replies tell you which ideas to follow up on.
What PodRescale does for the newsletter
PodRescale's newsletter agent writes three versions of the email for every episode, one for each angle above: spotlight, curiosity and value. Each comes with a subject line, preview text, a body of a couple of hundred words and a short call to action, built only from what was said on the episode and written in a tone learned from your own writing. You pick the one that suits the episode, edit it if you like, and paste it into whatever email platform you already use. It does not send the email for you.
The newsletter arrives with the rest of the pack: LinkedIn posts, X posts and a thread, captioned clips, quote cards, show notes, chapters and a blog article, about 30 pieces, ready in about 30 minutes for an hour-long episode. See how it works for the whole pipeline. If your recordings are webinars rather than episodes, the webinar repurposing page shows the follow-up email and everything else one recording becomes.
The first episode is free with no card, and pricing starts at $29 a month on yearly billing.
Frequently asked questions
Should I send a newsletter for every podcast episode?
Yes, if you publish on a schedule your list can keep up with. For a weekly show, one email per episode is a natural rhythm. If you publish several times a week, send a weekly email built around the best idea of the week.
How long should a podcast newsletter be?
Around 200 to 300 words for the body. That is enough to deliver one idea properly and short enough that people finish it. If you have more to say, that is a blog article.
Should I include the full show notes in the newsletter?
No. Link to them. Show notes are for people deciding whether to listen. The newsletter should give your subscribers one idea worth having, even if they never press play.
What makes a good podcast newsletter subject line?
It names the idea, not the episode number. Keep it between 40 and 60 characters with the important words first, and pair it with preview text that adds something new. Write three and pick the best.
Can I automate my podcast newsletter?
You can automate the writing. PodRescale drafts three versions from every episode for you to choose from. Sending stays in your own email platform, which is where your list and your sender reputation live.
Founder of PodRescale and a PhD in Data Science. Questions about this post go straight to him.
Follow on LinkedIn[email protected]