VTT to SRT Converter

Anything that WebVTT can express and SubRip cannot. That means the STYLE blocks, the REGION definitions, the per-cue settings such as align, position, size, and line, and the NOTE comments. SubRip is a plain format: a number, a timing line, and some text. If you were relying on VTT positioning to keep captions off a lower third, you will need to re-do that in whatever tool you are moving to.

Because SubRip requires a sequential numeric counter above each cue and WebVTT does not have one. The converter numbers the output cues from 1 in order, ignoring whatever cue identifiers the VTT file had. That also means the numbering is always correct even if the source file had gaps or duplicates.

No, and it fails in a way that looks like a corrupt file. SubRip parsers expect comma-separated milliseconds and a numeric counter, and they choke on the WEBVTT header line. Renaming produces a file that some players show partially and others reject outright, which is far more annoying than a clean conversion.

Those are WebVTT voice spans, which name the speaker (<v Alice>Hello). SubRip has no equivalent, so they pass through as literal text and most players will show the tag on screen. Search and replace them out of the output, or convert them into a plain speaker prefix such as "ALICE:" before you ship the file.

Yes, to the millisecond. Each timestamp is parsed into its components and rewritten in SubRip form, so the values are unchanged. Only the separator and the presence of the hours field differ, and both are normalised to what SubRip expects.

Open the .vtt in any text editor, copy everything, paste it into the input box, check the cue count, and click Download .srt. There is no file picker and no upload step, because the conversion is a text transform running inside the page; the file never leaves your machine.

Compare the cue count shown above the output against the number of cues in your source. The count is taken from the timing lines in the result, so if the source had 340 cues and the output says 340, nothing was skipped. A lower number means some blocks had timestamps the parser could not read, which are dropped silently.

No. The conversion is a local string transform, the text never leaves your device, and the tool keeps working with the network disconnected. Nothing about the file is stored once you close the tab, which matters when the captions are for unreleased material.

Yes, free with no signup and no size limit worth mentioning. A feature-length caption track is a few hundred kilobytes of text and converts instantly. If you can paste it, it converts.

Yes, on the companion SRT to VTT page, which does the reverse: it adds the WEBVTT header, rewrites the comma milliseconds as dots, strips a stray byte-order mark, and can optionally keep the SubRip cue numbers as VTT cue identifiers.