What is an SBV file?

SBV is a plain-text format you can open in any editor. It is used for subtitling.

The extension is .sbv, and the full name is YouTube Subtitle. Both matter less than what the file can hold, which is what the rest of this page is about.

Google published it in 2008.

Age is worth knowing here for one practical reason: the older a format is, the more programs have had time to learn it.

It is written down and implementable, though the vendor decides what the next version looks like. In practice that is enough for the file to keep opening; it is not enough to be sure of it.

It exists to do one job well for one group of people. Outside that job it is a poor default, and inside it there is usually nothing better.

YouTube Studio and Subtitle Edit read it, and so do most programs of the same kind.

If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.

No browser reads it.

That is the single most common reason to convert it: not that the format is bad, but that the place you want to show the file cannot read it.

SBV is meant to be opened and changed. Keep the file in this format for as long as the work is going on, and export from it whenever a finished copy is needed.

SBV is YouTube’s own subtitle format, produced by its caption editor and offered by its download tool alongside SRT and VTT. Nothing else writes it and very little else reads it, so a file with this extension came from one place.

Usually it arrives in one of two situations: somebody downloading their own captions to correct them offline, or somebody retrieving the automatic transcript of a video to reuse as text. Both end in the same question, which is how to get the file into anything else.

A start time, a comma, an end time, on one line. The caption text on the next line or two. A blank line. Repeat. There is no numbering, no header, and no styling of any kind.

Timestamps are written as hours, minutes, seconds and milliseconds with a full stop before the milliseconds, and — the detail that catches people converting by hand — the hours are not zero-padded, so a caption at four minutes begins 0:04:12.500 rather than 00:04:12,500. That single difference is why a renamed SBV is not a working SRT.

No positioning, no colours, no fonts, no speaker markers, no styling at all. In that respect it is simpler even than SubRip, which at least has a convention for italics that most players honour.

That is not really a criticism. The format exists to move caption text in and out of one web application, where the appearance is decided by the player and nobody is expected to design anything. It becomes a limitation only when the file leaves YouTube, which is the situation that brings people here.

SRT for anything played in a desktop player, on a television or uploaded to another platform. VTT for video on a web page, since that is what browsers accept. Both conversions are mechanical — the structure is close enough that only the timestamp punctuation and padding genuinely change.

If the destination is another video platform, check what it takes before converting: most accept SRT, several accept VTT, and almost none accept SBV. Uploading the file you have and hoping is the slow way to find that out.

A large share of the demand for this format has nothing to do with subtitles. People want the words: to turn a talk into an article, to quote a source accurately, to search a long video for the two minutes that matter, or to feed the text into something else.

For that, the timestamps are noise. Converting to plain text strips them and leaves the transcript, which is generally what was wanted. Bear in mind what the source was — an automatic transcript is good enough to skim and not good enough to quote, and the words it gets wrong are disproportionately the proper nouns and the technical terms that carry the meaning.

Any text editor works, and for correcting an automatic transcript that is usually the fastest route: the structure is obvious, and the work is reading and retyping rather than timing.

Save as UTF-8, keep the blank line between entries, and leave the timestamp format exactly as it was — hours unpadded, a full stop before the milliseconds. YouTube is not forgiving about that on upload, and a file it rejects gives very little indication of why.

As a working file, no. It reads nowhere, it carries nothing SRT does not, and it ties a set of captions to one platform.

The sensible arrangement is to keep the captions as SRT — which every subtitle editor handles, every player reads and every platform accepts — and convert to whatever a particular upload wants at the point of uploading. SBV then becomes a transport format you pass through rather than a file you maintain.

SBV carries a start time, an end time and the words. There is no italic, no colour, no way to say which corner of the screen a line belongs in and no way to mark who is speaking beyond typing it into the text.

That austerity is why it survives as an interchange format long after the tool it was built for changed. A file with nothing in it but timings and text cannot lose anything on the way into another program, and every subtitle format can represent what it holds. Converting the other way is where the loss is, because everything the richer format was carrying has nowhere to go.