Guide · ~5 min read
Delay subtitles by 500ms after dubbing (starting point)
“Move everything half a second later” is a common dubbing fix—but only when timing error is uniform. This guide explains when +500 ms helps, when it does not, and how to apply it in an SRT file.
When +500 ms is a reasonable first try
- New dialogue track replaced M&E but subs were timed to old audio
- Every cue looks ~0.4–0.6 s late in preview
- Export is fresh SubRip from the same picture lock
When not to use a fixed 500 ms
Drift over runtime, per-scene different errors, or subs authored against wrong video need cue-level edits or re-transcode—not a global offset. See fix constant subtitle delay.
Apply +500 ms in practice
- Open SRT time shift.
- Set unit to milliseconds, offset 500 (positive = later).
- Apply, download, test opening + mid + end.
- If still early/late, tweak in 50–100 ms steps—not another arbitrary 500 ms stack.
Fine-tuning after 500 ms
Lip-sync often lands between 350 ms and 650 ms. After the first pass, adjust by ±100 ms. Pair with line length checks before vertical export.
How to use
- Confirm constant delay (same error at start, middle, end).
- In SRT shift tool, set +500 ms (adjust after preview).
- Download, re-import, spot-check three lines.
Frequently asked questions
- Why delay subtitles by 500ms?
- Dubbed tracks often lag picture lock; +500 ms (0.5 s) is a common starting offset when every line is late by a similar amount.
- Is 500ms always correct?
- No. Measure one dialogue line; use 300–800 ms typical range. 500 ms is a midpoint for testing, not a universal fix.
- Milliseconds vs seconds in SRT shift tools?
- Either works: 500 ms equals 0.5 s. Use ms for fine lip-sync after you are within ~100 ms.
- Will a global 500ms shift fix drift?
- Only if error is constant. If sync worsens over time, fix frame rate or regenerate subs.
- Can I apply +500ms in the browser?
- Yes—paste or open .srt, enter 500 in ms mode (or 0.5 s), apply to all cues, download.