Why SRT overlaps happen
An overlap error occurs when the end time of one cue is later than the start time of the next cue. A person reading two lines of text at once wouldn't think twice about it, but most video players treat this as a conflict they can't resolve — VLC, Premiere Pro, and YouTube's player will often drop one or both cues rather than guess which should take priority.
In practice, overlaps almost always come from one of three places:
- Manual entry errors — typing timestamps by hand is an easy way to accidentally let one cue run past the next one's start.
- Copy-paste drift — duplicating a cue as a starting point for the next line, then adjusting only one of the two timestamps.
- Machine transcription output — auto-generated transcripts are frequently timed loosely and need a manual pass before they're usable as subtitles.
Three types of timing error, and how to tell them apart
Before fixing anything, it helps to know which of these you're actually looking at — the fix is different for each.
1. Incorrect sequence
This is when a single cue's own start time is later than its own end time — nothing to do with neighboring cues, just an internal contradiction. It's usually a typo (a digit transposed while typing the timestamp) and it will not render on any player.
2. Overlap between cues
This is the most common cause of flickering: cue A's end time lands after cue B's start time.
00:00:10,000 --> 00:00:13,500
First line of dialogue.
2
00:00:13,000 --> 00:00:15,000 // starts before cue 1 ends
Second line of dialogue.
3. Duration warnings
Not a hard error, but a readability problem: a cue that's on screen for well under a second is often gone before a viewer can finish reading it. This shows up most often on short exclamations or interjections that got auto-timed to match a very brief audio clip.
Catch all three automatically. Scan a full track for overlaps, sequence errors, and short cues in one pass — free, in your browser.
Open the editor →The fix-it workflow
Once you know which cues are flagged, resolve them in this order rather than deleting and retyping from scratch:
- Scan the whole track first. Fix issues in a batch rather than one at a time as you notice them — an early fix can sometimes shift what counts as an overlap further down the track.
- Adjust the earlier cue's end time, not the later cue's start time. Pulling the first cue's end time back preserves when the second line of dialogue actually starts. Pushing the second cue's start time later instead can make it feel out of sync with the audio.
- Check for accidental duplicate cues. A large, clearly-wrong overlap is often a sign that the same line got added twice with slightly different timing, rather than a genuine timing conflict.
- Leave a small gap between cues where you can. A brief gap — even just a couple of frames — gives the eye a moment to reset between lines and avoids a "stuck" flicker some players introduce on instantaneous cue changes.
Why automated checking beats scanning by eye
Manually reading through a 40-minute subtitle track looking for overlapping timestamps is slow and easy to get wrong — the errors that matter most are usually a handful of milliseconds, not something you'll reliably catch by eye. An automated check flags every conflict in the file in one pass, and consistently applies the same rules a video player will apply on playback.
Since a browser-based editor can run that check entirely on your device, you can validate a confidential or unreleased project without uploading it anywhere.