Convert SBV to SRT Online

How to convert SBV to SRT

Converting takes a few seconds and never involves a server. Follow these steps:

1. Drop your SBV file — Drag the .sbv file exported from YouTube onto the box above, or click to browse. The file is read locally; nothing is uploaded.
2. Confirm the detected encoding — YouTube exports are normally UTF-8, but captions edited on Windows may be GBK or Windows-1252. The encoding is detected automatically and normalised.
3. Shift the timing if needed — If the captions do not line up with your video, enter a Time shift in seconds before converting.
4. Convert — Click Convert to SRT. Each SBV timestamp pair is rewritten into SRT's arrow format with a comma before the milliseconds, and cues are numbered sequentially.
5. Preview and download — Review the preview, then click Download to save the .srt file ready for your editor.

What is a SBV file?

SBV (SubViewer) is the legacy caption format YouTube offered for download through YouTube Studio. It is plain text: each cue begins with a start and end time separated by a comma and using a dot for milliseconds (0:00:01.000,0:00:04.000), followed by one or more lines of text, with a blank line between cues. There are no cue numbers, no styling and no positioning. YouTube now offers .vtt and .srt exports as well, but a great many archived caption files still exist as .sbv, and some third-party downloaders still produce it.

What is a SubRip file?

SRT (SubRip Subtitle) is the most universally accepted subtitle format. Each cue consists of a sequence number, a start --> end line using a comma for milliseconds (00:00:01,000 --> 00:00:04,000), the text and a blank line. Editors such as Premiere Pro, DaVinci Resolve and Final Cut, players such as VLC, and encoders such as HandBrake and FFmpeg all read .srt reliably, which makes it the natural destination for any caption file you intend to reuse.

SBV vs SRT: what actually changes

Here is exactly what the conversion alters and what it preserves, so there are no surprises when you play the result:

Why convert SBV to SRT?

SBV is the older caption format YouTube used to offer for download. SRT is the de facto standard that every video tool reads. Converting SBV to SRT re-formats the timestamps into SRT's arrow syntax, adds sequential cue numbers, and leaves the text and timing untouched — so the captions line up exactly as they did on YouTube.

Common use cases

Editing YouTube captions in Premiere or DaVinci

Professional editors import SRT cleanly. Converting first avoids the "unsupported format" errors you get when dropping an .sbv onto a timeline.

Re-uploading captions to another platform

Most video hosts and course platforms accept SRT. Converting lets you reuse captions you already have instead of re-transcribing.

Archiving your channel captions

SRT is a far more durable archival format than SBV because it is readable by essentially every tool in existence.

Burning captions into a video

HandBrake, FFmpeg and most cloud encoders take SRT as their subtitle input, making conversion the first step to hard-coded captions.

Tips and troubleshooting

Prefer .srt or .vtt exports when available

YouTube Studio now offers newer formats. SBV conversion exists mainly for archives, older channels and third-party downloads.

Keep the original export

Conversion is safe, but keeping the source file costs nothing and protects you if a timing edit goes wrong.

Check for duplicate cues

Auto-generated YouTube captions sometimes repeat a line across cues. Skim the preview and delete duplicates in an editor if needed.

Fix sync during conversion

Use the Time shift field if the captions run consistently early or late, so you download one corrected file instead of re-syncing later.

Naming your subtitle files so players find them

Most desktop and mobile players load a subtitle file automatically when two conditions are met: the subtitle sits in the same folder as the video, and both files share the same base name. A video called movie.mp4 is matched by movie.srt, movie.en.srt or movie.en.forced.srt, but not by subtitles.srt or movie (1).srt. The language code in the middle is optional and is used by players that offer a subtitle track menu.

If captions do not appear, the problem is almost always the file name rather than the file contents. Rename the subtitle to match the video exactly, or use the player's subtitle menu to load it manually once. On macOS, Total Video Player Pro goes a step further and matches subtitle files to your video automatically, including subtitle tracks already embedded inside MKV and MP4 files.

Using the converted SRT file

Once you have the .srt, place it in the same folder as your video and match the file names — movie.srt beside movie.mp4 — so players such as VLC, IINA and Total Video Player Pro for Mac load it automatically. If captions do not appear, open the player's subtitle menu and load the file manually.

For editing, import the .srt into Premiere Pro, DaVinci Resolve or Final Cut as a caption track; all three handle it without further conversion. To produce a video with captions permanently burned in, use HandBrake's Subtitles tab or FFmpeg with ffmpeg -i movie.mp4 -vf subtitles=movie.srt out.mp4. If you plan to re-upload the captions, SRT is accepted by YouTube, Vimeo and virtually every other platform.

Privacy: nothing leaves your browser

Most online subtitle converters work by uploading your file to a server, processing it there and letting you download the result. That approach has three practical drawbacks: your subtitle text passes through someone else's machine, you wait for the upload and the download, and the service can impose file size limits, queues or watermarks.

This converter does none of that. It is built with JavaScript and runs inside your browser tab. When you drop a SBV file, the browser reads it from your disk, parses it in memory, converts it to SRT and hands the result straight back to you — no network request ever carries your content. That has a useful side effect: there is no queue, no server-side size limit and no watermark, and the tool keeps working even if you lose your connection after the page has loaded. If you handle unreleased footage, confidential transcripts or anything you would rather not share with a third party, local processing is the safer default.

Frequently asked questions