SBV to SRT: Converting the File YouTube Studio Gives You

Download a caption track from YouTube Studio and you get a .sbv file. Open it in almost anything else and you get an error, or worse, a file that loads with every caption in the wrong place. SBV is a real format with a simple structure, and the conversion is straightforward once you can see what makes it different.

What an SBV file actually looks like

SBV, sometimes called SubViewer, is what YouTube produces on export. A cue is a timing line, then the caption text, then a blank line:

0:00:01.000,0:00:03.000
Welcome back to the channel.

0:00:03.200,0:00:06.100
Today we are fixing caption timing.
It takes about a minute.

Four things differ from SRT, and each one breaks a parser that is not expecting it:

• The two times are separated by a comma, not the --> arrow SRT and WebVTT use.
• There are no cue numbers. SRT numbers every cue; SBV numbers none.
• The hour has no leading zero. SBV writes 0:00:01.000 where SRT writes 00:00:01,000.
• Milliseconds are separated by a period. SRT uses a comma, which is the detail most often missed, because the file looks correct until a player refuses it.

The same captions as SRT

1
00:00:01,000 --> 00:00:03,000
Welcome back to the channel.

2
00:00:03,200 --> 00:00:06,100
Today we are fixing caption timing.
It takes about a minute.

Cue numbers appear, the arrow replaces the comma, the hour gains its zero and the decimal point becomes a comma. Nothing about the caption text changes, and no timing is recalculated, which is what makes this conversion safe in a way that a format like ASS to SRT is not.

The round trip is lossless

Because both formats carry exactly the same information, plain words and start and end times, converting SBV to SRT and back returns the file you started with, character for character. We test that both directions produce an identical file rather than assuming it. That matters if you are editing a YouTube track and intend to put it back: nothing is quietly rounded, and no cue drifts by a millisecond each time it passes through.

Why convert at all

Because SBV is a dead end everywhere except YouTube. Video editors, players, caption checkers and almost every online tool expect SRT or WebVTT. So the moment you want to fix timing, re-break long lines, check reading speed, or hand the file to anyone, it needs to be SRT first. Once it is, the usual timing fixes all apply.

Converting back to SBV is rarely necessary. YouTube accepts SRT and many other formats on upload, so unless a workflow specifically demands the original extension, the SRT is fine to send back. What YouTube does not do is keep your styling, whatever format you use, which is covered in the subtitle formats YouTube supports.

What neither format carries

Neither SBV nor SRT can express position, colour, font or karaoke timing. That is not a conversion loss, because SBV never had them. It matters only when a caption needs to move out from under an on-screen element, and there the answer is WebVTT rather than either of these, as covered in caption positioning and safe areas.

A short checklist

1. Download the track from YouTube Studio; expect a .sbv file.
2. Convert to SRT before doing anything else with it.
3. Check the first and last cue times survived the conversion.
4. Do the real work, timing, line lengths, spelling, on the SRT.
5. Upload the SRT straight back, unless something specifically needs SBV.

The SBV to SRT converter runs in the browser, converts in both directions, and warns you if the file you pasted is actually SRT or WebVTT rather than SBV. If you do not have a caption track yet, the caption generator will build one from the video.