What is the difference between SRT and VTT?
SRT and VTT both store captions as plain text with a start and end time for each line. SRT numbers every caption and writes times as 00:00:01,000 with a comma. WebVTT starts with the word WEBVTT, uses a dot (00:00:01.000) and adds positioning and styling. HTML5 video players read VTT; editors and upload forms mostly take SRT.
SRT came from SubRip, a Windows program for ripping subtitles from DVDs, and became the default exchange format for video editors and streaming uploads. WebVTT was written for the web by the W3C; the full syntax is in the WebVTT specification. Because the two share the same idea of a timed cue, converting between them keeps every caption and every time exactly as it was.
How the SRT to VTT conversion works
The converter reads each block of the SRT: the counter, the timing line and the text below it. It then writes a new file that starts with WEBVTT and a blank line, followed by each cue's timing with dots instead of commas, and the caption text with its line breaks. The cue numbers are left out because WebVTT treats identifiers as optional. Italic, bold and underline tags (<i>, <b>, <u>) are valid in both formats and pass through unchanged.
Timing lines with missing leading zeros or a dot in place of the comma, which some tools produce, are read as well, and the output always uses the standard hh:mm:ss.mmm form.
Encoding matters as much as syntax. WebVTT files are always read as UTF-8, so an old SRT saved in Windows encoding would show accented letters as garbled symbols. The converter spots those files, reads them in the older encoding and writes clean UTF-8, so é, ñ and ü display correctly in the browser.
Where you need WebVTT instead of SRT
- Your own website. The HTML5
<track> element reads WebVTT, so self-hosted videos, landing pages and portfolio sites need a .vtt file.
- Web video players. Video.js, Plyr, JW Player and similar players load VTT caption tracks.
- Courses and LMS platforms. Many learning platforms and course builders ask for WebVTT when you add captions to a lesson for accessibility.
- Accessibility. WCAG success criterion 1.2.2 asks for captions on prerecorded video with sound, and on a website those captions are a WebVTT track.
- Vimeo. Vimeo accepts both SRT and WebVTT, and VTT keeps the door open for later styling and positioning.
Going the other way, the VTT to SRT converter turns WebVTT captions from YouTube, Zoom or a course platform back into SRT for an editor. To fix a typo or a late caption before you convert, open the file in the SRT editor, which also downloads VTT directly.
Convert SRT to VTT on Windows, Mac, iPhone and Android
The converter works in any current browser on Windows, macOS, Linux and ChromeOS, and in Safari or Chrome on iPhone, iPad and Android. On iPhone and iPad, tap Open .srt files, pick the file in the Files app, and the VTT saves to Downloads.
For a single short file, a plain text editor also does the job: add WEBVTT and an empty line at the top, change the comma in every timestamp to a dot, and save with the .vtt extension in UTF-8. Changing the file name alone keeps the SRT syntax inside, so players expecting WebVTT read it as an empty track; the header and the dots are what make it a VTT. If you only have plain text and no timing yet, start with the TXT to SRT converter, which can save VTT directly.