Move every subtitle earlier or later by the same amount. This is the fix for subtitles that are uniformly out of step — a two-second delay that is still two seconds in the last line. If instead they line up at the start and drift further out as the film goes on, that is frame-rate drift, and the resync page fixes it with two anchor points.
How it works
- Drop a subtitle file, and the video too, for burn-in.
- Pick the fix: convert, shift, two-point resync, translate, or burn in.
- Download the corrected file, or the re-encoded video.
Questions
- Does my file get uploaded?
- No. The models and all processing run inside your browser on your own device. You can verify this yourself: open your browser’s DevTools, watch the Network tab, and process a file: there are no uploads. After the first visit most tools also work fully offline.
- What is a two-point resync?
- A fixed shift fixes subtitles that are uniformly early or late, but not ones that drift further out over the runtime (a frame-rate mismatch). Pin the first and last line to their correct moments and every cue between them is stretched linearly. That is the standard fix, done locally.
- How does on-device translation work?
- Recent Chromium browsers ship a built-in translator that downloads language packs and runs locally. Where your browser offers it, this tool uses it, subtitle text included, and nothing is sent to a service. Where it does not, the page says so instead of quietly uploading.
- Burned-in vs a subtitle file: which do I want?
- A separate .srt/.vtt can be toggled and edited, and players render it crisply, so prefer it where you control playback. Burn-in re-encodes the video with the text drawn into the frames: it plays everywhere and cannot be turned off.