Why will my browser not load the .vtt file I already had?
The three usual causes are a missing WEBVTT header line, a byte-order mark sitting in front of that header, and comma-separated milliseconds left over from an SRT file that was renamed without being converted. This converter fixes all three: it writes the header, strips the BOM, and rewrites the timestamps with dots. Renaming a .srt to .vtt does not work, which is what most people try first.
What happens to my italic and bold tags?
They come through unchanged, and that is correct: WebVTT supports <i>, <b>, and <u> as SubRip does. What does not survive is anything SRT-specific, such as <font color> tags or ASS-style override codes like {\an8}. Those are passed through as literal text, so a player will either ignore them or display them on screen. Remove them first.
Should I keep the cue numbers?
Usually not. WebVTT does not need them, and dropping them makes the file smaller and less likely to confuse a strict parser. Keep them only if you intend to address individual cues from script or style them by ID, in which case they become the cue identifier line above each timing line.
Does the conversion change my timings?
No. Each timestamp is parsed into hours, minutes, seconds, and milliseconds and written straight back out in WebVTT form, so the values are identical to the millisecond. If your subtitles are out of sync with the video, they will be out of sync by exactly the same amount afterwards; this tool converts format, not timing.
How do I know it worked?
Check the cue count above the output box. It counts the timing lines in the result, so if your SRT had 340 cues and the output says 340, nothing was dropped. If the count is lower, some blocks failed to parse, which normally means a malformed timestamp somewhere in the source.
How do I convert an SRT file to VTT?
Open the .srt file in any text editor, copy its contents, paste them into the input box, and download the result as subtitles.vtt. The converter adds the WEBVTT header and rewrites the timestamps; there is no upload step because the conversion runs in your browser.
What is the difference between SRT and VTT?
Structurally, three things: a VTT file starts with a WEBVTT header line, uses a dot instead of a comma before milliseconds, and treats cue numbers as optional identifiers rather than required counters. VTT also supports styling and positioning that SRT lacks, but a plain subtitle file needs none of that.
Is this SRT to VTT converter free?
Yes, free with no signup. It is a paste-in, copy-out text transform that runs entirely in your browser, so there is no file size meter or daily quota involved.
Do my subtitles get uploaded?
No. The conversion is a local string transform in the page, the subtitles never leave your device, and it keeps working with the network disconnected. Nothing about the file is stored when you close the tab.
Can I convert VTT back to SRT?
Not on this page, but the companion VTT to SRT converter does the reverse: it strips the WEBVTT header, restores comma milliseconds, and re-numbers the cues for players that expect SubRip.
Is there a file size limit?
No practical one. A feature-length subtitle track is a few hundred kilobytes of text, and the converter processes it instantly. If you can paste it, it converts.