Why subtitle timestamps drift
Updated 16 November 2026
There are two very different problems people describe with the same words. If the subtitles are wrong from the first second, that is an offset. If they start correct and get worse, that is drift. They have different causes and need different fixes, and mixing them up wastes a lot of time.
First, decide which one you have
Watch the first thirty seconds and the last thirty seconds.
- Wrong immediately and stays equally wrong → constant offset. Something is shifted by a fixed amount.
- Right at the start, worse at the end → drift. The rate is wrong, not the starting point.
- Right, then suddenly wrong → the video and the subtitle are describing different edits.
That single check rules out most of the possibilities below before you touch anything.
Cause one: the frame rate was wrong at conversion
This is the classic source of drift, and it only applies to formats that count frames — MicroDVD, and ASS/SSA when they use frame-based timing. Convert a 23.976 fps film's subtitle at 25 fps and every cue is compressed by about 4%. A cue at one minute lands two seconds early; a cue at ten minutes lands twenty-four seconds early.
The signature is unmistakable: a uniform percentage error that grows with time. Fix it by converting again with the correct rate. If you have the video, read its actual frame rate rather than guessing — see the MicroDVD converter for the frame-rate handling.
Cause two: 23.976 is not 24 (and 29.97 is not 30)
NTSC video runs at 23.976 fps rather than 24 — a deliberate 0.1% slowdown introduced when colour television was standardised. Over a two-hour film that difference is about seven seconds.
So a subtitle made for a 24 fps release, played against a 23.976 fps copy, will not just be "slightly off". It will start nearly correct and end seven seconds late. Most people never notice this because seven seconds over two hours feels like the player's fault.
Practical consequence: when a file offers both 24 and 23.976, they are not interchangeable, and picking the wrong one produces exactly the drift pattern above at a much smaller scale.
Cause three: the video is a different cut
Subtitles follow the video they were made for. Add a distributor logo, cut a scene for broadcast, or replace the opening credits, and every subtitle after the change is shifted — usually once, by a large amount, not gradually.
The signature: correct, then suddenly wrong at a specific moment. If you can find that moment, the fix is to shift everything after it by the difference. Subtitle editors do this with a "shift from here" function; doing it by hand means editing every timestamp.
Streaming versions are the worst offenders, because they add front matter that the subtitle was never timed against.
Cause four: the tool resampled or rounded
Rarer, but real. Some converters round timestamps to whole seconds, which compounds across a long file. Others treat millisecond separators loosely — a file that mixes commas and periods can be parsed inconsistently, producing cues that are right in one region and wrong in another.
The signature: small, irregular errors that do not fit a percentage and do not start at a clean cut point. The fix is to convert with a tool that preserves milliseconds exactly rather than one that rounds.
What does not cause drift
File size or length. A subtitle file does not degrade with length; the timings are stored per cue.
Player settings. Some players let you nudge subtitle delay, but that shifts everything by a constant — it cannot create drift. If you find yourself adjusting delay repeatedly through a film, the file has drift and a delay setting will never fix it.
Which tool exported it. As long as the milliseconds survived, the exporter does not matter.
The order to check things
- Compare the first and last cue. Offset or drift?
- If drift: what format was this converted from, and at what frame rate?
- If offset: is the video a different edit — different intro, different credits?
- Only then: is the video's real frame rate 23.976 when you assumed 24?
Most drift is a frame rate that was assumed rather than read, and most offsets are a different cut. Neither is fixed by nudging the delay slider.