Subtitle 2-Frame Gap Calculator

Why subtitles need a minimum gap

Every subtitle event has a start and an end, and when one event ends and another begins a moment later, that boundary has to survive both the decoder and the eye. Two problems show up when the gap between events is too small.

The first is perceptual: a single-frame gap — the caption disappearing for one frame and reappearing a frame later — reads on playback as a flicker, not a clean cut. The eye is very good at detecting a one-frame interruption in an otherwise continuous element of the frame, and it registers as a glitch rather than an intentional edit. The second is technical: a zero-frame butt (event B's in-point exactly equal to event A's out-point, or worse, overlapping it) can collide with encoder GOP boundaries, container cue-list ordering, and player cue-handling logic that assumes cues don't share a timestamp. Some players silently drop or merge coincident cues; others render both for one frame, causing a visible double-flash. This is why the Netflix Timed Text Style Guide — the de facto reference most professional QC houses check against — requires a minimum 2-frame gap between consecutive subtitle events, and why post houses generally treat it as a hard delivery requirement, not a style suggestion.

The chain-at-exactly-2 convention

The 2-frame minimum is a floor, but professional practice goes one step further for a specific case: when two subtitles are meant to read as continuous dialogue with no real pause — one speaker's line ending as the next line's should appear — editors don't leave "2 or a few more" frames, they chain them at exactly 2 frames. That precision matters because irregular small gaps in the 3–5 frame range look like flashing: the eye can tell the difference between a deliberate, consistent 2-frame cut and a slightly-longer-but-still-tiny gap that just looks like an error. A gap of 2 frames disappears into the cut; a gap of 4 frames draws attention to itself.

This tool's verdict tiers encode that distinction directly, not as a single pass/fail line:

• Overlap (gap < 0): B starts before A ends — a hard error, not a QC judgment call.
• Fail (0–1 frames): below the Netflix minimum; will likely read as a flicker or trip a delivery QC report.
• Pass — chained (exactly 2 frames): the ideal continuous-subtitle spacing.
• Pass with note (3–11 frames): technically legal, but in the range that can read as an unintentional flash — either chain it at exactly 2 frames or open it up.
• Pass — distinct events (≥12 frames, roughly half a second at 24 fps): comfortably separated; reads as two unrelated events.

Worked example, 25 fps: event A ends at 00:00:04:10, event B starts at 00:00:04:12. That's a difference of 2 frames — at 25 fps, each frame is exactly 40.00 ms, so the gap is 2 × 40.00 = 80.00 ms. Because the gap lands on exactly 2 frames, this is the chained-ideal case: tight enough to read as continuous dialogue, wide enough to clear the decoder and avoid a flicker.

Shot changes

When a subtitle boundary sits close to a hard cut, the convention is to let the subtitle change land on the cut, not a few frames before or after it — a subtitle that straddles a cut by 3–6 frames draws the eye to the mismatch between the audio/picture edit and the caption edit. If a caption boundary can't be moved onto the cut exactly, the 2-frame chain (rather than a small arbitrary gap) is the safer choice, because a clean 2-frame cut reads as intentional even off the shot change, where an irregular small gap reads as a timing bug.

Ms-per-frame reference

Because professional frame rates aren't all whole numbers, the millisecond value of "2 frames" changes by rate. NTSC-family rates (23.976, 29.97, 59.94) use the exact 1001-based ratios (24000/1001, 30000/1001, 60000/1001), not rounded decimals — rounding to 23.98 or 29.97-as-a-decimal introduces drift over a long timeline. The reference table above this section gives the exact ms-per-frame and 2-frame-gap values for every standard rate from 23.976 through 60 fps, so you can sanity-check a gap by eye before pulling out a calculator.

1. Enter event A's out timecode and event B's in timecode, in SRT or SMPTE form.

2. Pick the frame rate — the gap comes back in both frames and milliseconds on a mini-timeline.

3. Check the verdict against the 2-frame minimum, and convert the timings for 29.97 with the DF/NDF subtitle converter.