Turn One Podcast SRT into Subtitles for Every Clip

One episode, twenty approved selects

A podcast episode ships once as audio and then lives on as clips: the opener for Shorts, a heated exchange for Reels, a quotable minute for TikTok. The transcript exists exactly once, timed against the full episode — but every published clip needs its own subtitle file that starts at its own 00:00. Copying captions per select, subtracting the select start by hand and renumbering is the same error-prone loop as any multi-clip delivery, repeated on every episode.

What is a clip-relative subtitle file? A clip-relative subtitle file is a subtitle file whose cue timings start at 00:00:00,000 — the first frame of a single video clip — instead of the full-length source video's timeline. Read what a clip-relative subtitle file is for the full definition and the maths.

The podcast clip workflow

1. Export one SRT for the whole episode. Keep it untouched — it stays the single source of truth for every select.
2. List the approved selects in a CSV. Three columns: name,start,end. Name rows after the working titles the team already uses, so the output files need no renaming.
3. Run the batch splitter. Every row is validated with its row number; captions that cross a select boundary are trimmed or excluded per clip.
4. Deliver the ZIP. One SRT and TXT per select under srt/ and txt/, plus a manifest that records range, caption count and policy.

Try it with the example master SRT and example clip CSV on the batch SRT splitter — no sign-up needed to load and review them.

Selects change; the transcript does not

Social selects are editorial decisions, and they get revised: a hook moves 4 seconds, one select is dropped, a new quotable moment is added after publish. Because the selects live in the CSV and the transcript is never modified, a revision is a row edit and a re-run. The master SRT guide walks through that loop end to end.

Podcast clip subtitles FAQ

Related tools and guides