Subtitles fall out of sync in one of three ways, and each has a different fix. If every line is early or late by the same amount, shift the whole file. If the gap grows as the video plays, the file was timed for a different frame rate and needs rescaling, not shifting. If it is fine and then suddenly wrong, it was made for a different cut of the video, and no single adjustment will fix it. Check three points in the video before you change anything.
Almost every bad fix starts the same way: someone drags a delay slider until the first line looks right, then finds the last one is still wrong.
Pick one spoken line near the start, one in the middle and one near the end. For each, note when the person actually starts speaking and when the subtitle appears. You only need the difference, roughly: "subtitle 2 seconds late", "half a second early". Then compare the three numbers.
| What the three readings show | What it means | The fix |
|---|---|---|
| The same offset at all three | A constant delay: the file and the video start at different points | Shift every line by that amount |
| A small offset that grows steadily | Drift: the file was timed against a different frame rate | Rescale the times by the ratio of the two rates |
| Right, then suddenly wrong, then a different offset | A different edit: scenes added, cut or moved | Fix section by section, or make new subtitles from this video |
| Mostly right, a few lines early or late | Loose timing on individual lines, typical of rough auto-captions | Retime those lines by hand |
Before you edit the file at all, rule out playback. Bluetooth headphones and speakers commonly deliver sound 150–300 ms after the picture, which makes perfectly timed subtitles look early against the voice you hear. If the offset is a few hundred milliseconds and disappears on the laptop's own speakers, the file is fine and nothing needs fixing.
The most common case, and the only one a player's subtitle-delay control actually fixes.
A constant offset means the subtitles were timed against a version of the video that starts at a different point: a release with a studio logo or a cold open the other one lacks, a recording trimmed at the front after the captions were made, or a clip exported from a longer timeline. Every timestamp is wrong by exactly the length of whatever was added or removed.
Most video players have a subtitle-delay setting, and for watching something once that is enough. It does not change the file, though, so the next player, the next upload and the next person get the same wrong timing. To fix the file itself:
The slider stops at three seconds. For a bigger offset, ffmpeg can rewrite the times
without suubbs: -itsoffset shifts everything read from the file that follows
it, so
ffmpeg -itsoffset 4.5 -i subtitles.srt -c copy shifted.srt
moves every line 4.5 seconds later, and a negative number moves them earlier. Open the result and check the first cue landed where you expected before you rely on it.
No amount of shifting fixes drift. Line up the start and the end goes wrong; line up the end and the start does.
Drift happens when the subtitles were timed against a version of the video that plays at a slightly different speed. The classic case is film: a 23.976 fps release and a 25 fps European TV release of the same programme run at different speeds, because the 25 fps version was simply played about 4% faster. A file timed against one is wrong on the other by an amount that grows with every minute.
| Timed for → played against | Speed difference | Error after 1 minute | After 45 minutes |
|---|---|---|---|
| 25 ↔ 23.976 fps | about 4.3% | about 2.6 s | almost 2 minutes |
| 25 ↔ 24 fps | about 4.2% | about 2.5 s | almost 2 minutes |
| 24 ↔ 23.976 fps | 0.1% | about 60 ms | about 2.7 s |
| 30 ↔ 29.97 fps | 0.1% | about 60 ms | about 2.7 s |
The 0.1% cases are the sneaky ones. Sixty milliseconds a minute is invisible for the first ten minutes and obvious by the end of an hour. It is also what happens in an editor: a 24 fps clip placed on a 23.976 timeline is played a thousandth slow, so a subtitle file timed to the clip lands correctly at the start and slips about a frame and a half late for every minute after.
The fix is to multiply every timestamp by the ratio of the two rates. suubbs does this at export. In Timing & layout, set Frame rate to the rate the subtitles were timed for, and Deliver onto a timeline running at to the rate of the video or timeline they need to match. Every exported time is scaled by the ratio, and the note under the setting tells you how many milliseconds a minute that corrects. Two things to know:
Drift and an offset can come together. Fix the drift first: export the rescaled file, set both frame-rate settings back to the video's own, re-import the export and then shift it. In suubbs the sync slider changes the times straight away while the rescaling only happens at export, so a shift made before exporting gets rescaled along with everything else.
A file made for another edit of the video. There is no single number that fixes it.
When the offset jumps at a particular point, a scene was added, removed or moved between the version the subtitles came from and the one you have. Extended editions, broadcast versions with the ad breaks cut out, and a client's re-edit of their own video all do this. Each section between two jumps has its own constant offset.
You can fix it by hand: find each jump, and shift the lines after it. suubbs' sync slider moves the whole file at once, so for a section-by-section repair the tools are the per-line ones in the next section, which gets tedious past a handful of jumps.
Often the faster fix is not to repair the file at all, but to make a new one from the video you actually have. Subtitles transcribed from a video's own audio cannot be timed for a different cut or a different frame rate, because there is only one source of timing. suubbs transcribes on your Mac and gives every word its own timestamp: the free browser version does the first 60 seconds of any file, and the Mac app does the whole thing, however long, without uploading it. If the old file was a translation or had hand-checked spelling you want to keep, that is the case for repairing instead.
The file is broadly right and some lines are not. This is retiming, not syncing.
Rough automatic captions often have lines that appear before anyone speaks or hang on after the speaker has stopped. In suubbs, select the line and fix its edges against the picture:
[, or where it
should end and press ]. With frame snapping on, the edge lands on a
real frame.1:02:03.500, 2:03.5 or plain seconds.A line that covers two sentences can be split at the playhead with S, and
two fragments merged with M.
Retime words from audio, in the same sheet, is for a different problem. It re-snaps the boundaries between words onto real pauses in the waveform, moving each by at most about 0.12 seconds, and keeps each line's own start and end. That matters for a word-by-word highlight, and it works on an imported SRT, whose word timings are otherwise only spread evenly across each line. It will not pull a line that is two seconds late back into place.
Worth knowing before you send the fixed file anywhere.
When you import an SRT or VTT, suubbs reads each cue's start, end and text. Cue numbers are dropped and rewritten on export. Each imported cue is treated as a line you wrote: its text and timing are kept as they are, and Re-split lines leaves it alone, so a layout change cannot rearrange somebody's careful subtitles. One thing does change. A cue that was on two lines in the original arrives joined into one, and exports that way. To put the break back, Alt-click the word that should start the second line.
Two settings affect the exported times. Snap cue edges to frames is on by default and moves every edge to the nearest frame of the video, which is what an editor wants and moves each time by at most half a frame. Turn it off if you need the original milliseconds kept. And in the free browser version, exports include only the lines that start in the first 60 seconds, the same limit as its transcription; the Mac app, $9.99 once, has no limit.
Including the ones a delay slider cannot answer.
Usually because they were timed against a different version of the video: one that starts at a different point (a constant offset), runs at a different frame rate (drift that grows over time), or has scenes added or cut (jumps). Bluetooth audio delay can also make correct subtitles look early.
Measure the offset near the start, in the middle and near the end. If all three match, it is a delay and you shift the file. If the offset grows steadily, it is drift from a frame-rate mismatch and you rescale the times instead.
A delay setting only shifts. It fixes a constant offset, but drift and a different cut need the times rescaled or changed section by section. It also changes nothing in the file, so the next player gets the same problem.
Not with the sync slider, which goes three seconds either way. For a bigger constant offset, ffmpeg -itsoffset 4.5 -i subtitles.srt -c copy shifted.srt rewrites every time, or transcribe the video again so the timing comes from its own audio.
Its timings and text are kept, and Re-split lines leaves imported lines alone. A cue that was on two lines arrives as one, so Alt-click a word to put a line break back. Cue edges are snapped to the nearest frame on export unless you turn that setting off.
Often, when the old file came from a different cut. Subtitles transcribed from your video's own audio cannot be off by a cut or a frame rate. suubbs does it on your Mac without uploading the video; the free browser version covers the first minute.
[subtitles · back · in · sync]