Subtitles Time shift
Get your video and subtitles in sync.
How to useRead UTF-8, CP949/EUC-KR and UTF-16; output is always UTF-8. If auto detection is wrong, change the encoding and check the text.
Bring subtitles back into sync.
Every cue shifts by the same offset. If synchronization drifts over time, you need a separate speed adjustment tool.
- 01
Load subtitles
Open an SRT or VTT file, or paste its contents. UTF-8, CP949/EUC-KR and UTF-16 files are supported.
- 02
Shift forward or backward
Enter a positive offset for subtitles that appear too early, or a negative offset for those that appear too late. Precision is 0.001 seconds.
- 03
Review and download
Review the result and save the SRT or VTT as UTF-8. Your original file is unchanged.
To show cues 2.5 seconds later
00:00:01,000 → 00:00:03,500
00:00:04,000 → 00:00:06,500Enter 2.5 as the offset. Start and end times shift equally, preserving cue duration.
Frequently asked questions
Does cue text or styling change?
Cue text, numbers, identifiers, line breaks, VTT styles, and positioning are preserved. Inline VTT timestamps shift too. Trimming before zero removes the affected portions.
What happens when cues move before zero?
The default is to report an error. With trimming enabled, cues crossing zero start at zero, and cues ending at or before zero are removed. Remaining SRT numbers are preserved.
What if Korean text is garbled or I get a UTF-8 error?
Auto detects UTF-8 or UTF-16 with a BOM. Without a BOM, it tries UTF-8 first, then CP949/EUC-KR. CP949 is a guess: check the text. Changing File encoding rereads the original bytes. For UTF-16 without a BOM, select LE or BE manually. Editing the text detaches the file, so changing encoding will not overwrite your edits.
Which subtitle formats are unsupported?
ASS/SSA, UTF-32 and streaming VTT with X-TIMESTAMP-MAP are unsupported. Save other encodings as UTF-8 before opening.