Convert between SRT and WebVTT
SRT to WebVTT and WebVTT back to SRT, both directions. It converts on upload — the file never leaves your browser.
Accepts .srt and .vtt up to 5 MB. The direction is read from the file extension — or you can pick it yourself.
The file is never uploaded — everything runs locally in your browser
Need the subtitles burned into the video?
The full version takes the video itself: it transcribes the speech, translates it, and burns the subtitles into a file you can publish.
Sign up free and get trial creditsFAQ
What is the difference between SRT and VTT, and which should I use?
They differ only in the container format — the timing and the text are identical. SRT has the widest support: desktop players (VLC, PotPlayer) and video editors all read it. VTT (WebVTT) is the web standard, and YouTube plus HTML5 video only accept VTT. Going to YouTube or embedding subtitles on your own site? Use VTT. Handing the file to an editor or a client? Use SRT.
Does converting change the timing?
No. The conversion only rewrites how timestamps are written (SRT separates milliseconds with a comma, VTT uses a period) and adds the required WEBVTT header to VTT files. Without that header line a browser refuses to load the subtitle file at all.
My file was saved in Windows Notepad — will it come out garbled?
No. The tool decodes strictly as UTF-8 first and falls back to GBK, which covers both encodings you are likely to hit. That is one advantage of processing locally: if something is wrong you see it immediately, instead of a file that "uploaded fine" but decoded into mojibake.