Back to Blog
Guides & TutorialsNovember 16, 20269 min read

Subtitles Out of Sync? It's One of Three Problems, and Only One Is Easy

Out-of-sync subtitles come from a fixed delay, a frame-rate drift, or a different cut of the video. How to tell which one you have, and the fix for each.

Subtitle SyncSubtitle DelaySRTVTTFrame RateFFmpegVLCSubtitles

People describe out-of-sync subtitles the same way every time: they're a couple of seconds off. That one description covers three different faults. The subtitle file can be early or late by a fixed amount. It can run at a slightly different speed from your video. Or it can belong to a different cut of the video altogether.

The fix for one does nothing for the other two, which is how you end up nudging the delay in your player until the first scene looks right, only to find it wrong again twenty minutes in. Working out which fault you have takes about two minutes, and it's worth doing before you change anything.

#Check two points before you touch anything

Load the subtitles and find a line of dialogue in the first couple of minutes. Note how far off it is, and in which direction. Then jump to somewhere near the end and do the same. Those two measurements are enough to tell the three cases apart.

What you seeWhat it isWhat fixes it
The gap is the same at the start and at the endA constant offsetShifting every timestamp by one number
The gap is small at the start and keeps growingDrift, from a speed or frame-rate mismatchStretching or squeezing the whole timeline
In sync for a while, then suddenly off (or the reverse)Subtitles made for a different cutRe-timing section by section, or a file made for your version

