Skip to content
Guide

Podcast Intro Script Examples and a Reusable Template

Copy four original podcast intro script examples for solo, interview, co-host, and serial shows. Download a template and write a clear episode opening.

Murmur9 min read

Choose a podcast intro script that tells the listener which show they have opened and what this episode will give them. Use a specific problem, question, conversation, or story moment, then move into the content. The examples below are for solo creators, interview hosts, co-hosts, and serialized storytellers writing episode openings, rather than a standalone show trailer.

All show names, hosts, guests, stories, and situations are fictional. These are original scripts you can copy and adapt, with notes explaining their different jobs. They are not excerpts from real podcasts or evidence of listener retention. Download the plain-text podcast intro script pack for the examples and a blank episode-opening template.

Separate the show identity from the episode setup

PartJobUpdate when
Episode openingGive a specific reason to listen todayEvery episode
Show identityName the show and its subjectThe show positioning changes
Host or guest contextExplain who is speaking and why they matter hereThe speaker or relevant role changes
TransitionStart the first question, lesson, or sceneThe opening content changes

Write the changing part before reusing the fixed part. A recurring identity line may work across a season, but a generic “we have an exciting episode” gives little information. Look at the edited episode and choose the question it actually answers. If the interview becomes a discussion about workshop scheduling, do not keep a draft introduction promising a tutorial about repairing chairs.

Apple Podcasts' presentation guidance recommends matching the show's vocabulary, energy, and personality in its writing. Apply that idea to the opening: a quiet interview does not need an announcer shouting about an unmissable conversation. Consistency can come from recognizable phrasing and subject matter without requiring an identical paragraph at the start of every file.

Four podcast intro script examples with different jobs

Solo practical episode

One folder, six files called final. How do you know which one to send? This is Desk Notes, a podcast about the small decisions behind creative work. I'm Lena Ortiz. Today we'll build a simple file handoff: a name, a version, and a note that tells the next person what changed. Let's start with the filename.

Original fictional podcast intro

The opening names a recognizable problem and a specific lesson. The show identity can remain in later episodes; the file-handoff setup should change with the topic. Do not promise a complete system for every creative workflow when the episode teaches only a small habit. The last sentence is a usable transition into the first segment.

Interview with a relevant guest

When a repair bench fills up, which job gets attention first? On Bench Talk, we ask makers how they decide. I'm Noor Patel. Today, workshop owner Eren Shaw joins me to walk through a crowded Monday, from the first customer message to the last job on the bench. Eren, what do you check before picking up a tool?

Original fictional podcast intro

This introduction gives the fictional guest a relevant role and moves directly into a question. Replace the role with a verified description approved by your actual guest. A long biography can wait until it becomes useful in the conversation. If the guest changes the topic during recording, update the introduction to match the finished interview rather than the original booking.

Two co-hosts with different perspectives

MAYA: I named the folder final. SAM: I named mine final, version two. MAYA: So neither of us knows which one to send. Welcome to Two Desks. I'm Maya. SAM: And I'm Sam. Each week we compare the way a designer and an editor approach the same small problem. MAYA: Today, it's handing over unfinished work without handing over confusion. Sam, what's the first thing you need from me?

Original fictional podcast intro

The exchange demonstrates the co-host relationship instead of saying the hosts have great chemistry. Give each voice a purpose: one presents the situation, the other introduces a different need. Speaker labels help production and are not part of the spoken text. Replace the fictional professions only if that contrast actually shapes your own show.

Serial fiction with episode orientation

The parcel arrived without an address. Inside was a key, a train ticket, and a note: come back before the clock stops. This is The Last Parcel, an audio mystery. I'm your narrator, Celia. You're listening to part three, The Station Room. If you're starting here, begin with part one. Last time, Ada found the name of the person who sent the key. Tonight, she finds the room it opens.

Original fictional podcast intro

The narrative opening gives a new listener an orientation and a returning listener a specific continuation. Because the invented story is sequential, the start-at-part-one instruction has a purpose. Keep the recap limited to what this episode needs. Do not imply that fictional dialogue or a created sound clip is a documentary recording from a real event.

Script length estimates for planning

