Account

What new tool do you want?

Video & Audio

Subtitle Timing Shifter (Sync Subtitles)

Fix out-of-sync subtitles — shift every SRT or VTT timestamp earlier or later by any number of seconds, or stretch timing to fix drift.

How to use

  1. 1Paste the SRT or VTT file.
  2. 2Enter how many seconds to shift (negative = earlier). Use 'Speed factor' if subtitles drift more over time.

How it's calculated

New time = old time × factor + shift. A 23.976 → 25 fps mismatch needs a factor of 23.976 ÷ 25 = 0.959.

Frequently asked questions

Subtitles appear too early — which way do I shift?

Enter a positive number to delay them. If they appear too late, use a negative number.

They start in sync but drift apart — what now?

That's a frame-rate mismatch. Try a factor of 0.959 (subtitles made for 23.976 fps on a 25 fps video) or 1.0427 for the reverse.

Is the format kept?

Yes — SRT stays SRT and VTT stays VTT. Cues that would start before 0:00 are clamped to 0.

Two kinds of 'out of sync', two different fixes

A constant offset — subtitles that are always 2 seconds late, from the first line to the last — is a shift problem: one number added to every timestamp fixes it everywhere. Drift — subtitles that line up fine at the start but are visibly behind by the end — is a speed problem, not an offset problem, and no single shift value can fix it, because the gap between audio and subtitle keeps growing the longer the video runs. That's why this tool has two separate fields instead of one.

Where drift actually comes from

The most common cause is a frame-rate mismatch between the subtitle file and the video: subtitles timed against a 25 fps PAL edit of a film, played against the original 23.976 fps version, run about 4.1% faster than the picture. Applying a factor of 23.976 ÷ 25 = 0.959 compresses every timestamp proportionally — new time = old time × factor — so a cue near the start barely moves while one near the end shifts substantially, matching how the error itself grows over time. The reverse mismatch (23.976 timed subs on a 25 fps video) uses roughly 1.0427.

Worked example: a 90-minute film with PAL-speedup drift

Say subtitles for a 90-minute film were timed against the 25 fps PAL cut but you're watching the 23.976 fps original. At the very start they look fine, but a line timestamped at 1:30:00 (5,400,000 ms) in the subtitle file needs to land earlier in the slower-running source. Applying factor 0.959 with shift 0 moves it to 5,400,000 × 0.959 ≈ 5,178,600 ms — about 3 minutes and 21 seconds earlier — which is exactly the kind of large, compounding drift PAL/NTSC frame-rate conversions produce over a full-length feature.

Fixing a simple constant lag

For the more common case — subtitles that are consistently early by a fixed amount — only the shift field is needed. A cue at 00:00:01,000 --> 00:00:03,500 with shift +2.5 and factor 1 becomes 00:00:03,500 --> 00:00:06,000: every cue moves by exactly 2.5 seconds, format and numbering otherwise untouched, and any cue that would fall before 0:00 after a negative shift is clamped there instead of going negative.

Related tools

More: Video & Audio