SRT to VTT Converter
Convert SubRip .srt subtitles to WebVTT .vtt in your browser, with an optional timing shift.
Drag & drop a .srt file here, or click to browse
No uploads. Your files stay on your device.
How it works
SubRip (.srt) and WebVTT (.vtt) are almost the same format, but
HTML5 <track> elements only accept WebVTT. This converter reads your SRT,
rewrites every timestamp from 00:00:01,000 --> 00:00:04,000 to
00:00:01.000 --> 00:00:04.000 (comma to dot), adds the required
WEBVTT header and normalises line endings. Timing lines without an hours field
(01:23,500) are expanded, stray Windows carriage returns and byte-order marks
are removed, and cue numbers are renumbered from 1 so a merged or hand-edited file comes out
clean.
If your subtitles run early or late, type a positive or negative number in “Shift
timings” to move every cue at once. “Strip unsupported tags” removes
<font> wrappers and ASS-style overrides such as {\an8}
while keeping the italic, bold and underline tags WebVTT does support. Everything happens in
your browser with plain JavaScript — the subtitle file is never uploaded, so unreleased
footage and client work stay private. Copy the result or download a ready-to-use
.vtt file.
Frequently asked questions
What is the difference between SRT and VTT?
They are almost the same format. WebVTT files start with a WEBVTT header line and use a dot before the milliseconds (00:00:01.000), while SubRip files have no header and use a comma (00:00:01,000). WebVTT also supports styling and positioning cues that SRT does not, and it is the only subtitle format the HTML5 <track> element accepts, which is why browsers need VTT.
How do I convert an SRT file to VTT?
Drop your .srt file onto this page or paste its contents into the box. The WebVTT version appears instantly: the WEBVTT header is added, every timestamp comma becomes a dot, cues are renumbered from 1 and Windows line endings are cleaned up. Then click Download .vtt, or Copy VTT to paste it straight into your player or editor.
Are my subtitle files uploaded anywhere?
No. The conversion runs entirely in your browser with plain JavaScript — the file is read locally and never leaves your device, so there is no server, no account and no size limit beyond what your browser can hold. That makes it safe for unreleased footage, internal training videos and client work under NDA.