SBV to SRT Converter
Convert YouTube SBV captions to SubRip or WebVTT. SBV separates the two timestamps with a comma and SubRip puts one inside each timestamp, which is why a rename produces a file with half the cues.
Processed on your device — no upload
How to use it
- Paste the captions, or choose the .sbv file.
- Pick SubRip or WebVTT.
- Copy or download the result.
How it works
SBV is the format YouTube’s own caption editor hands back. It is the simplest format in this section: two timestamps, then the lines, then a blank line. No header, no index numbers, no styling and nowhere to put any. Which is exactly why an SBV file turns up so often in front of a tool that has never heard of it — a caption download from YouTube is where most people first meet the extension, and the reason to convert SBV at all is that almost nothing else reads it.
YouTube captions are the source of nearly every one of these files, and they arrive in two states: written by a person, or generated automatically. Both are SBV, and the conversion is the same for either.
The comma is in a different place, and that is the whole problem. An SBV timing line reads 0:00:01.000,0:00:04.000: a full stop before the milliseconds, and a comma separating the start from the end. A SubRip timing line reads 00:00:01,000 --> 00:00:04,000: a comma before the milliseconds, and an arrow separating the two. Both formats have a comma between two numbers, so a tool that looks for the comma rather than for what sits either side of it reads one as the other.
When that happens, the file does not fail — it half works. Every pair of cues is read as one, each running from its own start to the next cue’s, and the result is a track with half the lines and every one of them on screen twice as long as it should be. What actually distinguishes the two formats is the arrow: SBV has none, and neither SubRip nor WebVTT can express a cue without one.
Index numbers are added, not preserved. SBV has none at all. SubRip requires a sequential number above every cue, so the output is numbered from one. WebVTT does not require them and does not get them.
The hours are single-digit and stay optional going in. SBV writes 0:00:01.000 rather than 00:00:01.000. SubRip requires the long form, so the output always writes it, whichever way the input was written.
A worked example
Press Load a sample. It is three cues of SBV, and the status line reads read as SBV — decided from the content, not from the extension, so it also answers the question of whether the file is what its name claims.
Convert it to SubRip. The first cue becomes 00:00:01,000 --> 00:00:04,000 with a 1 above it: the hours padded to two digits, the comma moved from between the timestamps to inside each one, the arrow added, and the index that SBV never had written in.
The second cue’s two lines stay two lines. Where a caption breaks is a decision somebody made about where the sense breaks, and re-wrapping it silently would throw that decision away.
Now convert the same input to WebVTT instead. The WEBVTT header appears at the top, the commas inside the timestamps become full stops, and the index numbers are not written — WebVTT does not ask for them.
Automatic captions from YouTube usually need one more pass after this: turning them into a transcript collapses the repeated line that rolling captions leave behind, and tidying the timings separates the cues that were written to overlap on purpose.
Questions
Is my caption file uploaded?
No. It is read by your own browser and never leaves the device — which is worth caring about for an unpublished video, because a caption file is the complete script of it.
What is an SBV file?
It is the caption format YouTube uses in its own editor and in the caption download. Two timestamps separated by a comma, then the text, then a blank line. It carries no styling, no positioning and no index numbers.
Can I just rename .sbv to .srt?
No. A player reading it as SubRip finds no arrow where it expects one and shows nothing at all — or, worse, reads pairs of timestamps as single cues and shows half your captions for twice as long.
Does YouTube still use SBV?
Its caption editor still produces it, and it is still what a lot of downloaded caption files are. YouTube will also accept SubRip and WebVTT on upload, so converting in this direction is the common one.
What happens to the automatic captions’ repeated lines?
Nothing, in this tool — the conversion is faithful, and the cues come out as they went in. That repetition is how rolling captions work rather than an error in the file. The subtitle-to-text tool collapses it, because a transcript should not say everything three times.
Can it read a file that is actually SRT with the wrong extension?
Yes. The format is decided from the content, so a mislabelled file is read as what it is, and the status line reports what it decided.
Will it convert SRT back to SBV?
No. There is no reason to: YouTube accepts SubRip and WebVTT directly, so converting into SBV would mean going into a format with fewer capabilities to upload it to the one place that no longer needs it.
What happens to a cue with no text?
It is skipped and counted in the status line rather than written out empty. An empty cue is a gap on screen, and it also divides by zero in any reading-speed check run afterwards.
Is SBV to SRT Converter free to use online?
Yes — free, with no account, no daily limit and no watermark. It runs online in your browser, and because the work happens on your own device it keeps working offline once the page has loaded.
Related Subtitles tools
Merge Subtitle Files
Two languages, or two halves
open$termiva subs split film.srt --at 01:02:30Split a Subtitle File
Cut at a time, rebase the rest
open$termiva subs strip film.srt --tags --sdhRemove Subtitle Formatting
Take the layers off the words
open$termiva subs tidy film.srt --gap 100msFix Overlapping Subtitles
Ends move, starts never do
open