SubForge · subtitle converter · 0 uploads

SRT in, VTT out.
Half a second late,
fixed in the tab.

Four subtitle formats read and written, a whole-file time shift, a timeline rescale for a different frame rate, gaps and overlaps repaired, long lines balanced — and a warning list that names the cue that will still read badly. The file never leaves your device.

0 bytes uploaded No file leaves the device SRT · VTT · ASS · SBV

Subtitle file

Format — Cues 0 Length 0:00

Result

Before you ship

0 notes

No timing notes — the file reads clean.

Questions that come up

Is my subtitle file uploaded?

No. The file is read with the browser's own file API or pasted into the box, parsed in the tab and written back out there. The dialogue is never sent anywhere.

Will the conversion keep the styling?

SRT and VTT carry italic and bold tags, which survive. A full ASS style table does not: converting to SRT or VTT keeps the text and the times and drops the styling, and going back to ASS writes one clean default style.

Why is my file detected as the wrong format?

Detection looks at the first lines: a WEBVTT header, a [Script Info] block, numbered blocks with --> and commas, or a bare time pair. A file that starts with a title card instead of a cue can be read as the wrong one — pick the format in the list and it is parsed as that.