Podcast clip: structure, script and how to clone it
Podcast clip is a proven short-video structure. Here is why it holds attention, how its beats are timed, a script you can start from, and the command that clones it for your own subject.
Why this format works
The podcast clip format borrows trust: an existing conversation already sounds credible, and a tight cut of it works as a standalone video.
Structure breakdown
1. Hook line (0–3s)
Start on the sentence that would make someone stop scrolling, not on the intro.
2. Context (3–10s)
One caption line of setup so the clip is legible without the episode.
3. Build (10–40s)
Keep the natural back-and-forth but trim every pause; speaker changes are the rhythm.
4. Landing line (last 5s)
End on the strongest sentence and cut — no outro, no “subscribe”.
A script you can start from
Segments, takes and selection anchors — this is the part of the project that changes when you re-run the format:
<script>
<segment> id="guest">
<take>Everyone says || @ship-fast ship faster. || We shipped slower || @one-thing and revenue doubled.</take>
</segment>
<caption-track document={story.caption}/>What you need
- — Transcript or episode audio
- — Speaker roles
- — A 9:16 layout that keeps two faces legible
Run it
hypit run clone --reference ./reference/podcast-clip.mp4 --script ./episode-42.svs --runThe reference video stays fixed. Change the script, re-run, and you get a new edit in the same format — that is the whole point of cloning instead of prompting.
Keep reading
FAQ
Should I cut the clip or clone the format?
If you already have the moment, cutting is fine. Cloning is for when you want a weekly clip format with the same pacing and captions regardless of the episode.
How do speaker roles help?
Lines, looks and captions are routed per role, so swapping a guest does not break the layout.
What about clip length?
30–60 seconds is the sweet spot for a single idea; longer only works when the argument has two turns.