To measure the gap properly, choose a line that starts cleanly after a pause. Pause the video on the moment the first word is spoken and read the clock. Then open the subtitle file in a text editor (it's plain text) and look up the same line:

214
00:12:38,500 --> 00:12:41,200
I told you not to open that door.

If that line is spoken at 12:41.0 in your video, the file is 2.5 seconds early, and every cue needs to move 2.5 seconds later. Write the number down with its direction. You'll need both.

#A constant offset is the easy one

The same gap at the start and at the end means the two timelines run at the same speed and one of them is displaced. It's the fault you're most likely to have, and the only one a plain shift can fix. The usual cause is a different opening: a studio logo, a recap, or a few seconds of black that one version has and the other doesn't. You also get it when you trim the start of your own video and keep using the old subtitle file.

#Find the number in your player

A media player is the quickest way to find the right offset, because you can nudge it and watch. In VLC on Windows and Linux, the G and H keys move the subtitle delay down and up in 50 millisecond steps, and the current value shows on screen as you press. Tools > Track Synchronization lets you type an exact figure. On a Mac the keys are H and J. VLC also has a shortcut for subtitles that are running late: press Shift+H when you hear a line, Shift+J when its subtitle appears, and Shift+K to apply the difference.

In mpv, z and Z change the delay by a tenth of a second. Ctrl+Shift+Left and Ctrl+Shift+Right are more useful: they set the delay so that the previous or next subtitle is showing right now, so you can wait for a line to be spoken and press the key.

None of that is saved. Close the video and the delay is gone, and it never applied to your phone, your TV, or anyone you send the file to. Once you know the number, write it into the subtitle file.

#Write the offset into the file

Our Subtitle Shifter does this in the browser. Drop in an .srt or .vtt file, type the offset in seconds (positive makes the subtitles appear later, negative earlier, and decimals are fine), press Shift Timestamps and download the result. The page reads the file itself and nothing is uploaded. A subtitle file is a few kilobytes of text, and adding a number to each timestamp isn't a job that needs a server. If you're not sure which of the two formats you have or need, this comparison of SRT, VTT and TXT will sort that out.

One detail matters when you shift earlier. If the offset is larger than the start time of the first cue, that cue would land before zero. The shifter pins those timestamps at 00:00:00,000 and moves every other cue by exactly the amount you asked for.

If you'd rather stay on the command line, ffmpeg does the same job:

ffmpeg -itsoffset 2.5 -i subs.srt -c copy subs_shifted.srt

Positive values behave as you'd expect. Negative ones have a trap. We ran it with -itsoffset -2 on a file whose first cue started at 1.2 seconds, using ffmpeg 8.0. It didn't clip that first cue. It slid the whole file so the first cue began at zero, which moved every line by 1.2 seconds when we'd asked for 2. Nothing in the output warns you about it. If you shift earlier with ffmpeg, compare a cue from the middle of the result against the original.

If the offset is there because you cut the start off the video, the number should be the length you removed. Check it against the trimmed file anyway. Tools that trim without re-encoding (our trim tool is one) can only begin a cut on a keyframe, so the real starting point may sit a little earlier than the time you typed.

#Drift: fine at the start, worse every minute

If the gap grows as the video plays, the subtitles were timed against a version that runs at a different speed. Frame rate is nearly always the reason. Films are shot at 24 frames per second. For broadcast in PAL countries they were traditionally played at 25, about 4% fast, which takes nearly five minutes off a two-hour film. Subtitles timed to that faster version are compressed by the same 4%, and no offset will make them fit the original.

SRT and VTT store times, not frame numbers, so nothing in the file says what it was timed for. The size of the drift tells you:

Subtitles were timed forYour video runs atMultiply every time byGap after one hour
25 fps23.976 fps1.04272 min 34 s, subtitles early
23.976 fps25 fps0.95902 min 27 s, subtitles late
24 fps23.976 fps1.00103.6 s, subtitles early
23.976 fps24 fps0.99903.6 s, subtitles late

The two pairs in that table look very different when you're watching. A 25 against 23.976 mismatch is more than two seconds out after the first minute, so you spot it immediately. A 24 against 23.976 mismatch gains only 3.6 seconds an hour. The opening scenes look perfect and the last act of a two-hour film is seven seconds out, which is why this one so often gets treated as a simple delay.

#Work out the stretch from two lines

If your drift doesn't match the table, or you'd rather measure than guess, take one line near the start and one near the end. For each, note the time in the file and the time it's spoken.

Early line:  file 00:02:00.000   spoken 00:02:06.625
Late line:   file 01:30:00.000   spoken 01:33:52.125

stretch = spoken gap / file gap
        = 5505.5 s / 5280 s
        = 1.0427

offset  = first spoken time - stretch x first file time
        = 126.625 - 1.0427 x 120
        = 1.5 s

new time = old time x 1.0427 + 1.5

A stretch of 1.0427 is the first row of the table, with a 1.5 second offset on top. That pairing is common, because a version with a different frame rate often has a different opening too. Apply the stretch first and the offset second.

#Tools that can stretch a timeline

Our shifter can't do this. It adds the same number to every timestamp, and for drift that's the wrong operation: get the opening scene right and the ending is still minutes out. Two free tools handle it well.

  • Subtitle Edit keeps everything under its Synchronization menu. Change frame rate converts between two known rates. Point sync and Visual sync ask you to match one early line and one late line, then work out the stretch and offset for you. It's the calculation above, done against a video preview.
  • ffsubsync is a command-line tool that detects where speech occurs in the audio and lines the subtitle file up against it. It tries the common frame-rate ratios by default. The basic command is: ffs video.mp4 -i subs.srt -o subs_synced.srt

#A different cut: right, then suddenly wrong

The third case is the awkward one. The subtitles hold for a stretch and then jump out, sometimes more than once. Your video and the subtitle file disagree about what the video contains: one of them has an extra scene, a recap, an ad break that was removed, or a longer edit of some sequence. Every cue after that point is displaced by the length of the difference.

A quick test is to compare your video's running time with the last timestamp in the subtitle file. If the final line of dialogue is listed four minutes after your video ends, the subtitles were made for a longer version.

No single shift or stretch repairs this, because the error changes wherever the cuts differ. You can split the file at each jump and shift the sections separately, which is tedious but manageable for one or two breaks. ffsubsync has an experimental --split-penalty mode that attempts the same thing automatically. Often the better use of your time is to find subtitles made for your exact release, or to stop repairing and make new ones.

#When it's quicker to start over

If the subtitles are in the language being spoken, you don't need the old file's timings at all. Speech recognition will build a new subtitle file from the audio of the exact video you have, so there's nothing to offset and nothing to drift. Our transcription tool does this for free in the browser and exports SRT and VTT. There's a trade-off you should know about: the free mode runs a small Whisper model on your own device. It handles clear speech well and struggles more with strong accents, people talking over each other, or music. The Pro mode uses a much larger model on our servers.

If you plan to burn the captions into the video anyway, there's a shortcut for when the words are right and only the timing is wrong. Save the text as a plain .txt file with no timestamps and upload it alongside the video in the subtitle generator. It listens to the audio, works out when each word is spoken, and attaches those times to your wording. Upload the broken .srt instead and its timestamps are used exactly as written, sync problem included.

None of this helps when the subtitles are a translation. Recognition returns the words that were spoken, in the language they were spoken in. A Korean film with English subtitles still needs its English file repaired by one of the methods above.

#Check again before you burn anything in

A separate subtitle file can be corrected as many times as you like. Burned-in captions can't. Once the text is part of the picture, a sync error is permanent and the only fix is to render the video again. Before hardcoding subtitles from an existing file, play the first minute and the last minute with that file loaded. It's quicker than a second render.

#The short version

  • Measure the gap near the start and near the end before changing anything.
  • Same gap in both places: shift the file by that amount.
  • Gap that grows steadily: it's a speed mismatch. Stretch the timeline with Subtitle Edit or ffsubsync, because a shift won't hold.
  • Gap that changes in jumps: the file is for a different cut. Find the right file, or generate new subtitles from the audio.
  • Player delay controls are for finding the number. They don't fix the file.