The table counts whitespace-separated spoken words in the original examples, excluding leading speaker labels. The duration column is calculated at an assumed 150 words per minute: words divided by 150, multiplied by 60. These are planning estimates, not measured performances. Pauses, music, effects, turn changes, and time needed to show an action are not included. Time the finished audio or video before using it.

Original exampleSpoken wordsEstimated speech at 150 words per minute
Solo practical episode5622.4 seconds
Interview with a relevant guest5823.2 seconds
Two co-hosts with different perspectives6425.6 seconds
Serial fiction with episode orientation7028.0 seconds

Build an intro from a blank template

[A specific question, problem, or story moment from this episode.] This is [show name], [plain description of the recurring subject]. I'm [host name]. [Optional: guest name and one verified relevant role.] Today, [what the episode actually explores or teaches]. [The first question, instruction, or scene transition.]

Blank podcast episode intro template

Fill in the opening and the transition first. These two lines show whether the intro belongs to the episode or could be pasted onto anything. Then add the minimum show context a new listener needs. Read the result without music. If the structure depends on a large sound effect to make an ordinary promise feel interesting, make the promise more specific.

  • Episode question: [what the listener wants answered].
  • Show identity: [name and ordinary-language subject].
  • Speaker context: [host; optional relevant guest role].
  • Episode promise: [what the finished recording contains].
  • First segment: [the actual first question or scene].
  • Necessary orientation: [prior episode, content note, or context when relevant].
  • Production cues: [speaker labels, pauses, sound entries, separate from spoken copy].

For an interview, the transition should be a question the guest can answer. For a lesson, it should start the first useful step. For a story, it should place the listener in the next scene. A blank template is useful because it exposes missing decisions; it should not force a narrative show to sound like a business tutorial.

Edit weak openings into a concrete promise

Weak draft: “Welcome back to another amazing episode. Today we have a very special guest and lots of great tips.” The problem is not friendliness. It is that the listener cannot tell what they will hear. Replace praise with subject matter: “How does a workshop choose the next repair when every customer wants an update? Today, Eren walks us through the morning job list.” This is an original editing example, not copy from a real show.

Avoid making the opening a table of contents for the entire episode. A list of seven segments can postpone the first useful moment. If one theme connects the segments, state that theme and begin. Save housekeeping, multiple requests to follow the show, and unrelated announcements for a place where they do not bury the reason to listen.

Do not write “you'll never believe” when you can name the actual uncertainty. “Why did the booking disappear?” gives a listener a question; “the most shocking episode yet” gives them an unsupported ranking. Similarly, do not add invented listener numbers, guest awards, or research findings. An introduction can be engaging through a precise question and an honest promise.

For a serialized show, include enough context to preserve the sequence. Apple distinguishes episodic shows from serial shows that are intended to be heard in order. That distinction helps explain why the fictional mystery includes a part-one instruction while the independent file-handoff lesson does not. Keep the opening consistent with how your real feed is organized.

Plan the audio handoff and check the finished episode

There is no universal best intro length established by these examples. Use the speech time calculator for a draft estimate, then listen to the actual opening and first segment together. A performance may add pauses; a co-host exchange includes turn changes. The useful check is whether the listener understands the show and reaches the promised content without repeated setup.

If you have a cold open, decide what happens after it. A quote followed by the full interview introduction can repeat the same point. Write a shorter bridge that adds the context the clip left out. Keep a clean spoken script and a separate cue version so labels such as MAYA or MUSIC IN are not accidentally narrated.

A standalone trailer is a different deliverable. Apple's episode guidance distinguishes full, bonus, and trailer episodes. Do not apply a trailer's broad show pitch unchanged to every ordinary episode. If your real task is producing the opening audio on a Mac, the podcast intro generation guide covers that workflow; this page supplies the copy and editing decisions.

After editing, check the beginning of the exported episode rather than only the standalone intro file. Confirm that the host and guest names are correct, the content matches the promise, and the transition is complete. The voiceover export guide explains the difference between an editing master and a delivery copy. Do not assume that a music track has permission for podcast use simply because it was easy to download.

Frequently asked questions

Sources

Prepare your podcast intro narration in Murmur

Murmur is a local voice studio for Apple Silicon Macs running macOS 15 or later. The website edition costs $49 one-time, with no free trial and a 7-day refund policy. Listen to the public samples before buying.

macOS 15+ · Apple Silicon required · 7-day refund policy