What an SBV file is
SBV was YouTube's caption format before SRT and WebVTT took over. A cue looks like this:
0:00:01.000,0:00:04.000
Hello there.
0:00:05.500,0:00:08.250
Second line.
Two timestamps separated by a comma, then the text, then a blank line. No index number, no arrow. That minimalism is the problem: a tool that expects to see --> on the timing line will read an SBV file as one long block of junk text, which is why people end up looking for a converter.
The three differences from SRT
- No index number. SRT numbers each cue (
1,2,3). SBV has none. - A comma where SRT has an arrow. SRT writes
00:00:01,000 --> 00:00:04,000; SBV writes0:00:01.000,0:00:04.000. - No leading zero on the hour. SBV uses
0:00:01.000, SRT uses00:00:01,000.
The subtitle text and the actual times are identical. Conversion is a layout change, not a re-timing.
Where SBV files still come from
YouTube stopped exporting SBV years ago, so the format is mostly a fossil now. You still run into it from three places: caption files downloaded in the 2010s and never converted, a few transcription services that kept exporting in YouTube's old format, and older subtitle editors with SBV as their save option.
If a client or colleague sends you one, this converts it in a second.
After converting
The SRT you get back opens in every video editor and upload form. If the destination is a web player rather than an editor, WebVTT is the format that element reads natively — the same tool produces it.
If instead you have a text file with no timings at all, text to SRT estimates the cue timings from reading speed.