Subtitle timestamps drifting, shifted by a few seconds, or slowly slipping out of sync across your file? Upload your SRT, choose a correction mode, and download a clean, resynced file. No sign-up. No forced watermark on exports.
No account required · No forced watermark · Files stay clean
Timing drift in subtitle files usually comes from one of a handful of causes. Identifying which one you're dealing with makes the fix a one-click job instead of a manual slog.
You exported from a video editor using a different framerate, or ripped captions from a different source — and every cue now starts a uniform number of seconds too early or too late. A single shift fixes it.
Auto-generated captions from long videos tend to drift — fine at the start, off by a full second by the end. This is the classic "stretch / linear retime" scenario where one constant shift isn't enough.
Your SRT cues were built around scene changes that don't match your final cut. The fix is a per-cue nudge — but doing it by hand across hundreds of lines is brutal.
Original captions were timed at 23.976 fps but your final video is 25 fps (or vice versa). Every timestamp needs to be proportionally scaled — a classic retime job.
Part of your file came from one transcribe pass and part from another, so the first half is on time and the second half is offset. A two-block shift handles it cleanly.
Some players interpret SRT timestamps slightly differently, making them appear "off" even though the file is technically valid. A rounding pass to whole frames can resolve it.
Four correction modes cover roughly the long tail of timing bugs we see in the wild. Pick the one that matches your symptom — or use visual preview to find it for you.
Add or subtract a fixed number of seconds from every timestamp. Use this when the whole file is consistently off — enter a positive value to push subtitles later, negative to bring them earlier. Works for the constant-offset case in one click.
Apply a scaling factor so subtitle durations match the real playback speed. Useful for FPS conversions and for gradually drifting auto-generated captions where the offset grows over time.
Apply different shifts before and after a chosen timestamp. Built for files where the offset changes mid-document — for example when you've stitched two source transcripts with different timing baselines.
Drag any cue on the timeline to nudge it individually, or set a new in/out by clicking. A waveform-style preview makes drift visible at a glance, so you stop guessing and start clicking.
Most "free" subtitle tools either slap a watermark on your export, force a sign-up, or only fix the easiest kind of error. SRTKit is built for the cases those tools ignore.
Your exported SRT is exactly the file you uploaded, with corrected timestamps. No header line, no injected comment, no branding footprint — safe to upload straight to your platform of choice.
Open the page, upload, fix, download. We don't gate fixes behind an email signup, and we don't sell your files to train models on. [TODO:privacy implementation confirmation]
Got a folder of episodes or a season's worth of short videos all with the same drift? Skip the per-file clicks and use the batch tool to apply the same correction across an entire folder.
Need timing-fixing baked into a transcoding pipeline? The same correction engine is available as an API so you can sync hundreds of subtitle files programmatically.
--> in-point and --> out-point of every cue so the duration stays intact.HH:MM:SS,mmm --> HH:MM:SS,mmm rows). All text, line breaks, formatting tags, and positioning data are passed through unchanged so your cues look identical apart from the corrected timing.Drop it into the timing fixer, pick a correction mode, and download a resynced file in seconds. Clean output, no forced watermark, no sign-up wall.
Prefer to script it? See the timing-fix API