ToolCabana
Language preview: no interface translation is available for this language yet. Showing English. Use English

Subtitle timing editor

Shift subtitle timing and flag overlapping cues.

Favorites are saved in this browser. Find them in My favorites.

Subtitle timing editor

Your input stays in this browser unless stated otherwise
Clear your input, files and result, and restore the default settings.
Load sample text to explore what this tool can do. This replaces your current input.
0 charactersClear the source text.

How to use Subtitle timing editor

The subtitle timing editor shifts every cue in an SRT or WebVTT file earlier or later by a set number of seconds and counts overlapping cues. Shifts range from -3600 to 3600 seconds in whole milliseconds. You choose SRT or WebVTT as the output format, and the result shows the number of cues and overlaps.

  1. Paste the source into the input editor, or load the built-in example.
  2. Set shift seconds (may be negative), output format.
  3. Run subtitle timing editor, review the output, then use the available copy or download controls.

What this tool supports

Shift subtitle timing and flag overlapping cues.

Shift seconds (may be negative)
Range: -3600 to 3600
Output format
SRT · WebVTT

Limits and processing

Browser file and text limits apply, along with the bounds shown in Settings. Image processing is capped at 32 megapixels. OCR quality depends on source resolution and layout.

Example source
1
00:00:01,000 --> 00:00:03,000
Hello, world.

Frequently asked questions

How do I fix subtitles that appear too late?

Enter a negative shift, such as -1.5, to move every cue 1.5 seconds earlier. A positive value delays them. If a negative shift would push any cue before zero, the tool stops with an error.

What does the overlaps count mean?

After shifting, cues are sorted by start time and each cue that begins before an earlier cue has ended is counted. Overlaps can display two captions at once in some players, so check those cues.

Can I shift subtitles by a fraction of a millisecond?

No. Shifts must be whole milliseconds, so values like 0.25 or -2.125 seconds work but 0.0005 does not. The editor reports an error for finer values.

Where is my input processed?

Processes source in your browser. Copy and download are explicit actions; source is not saved to account history.

What are the input limits?

Browser file and text limits apply, along with the bounds shown in Settings. Image processing is capped at 32 megapixels. OCR quality depends on source resolution and layout.