Subtitle frame rates and the 23.976 vs 25 fps problem

If your subtitles start in sync but slowly slide further and further out as the film plays, you are almost certainly looking at a frame-rate problem. It is one of the most misunderstood subtitle issues, because the obvious fix of shifting the timing does not work. This guide explains where frame rates come from, why a mismatch causes drift rather than a fixed offset, and how to correct it.

What “frame rate” means

Video is a flipbook, a sequence of still images shown fast enough to look like motion. The frame rate, measured in frames per second (fps), is how many of those stills play each second. You will only ever meet a handful of them.

• 23.976 fps is the standard for film and most modern movie releases (often written as 24p but technically 23.976).
• 24 fps is the true cinema frame rate, very close to 23.976.
• 25 fps is the PAL standard, used for broadcast and DVDs across Europe, Australia and much of Asia and Africa.
• 29.97 fps is the NTSC standard, used for broadcast in North America and Japan.

Subtitles do not store frames. They store clock time. But the video runs at a particular frame rate, and that determines how long the film actually lasts. That is where the trouble starts.

Why a mismatch causes drift, not a fixed offset

Here is the key idea. Take a film mastered at 23.976 fps. To show it on 25 fps PAL television, the simplest method is to play every frame slightly faster, 25 frames per second instead of 23.976. The film now finishes about 4% sooner. A two-hour movie ends roughly five minutes early. This is the famous PAL speed-up, and it is why the same film can have a slightly higher-pitched soundtrack on European TV.

Now imagine subtitles authored for the slower 23.976 version, played against the sped-up 25 fps copy. At the very start, both timelines agree, so the first subtitles look fine. But because the 25 fps video is running 4% faster, every spoken line arrives a little earlier than the subtitle expects, and the gap grows with every minute that passes. By the end of a two-hour film the subtitles can be minutes adrift.

That growing gap is the signature of a frame-rate mismatch. Because the error accumulates over time, no single shift can fix it. The amount you would need to shift at the start is different from the amount at the end.

Why shifting can’t fix it, but rescaling can

Shifting moves every cue by the same number of seconds. That is the right tool when the whole file is offset by a constant amount (see our guide on why subtitles go out of sync). But drift is not a constant offset. It is a proportional error. A cue at the one-hour mark is twice as far off as a cue at the thirty-minute mark.

The fix has to be proportional too. Rescaling multiplies every timestamp by the ratio between the two frame rates. Going from 25 fps to 23.976 fps, every time is multiplied by 25 ÷ 23.976 ≈ 1.0427, which stretches the subtitles back out to match the slower video. Going the other way divides by the same ratio. Because the multiplication scales with time, early cues barely move and late cues move a lot, exactly cancelling the drift.

The frame-rate converter does this calculation for you. You set the frame rate the subtitle was made for as the source and your video’s frame rate as the target. It rescales every timestamp by the correct ratio and gives you a file that stays in sync from the first line to the last.

How do I know which frame rates to choose?

There are two practical approaches.

• Check the video file. Most players and tools (VLC’s Media Information, for example) report the video’s frame rate. That is your target. The subtitle was most likely made for the other common rate in the pair.
• Use the common pairings. The overwhelmingly common mismatch is 25 ↔ 23.976 fps, because it is the PAL-versus-film difference described above. If a film drifts and you do not know the exact numbers, try that pair first. It fixes the large majority of cases.

If your subtitles drift only slightly, you are probably dealing with the 23.976-versus-24 difference, which is tiny (about 0.1%) and only matters for very long files.

A quick way to confirm it’s a frame-rate issue

Watch one minute at the start and one minute near the end.

• Subtitles roughly in sync at the start but badly off at the end means frame-rate drift. Use the converter.
• Subtitles off by the same amount at both ends means a constant offset. Just shift the file instead.

This thirty-second check stops you from rescaling a file that only needed a simple shift, or vice versa.

The bottom line

Frame rates exist because film, European TV and North American TV all settled on different standards, namely 23.976, 25 and 29.97 fps. When a subtitle made for one frame rate meets a video encoded at another, the timing error grows steadily through the film instead of staying fixed. The cure is to rescale the timing by the ratio between the two frame rates, most often the classic 25-to-23.976 conversion, so every cue lands back where it belongs.