Fix subtitles that lag behind, run ahead of, or slowly drift away from your video's audio. Resync your entire .srt file in one pass — no sign-up, no forced watermark.
No account required No forced watermark on exports [TODO:实测] Browser-side processing vs. auto-delete
SRT files go out of sync for a handful of predictable reasons, and each one needs a slightly different fix. If you just nudge every timestamp by a single number, you might fix the first line but break the last one. SRTKit handles the three most common drift patterns so the whole file lines up, not just the opening cue.
Every cue is off by the same amount — maybe 1.5 seconds late, maybe 3 seconds early. This happens when you re-encode a video, trim the head, or grab subtitles from a different cut. A single positive or negative shift fixes the entire file.
The file starts close to correct, but by the end of a 90-minute movie the audio is five seconds ahead of the captions. This usually means the source frame rate or sample rate didn't match when the subtitles were generated. A linear time-stretch per cue restores alignment throughout.
Cues are fine through the first scene, then jump out of sync after a chapter break, ad insertion, or cut to a different camera angle. This needs you to anchor at a known-good point and shift everything after it independently.
If you have a 600-cue file and it's drifting, opening it in a text editor and editing every timestamp by hand is the definition of a bad afternoon. Resync tools apply the correction across all cues at once and let you preview the result before committing. For fine-grained single-cue edits, pair this with a standard SRT editor after resync.
Yes — the file format is the same regardless of source. Subtitles pulled from TV captures, Blu-ray rips, or YouTube's auto-generated captions are all plain .srt (or convertible to .srt). The drift pattern differs by source, but the fix mechanism is the same: detect the offset, apply a correction, export.
For ripped Blu-ray PGS or VobSub streams, you'll want to convert to SRT first using our main converter, then come back here to resync. The output timing is only as clean as the input timestamps.
That's a constant offset. Open the resync tool, enter the offset in seconds (positive to push subtitles later, negative to pull them earlier), apply, and re-check the opening cue. Most files settle on the first attempt.
Yes. Encoding fixes (mojibake like æµè¯ or ???) and timing resync are independent operations and both run in the same pipeline. Drop the file once and pick what you want fixed.
Just the timestamps. Cue text, ordering, and formatting are preserved. The output is byte-identical to the input except for the rewritten --> timing lines.
Use the batch mode — apply the same offset or stretch across every file in one run. For per-file corrections (each file needs a different shift), batch mode accepts a small CSV mapping filename to offset.
Yes, the same resync logic is exposed via the SRT API — POST an SRT body, get the resynced SRT back. Useful for pipelines that ingest subtitles nightly.
Drop your file, pick an offset, download a clean SRT. No sign-up, no forced watermark.
Resync SRT Subtitles — Free Try Batch Resync →