Create an SRT File — Three Steps, Validated
Never made an SRT before? Three guided steps — first cue, keep chaining, download. With live validation throughout.
Quick answer: Step 1: add your first cue (start, end, text). Step 2: keep adding cues — each start can copy the previous end so the file chains naturally. Step 3: download the finished .srt. Validation runs on every row.
- Step 1. Fill the first cue: start, end, text.
- Step 2. Add more cues — “chain” copies the previous end as your next start.
- Step 3. Download the .srt when every warning is gone.
| Step 1 | First cue: start time, end time, text |
|---|---|
| Step 2 | Chain cues; “end = next start” keeps timing continuous |
| Step 3 | Download a standard .srt |
| Guardrails | Overlap and reading-speed warnings as you type |
| No account | Nothing to sign up for; nothing uploaded |
What this tool does
An SRT file is simpler than its reputation: numbered blocks of “start --> end” plus text. This page walks you through making one for the first time — first cue in three fields, then a run of cues where each new start can inherit the previous end so your captions chain continuously, with plain-English warnings the moment an overlap or a too-fast line appears. The guided mode exists because most mistakes in hand-made subtitles are ordering mistakes, and they are cheapest to prevent at entry time. The result is a standard SRT ready for YouTube, Premiere, VLC or any player.
Common uses
- First-time captioning: a short video, a handful of lines
- Quick title cards over b-roll footage
- Learning how SRT works by building one
Chaining cues back-to-back
Professional subtitlers time cues as a chain: each cue ends exactly where the next begins, so text streams continuously instead of blinking out between lines. The guided editor supports this directly — one button copies a row's end time into the next row's start. For conversational pacing, add a small deliberate gap instead; both patterns are common, only unvalidated overlaps are wrong.