How to fix subtitle timing

Timing bugs show up as lines that appear too early, hang too long, or step on each other. Sometimes the whole file is shifted by a fixed amount. Sometimes drift grows minute by minute because speed or frame rate changed somewhere in the chain.

You will learn how to diagnose which problem you have, how to shift groups of cues without wrecking spacing, and when re-transcribing beats nudging hundreds of lines. You will also learn why Bluetooth headphones lie about sync.

If dialogue changed because you re-edited audio, regenerate a new SRT from the final mix using the free upload tool, then re-apply style in your NLE. Patching ancient cues onto new audio rarely ends well.

Step-by-step guide

Step 1: Play from the first cue and listen for pattern

If everything sounds equally early or late, you likely need a global offset. If drift grows over time, suspect speed change or mixed frame rates.

Step 2: Apply a global shift when it fits

Move all cues earlier or later by the same milliseconds. Preview after a small test shift before you commit wide changes.

Step 3: Hunt overlaps locally

When cue ends meet cue starts, shorten ends slightly. Leave a tiny gap so players do not strobe text.

Step 4: Align to dialogue, not only timeline markers

Cuts and reaction shots sometimes need captions to appear after the cut even if the timeline says otherwise. Trust the spoken word.

Step 5: Revisit speed changes

If you changed playback speed in the edit, subtitles rarely track automatically. Re-time or regenerate from the final audio.

Step 6: Export a new SRT version

Name files with _shifted or _v2 so you can roll back.

Step 7: Test on the device viewers use

Phones, cheap laptops, and TV apps behave differently. One quick check prevents surprises.

Tips for better subtitles

• Use wired headphones when judging sync.
• If only one section drifts, fix local mistakes before global stretches.
• Frame snapping helps in NLEs when delivery expects frame boundaries.
• Keep notes on sample rate and fps when debugging drift.
• Avoid stacking two fixes you cannot separate later. Document what you changed.
• When in doubt, regenerate from final mixed audio.

Common mistakes

• Dragging every cue by hand when a global shift would work If every cue is late by the same amount, one shift fixes the file in a second. Moving hundreds of cues by hand also introduces new errors of its own.
• Ignoring Bluetooth latency during review You might shift good cues the wrong way.
• Leaving overlaps because “it looked fine in scrubbing” Scrubbing hides the problem because you never see two cues alive at once. In real playback the lines flicker or replace each other mid sentence.
• Stretching timings without measuring the speed change Guessing at a ratio replaces one drift with another, usually in the opposite direction. Measure the offset at the start and at the end, then let the tool calculate the factor.

FAQ

Conclusion

Timing issues look chaotic until you classify them. Fixed offset, local overlap, or drift each wants a different fix. Solve the class first, then polish details.

Upload fresh audio if the edit changed, then adjust subtitles with fewer guesses.

Related guides

• How to sync subtitles with audio
• How to edit an SRT file
• How SRT files work