Check subtitles for overlap, reading speed and long lines
Subtitles become difficult to read when dialogue overlaps or disappears too quickly. Use the issue report to locate suspicious cues, then decide what needs editing by watching the corresponding video sections.

How to use this tool
- Add the SRT or VTT file to inspect.
- Set reading-speed and line-length thresholds.
- Run and compare reported cues with the video.
- Download the report for your editing checklist.
Choose the right settings
Set characters per second and maximum line length for your audience and display context. Defaults are inspection thresholds, not universal platform rules, so use the actual publishing requirements when they are available.
- Supported input
- SRT,VTT
- Available settings
- Maximum characters/second
- Maximum characters/line
Before you start
Identify a useful reference point
Keep the original media or subtitle file and define what you need: a still frame, a waveform, adjusted subtitles, a report or reading text. A visual extract is different from editing the source media. Use a recognizable scene, spoken line or time position as a reference so the result can be checked against something specific.
Where time, dimensions, display style or subtitle timing can be changed, test one choice before altering several. For subtitles, distinguish a constant delay from a mismatch that grows over time. For a thumbnail or waveform, choose settings that show the information you need; a larger picture alone does not add detail or establish an audio measurement.
Record the source version, reference time and relevant display or timing choices for a trial. Before changing subtitle timing, confirm that the subtitles and media belong to the version you intend to use; a mismatch is not always one adjustable delay. If only a later output looks wrong, compare the intermediate file with the original. A reading transcript can intentionally omit cue timing, and a still image omits motion, so judge each result against its purpose rather than against every property of the source.
Compare at the actual time and size
Check the saved result at its intended display size and compare it with the corresponding source moment. For subtitle output, test the beginning, middle and end with the media. For a transcript or issue report, compare sample lines with the original cues and note whether timing or layout information was intentionally left out.
If a frame cannot be decoded or a media file cannot be opened, check browser support and the source format before changing unrelated settings. If subtitle text parses but displays incorrectly, review the chosen format and player behavior. Keep the source for missing scenes, channels or cue information that the selected output does not preserve.
Example input and output
SRT/VTT → timing/readability issue reportExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Find reported cue numbers, start times and issue types in the original subtitle file. Determine whether overlapping dialogue is intentional, and read long or fast cues at their actual on-screen size.
If the result is different from what you expected
The inspection report identifies issues without automatically rewriting or repairing the subtitle file. Fix invalid timestamp syntax before inspection, and remember that an empty issue report does not establish translation quality.
Limits to keep in mind
- Report potential issues without changing cues. Review intentional overlaps against the video.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.