Skip to content

Convert

SBV to SRT

SBV to SRT

Beta

Convert a YouTube Studio .sbv caption export into the .srt that editors and players accept, or convert back the other way. Paste or drop a file; nothing is uploaded.

Use via API
  • Free, no sign-up
  • REST + MCP
  • Updated
  • Reviewed by Olgun Ozoktas

Detected from what you paste until you choose.

SBV input
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
SRT output

Converted captions appear here

Common uses

Moving captions off YouTube

An .sbv export is the one file YouTube gives you and the one file your editor will not open. Converting it to .srt makes the captions usable everywhere else.

Re-uploading to another platform

Vimeo, LinkedIn and most self-hosted players accept SRT or VTT and not SBV, so a converted file uploads without a fight.

Editing captions in a desktop tool

Subtitle editors read SRT natively. Converting first means you can fix timing and typos in a proper editor rather than in the YouTube interface.

Going back to YouTube

The reverse direction turns an SRT back into SBV when you want to upload captions in the format YouTube exported.

Why convert SBV to SRT?

YouTube Studio still offers .sbv as a caption download, and almost nothing else reads it. The format is SubViewer: each cue is a timing line like 0:00:01.000,0:00:04.000 followed by its text, with no cue numbers and no header. SubRip wants 00:00:01,000 --> 00:00:04,000 with a number above it. The two are close enough to look interchangeable and different enough that renaming the file does not work — a player given a renamed .sbv usually shows nothing at all rather than reporting an error, which is why this trips people up.

SBV to SRT converts between SubViewer (.sbv) and SubRip (.srt) caption files in your browser. SubViewer is the format YouTube Studio hands out when you download captions, and it is close enough to SubRip to be mistaken for it: both are plain text, both list cues as a timing line followed by the words on screen. The differences are small and total. SBV writes 0:00:01.000,0:00:04.000 — an unpadded hour, a dot before the milliseconds, a comma joining the two stamps — and no cue number. SubRip writes 00:00:01,000 --> 00:00:04,000 with a sequential number on the line above.

Because the file is plain text either way, the temptation is to rename it, and because a player given a malformed caption file usually shows nothing rather than complaining, the result looks like the subtitles simply did not work. Converting properly rewrites the timings, pads the hours, swaps the separators and adds the cue numbers SubRip requires.

The conversion runs entirely in the tab: the file is read with the File API, converted and handed straight back, so nothing is uploaded and nothing is stored. Cue text and order are preserved exactly. The reverse direction is available for going back to SBV. If you need WebVTT for an HTML5 player, convert here and then use the SRT to VTT tool.

How it compares

Most answers to this are either a desktop subtitle editor, which handles SBV among a hundred other things, or one of the many upload-and-convert sites. The editors are excellent and are a large install for a format change; the upload sites do the same arithmetic this page does, on their server, with your file.

There is no reason a text format change needs a server. Caption files often carry unpublished material — a video still under embargo, an interview not yet released — and the smallest safe option is the one where the file never leaves the machine. This page reads it locally and converts it in the tab.

It does not translate captions, re-time them, or burn them into video. Those are separate jobs, and the Subtitle Shifter and Subtitle FPS Converter cover the timing ones.

Tips

  • SBV has no cue numbers. Converting to SRT adds them, numbered from 1 in order, because SubRip requires them.
  • The separators are the difference worth remembering: SBV writes a dot before the milliseconds and a comma between the two stamps, SubRip does the opposite.
  • SBV hours are not zero-padded, so 0:00:01.000 is valid. The SRT output pads them to 00:00:01,000.
  • Renaming a .sbv file to .srt does not convert it. Most players will simply show no subtitles, with no error to explain why.
  • If a line will not parse, the error names the line number so you can find it in the left panel rather than hunting through the file.
  • Need WebVTT for an HTML5 player instead? Convert to SRT here, then use the SRT to VTT tool.

Frequently asked questions

What is an SBV file?

SubViewer, the caption format YouTube Studio exports. Each cue is a timing line like 0:00:01.000,0:00:04.000 followed by the text, separated by a blank line. There are no cue numbers and no file header.

Can I just rename the file to .srt?

No. The timing lines use different separators and SubRip requires cue numbers the SBV file does not have. Most players respond to a renamed file by showing no subtitles at all, with no error, which makes the problem hard to spot.

Where do I download an SBV file from YouTube?

In YouTube Studio, open Subtitles, choose the video and language, then the three-dot menu next to the caption track and Download, picking SBV.

Is my caption file uploaded?

No. It is read in your browser with the File API and converted in the tab. Nothing is sent to a server, and you can confirm that in your browser's network tab.

Does the conversion change my caption text?

No. Only the timing lines and the cue numbering change. The words, their line breaks and their order are copied exactly.

Can it convert back to SBV?

Yes. Switch the direction to SRT to SBV. The cue numbers are dropped and the timings rewritten in SubViewer's format.

What if a line will not convert?

The error names the line number and shows the text it could not read, so you can find it in the input panel. A single malformed timing line is the usual cause.

I need WebVTT, not SRT. Can this help?

Convert to SRT here, then use the SRT to VTT tool, which converts in both directions between SubRip and WebVTT.

Are there limits on file size?

Up to about 10 MB of text, which is far larger than any real caption file — a feature-length subtitle track is usually well under 100 KB.

Rate This Tool

0/1000

Get Weekly Tools

Suggest a Tool