Subtitle shifter & converter
All tools

Convert subtitles from 24 to 23.976 fps

Subtitles timed against a 24 fps master used with the 23.976 fps home-video release. They slowly run late, by about 3.6 seconds per hour.

…or drop it here. SRT, VTT, ASS, SSA or TXT. Files are processed on your device and never uploaded.

sample.srtLoading…

 

Rescale times when the subtitle was made for a video with a different frame rate.

Cues

     

    Save options

    Output preview

    
    

    What the conversion does

    Converting from 24 to 23.976 fps multiplies every subtitle time by 24 ÷ 23.976 = 1.001000. The subtitles become later by 0.10 % of their time, so the change is zero at the start and largest at the end. The exact NTSC rates are used (23.976 = 24000/1001, 29.97 = 30000/1001).

    Drift between 24 and 23.976 fps

    Subtitle timeAfter conversionDifference
    00:10:0000:10:00,600+0.6 s
    00:30:0000:30:01,800+1.8 s
    00:45:0000:45:02,700+2.7 s
    01:00:0001:00:03,600+3.6 s
    01:30:0001:30:05,400+5.4 s
    02:00:0002:00:07,200+7.2 s

    A 120-minute film timed at 24 fps runs 7.2 s longer at 23.976 fps.

    How to convert subtitles from 24 to 23.976 fps

    1. Open the subtitle file. Drop the subtitle file that drifts on the tool.
    2. Check the frame rates. “Subtitle made for” is set to 24 fps and “Video plays at” to 23.976 fps.
    3. Convert. Click Convert frame rate, then compare a line near the end with the video.
    4. Save. Download in SRT, VTT, ASS or TXT.

    Other frame-rate conversions

    Background: why subtitles drift between frame rates. Not sure of the rates? Use two-point sync — it detects the ratio for you.

    FAQ

    How much do subtitles drift between 24 and 23.976 fps?

    0.10 % of the running time: 0.6 s after 10 minutes and 3.6 s after an hour.

    What is the conversion factor from 24 to 23.976 fps?

    Every time is multiplied by 24 ÷ 23.976 = 1.001000. A subtitle at 01:00:00 moves to 01:00:03,600.

    How do I know this is the right fix?

    If the subtitles are close at the start and the error grows steadily, it is a speed mismatch. If the error is the same everywhere, use Shift instead.