Convert VTT subtitles to SBV without uploading your files. Paste the subtitle text or drop a .vtt file, and the SBV version appears instantly — every cue keeps its exact start and end time. Copy the result or download it as a .sbv file.
VTT (WebVTT) is the web's subtitle format — the one browsers and HTML5 video players read. SBV (SubViewer) is the simpler format YouTube's uploader accepts: the same cues, but timestamps separated by a comma and no cue numbers at all. If the video needs plain desktop subtitles instead, VTT to SRT is the universal format, and SRT to SBV converts subtitles that start as SRT.
How to use
- Paste your VTT subtitles into the input box, or drop a .vtt file to load it.
- The SBV output appears automatically, with every cue's timing preserved to the millisecond.
- Copy the result, or download it as a .sbv file with the Download button.
- Check the first and last cues in your player — if the timing looks right there, the whole file is right.
Why use Toolsvine
YouTube accepts VTT, so converting VTT to SBV is usually about an older upload workflow or a guide that names SBV specifically — and the few tools that offer the format want the file uploaded first. This converter does the job locally in your browser, keeps every cue's timing to the millisecond, and writes plain SBV with no header and no cue numbers, ready for the uploader.
What is SBV?
SBV is the SubViewer format: the plainest subtitle file still in common use. Each cue is a pair of timestamps separated by a comma, then the text, with a blank line between cues. No header, no cue numbers, no styling — just the times and the words, which is exactly what YouTube's subtitle uploader reads.
VTT and SBV timestamps already agree: both use dot milliseconds, so 00:00:01.000 means the same thing in both files. The conversion only drops the WEBVTT header, removes the arrow and any cue numbers, and joins the two times with a comma. The words and the timings never change — the SBV file is the VTT file with the web extras taken out.
What changes in the conversion
| Detail | SBV |
|---|---|
| Header | WEBVTT line removed |
| Timestamps | Arrow removed, times joined with a comma |
| Cue numbers | Dropped — SBV has none |
| Positioning | Dropped — SBV has no positioning |
| Text | Unchanged |
| Timings | Unchanged, to the millisecond |
VTT files often carry extras SBV cannot hold: positioning settings after the timestamp, voice spans, and style blocks. Those are dropped, because SBV has nowhere to put them — the words and the times carry over, and everything else is left behind. If styling matters, convert to ASS instead, which keeps it.
Worked example: two VTT cues become SBV
Press Sample and the tool loads two cues: "Hello world" from 1 second to 4.5 seconds, and "Second line here" from 5 seconds to 7.25 seconds. The SBV output has no header and no numbers — just two timestamp pairs and the two lines of text. VTT and SBV both write 00:00:01.000, so only the arrow disappears.
Example input:
WEBVTT\n\n00:00:01.000 --> 00:00:04.500\nHello world\n\n00:00:05.000 --> 00:00:07.250\nSecond line here
Becomes:
00:00:01.000,00:00:04.500\nHello world\n\n00:00:05.000,00:00:07.250\nSecond line here
Try it yourself: change the second cue's end time from 7.25 to 8 seconds in the VTT and watch the SBV update — 00:00:08.000, with the dot. Then upload the .sbv file to a YouTube video: YouTube reads the timestamps and shows each line at the right moment. If the subtitles started as SRT instead, the SRT to SBV converter writes the same format.
When should I choose SBV over SRT?
Choose SBV when a tool asks for it by name — YouTube's uploader and a few older workflows do — and choose SRT for everything else. SRT plays in far more players and editors, carries cue numbers that make editing easier, and converts to SBV in seconds whenever a tool demands the simpler format.
SBV's simplicity is its whole appeal: nothing to misconfigure, nothing to strip. But that simplicity is also the limit — no numbers, no styling, no positioning. Keep the VTT or SRT as the master copy, and generate SBV only when the destination asks for it.
Frequently asked questions
Will the subtitle timings stay exact when converting VTT to SBV?
Yes — timings are carried over to the millisecond, and the timestamp format does not even change: VTT and SBV both write 00:00:01.000. Only the arrow and the WEBVTT header are removed. The moments each line appears and disappears do not move at all, so the conversion is lossless.
Is converting VTT to SBV free?
Yes, completely free with no account and no file-size games. The conversion runs in your browser, so your subtitles never leave your device. You can convert one cue or a two-hour feature film's worth of subtitles and the price stays the same: nothing.
Can I upload a .vtt file instead of pasting?
Yes — drop the file on the box above and its text loads into the input automatically. You can also paste from your clipboard, which is handy for subtitles copied out of an editor. Either way, the file is read on your device and never uploaded anywhere.
What if my VTT file has errors?
The tool shows a plain-English error naming the problem — for example a cue with a missing timestamp — instead of producing a broken file. Fix that cue and the conversion runs. Blank cues and cues that end before they start are dropped quietly, since they cannot play anyway.
What is the difference between SBV and VTT?
Very little. SBV drops the WEBVTT header, the cue numbers, and the arrow between the timestamps, joining the two times with a comma instead. The timestamps keep the same dot format and the words stay identical. Think of SBV as VTT with the web extras removed — the same subtitles in the plainest wrapper that still plays.