Subtitle Guidelines: Line Length, Reading Speed and Timing
Keep subtitles to two lines of about 37–42 characters, give viewers time to read (around 15–20 characters per second), keep each cue between about one and seven seconds with a small gap between cues, and break lines at natural phrase boundaries.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Help me use a Skill with another agent. Ask which agents and package I use, check supported locations and tools, identify any assumptions to change, and verify the workflow with a small example.
Quick answer
Good subtitles are short enough to read at a glance and stay on screen long enough to finish. Use at most two lines, keep lines around 37–42 characters (shorter for vertical video), aim for 15–20 characters per second, show each cue for at least about one second and at most seven, and leave a couple of frames between cues so viewers notice the change.
Line breaks
- Break after punctuation or before a conjunction such as "and" or "that".
- Never end a line on an article or preposition such as "the", "of" or "to".
- Keep the bottom line similar in length or a little longer than the top.
- Two speakers in one cue each get a line starting with a dash.
Timing and sync
If subtitles start late and drift further out, the file was timed against a different frame rate. Correcting it needs two points: the real start time of an early line and of a late one. A single shift fixes only a constant delay.
When speech is too fast
Retiming cannot fix a line spoken faster than anyone can read. Condense it: drop filler, repetition and false starts while keeping names, numbers and meaning.
Do it with an AI agent
SubtitleForge corrects sync and drift from two anchors, splits and merges cues, gives every line time to read, snaps to frames and rebalances line breaks for streaming, broadcast, social or children's profiles, then writes SRT, WebVTT, a review page and a subtitled video.