Missing timestamps, overlapping cues, silent stretches where dialogue should be — upload your .srt and SRTKit closes the gaps so your subtitles stay in sync with the video.
No account required · No forced watermark on exports · Files processed [TODO:实测→确认: in your browser / auto-deleted within X hours]
Subtitle gaps are almost always a sign that one of three things went wrong upstream: an auto-transcriber dropped a line, an editor trimmed timestamps without re-checking, or a file was re-encoded and lost its first cue index. Here is what we see most often.
One cue ends at 00:01:23,500, the next starts at 00:01:25,800 — and there is nothing in between even though someone is clearly still talking. Usually caused by a transcriber that filtered out low-confidence lines or an editor that deleted "duplicates" too aggressively.
Cue 14 starts before Cue 13 ends. Most players render the later cue on top, which means one line of dialogue silently overwrites another. Common after manual editing in tools that re-number cues without adjusting in/out points.
The file opens with 00:00:00,000 --> 00:00:00,000 or skips straight to cue 2. Caused by trimming at the head or by a converter that stripped the leading cue. Players sometimes hide the whole file when this happens.
Cues jump from 4 to 7, then back to 5. Happens when an editor deleted or merged cues and the numbering was never rebuilt. Some players stop reading after the first gap in the index.
The same engine handles the related problems people run into while they are fixing gaps: encoding mismatch (mojibake like "æµè¯•"), off-by-seconds timestamp drift, and merging two .srt files into one. If you would rather fix all of this in code, the same logic is available as an SRT API.
Auto-closing is safe when the gap is short (under [TODO:实测] ms) and the next cue's text clearly continues the previous one. It is not safe when:
For these cases, switch to Strict mode. SRTKit will report the gap and leave both cues untouched, so you can decide manually.
It means repairing the timeline of an .srt file so consecutive subtitle cues are contiguous — no silent stretches where dialogue was dropped, and no overlapping ranges where one cue overwrites another. The text is left as-is; only the in/out timestamps and cue indices are adjusted.
No. The gap fixer only rewrites timestamps and cue numbers. If a cue's text is wrong, that is a different problem (usually a transcription issue) and is left alone. If you also need to correct text, use the full SRT converter and repair suite.
Yes — upload a VTT, ASS, SSA, SCC, STL, or DFXP file and the same gap-repair logic applies, because the timeline format is identical. Output can be saved in any of those formats, so you can fix a VTT and export it as clean .srt, or vice versa.
Yes. The fixer is designed for full-length films and long-form content — files up to [TODO:实测: size] with thousands of cues process in a single pass. For an entire season of episodes at once, use batch mode.
No forced watermark is added to any export — every file you download is a clean, platform-ready .srt you can upload straight to YouTube, Vimeo, or a broadcast workflow. There is no sign-up step gating the download either.
Drop in your .srt and download a clean, contiguous timeline in under a minute. Or fix an entire folder of files in one go.