Convert YouTube SBV Captions to Plain Text

.sbv (SubViewer) is the caption format YouTube Studio offers when you download a video's captions, whether auto-generated or manually uploaded. It's built from blank-line-separated blocks: a timing line like 0:00:04.160,0:00:06.770 (start and end joined by a comma, no cue number, no arrow), followed by one or more lines of caption text. Reading it directly is about as awkward as reading SRT or VTT: sentences are chopped up every few seconds to fit on screen.

SubToolDesk's SBV to TXT converter parses every block locally in your browser. No file ever leaves your device. It extracts just the caption text, discards the timing entirely, and (optionally) reassembles the fragments into natural paragraphs.

How to convert SBV to TXT (step-by-step)

• In YouTube Studio, open Subtitles for your video, then use the options menu next to a caption track and choose Download > .sbv.
• Drag that .sbv file onto the converter above, or click “Upload File” to browse for it.
• Check the auto-detected format badge reads SBV.
• Toggle Merge into paragraphs on for flowing prose, or off to keep one caption per line.
• Toggle Strip speaker labels if your captions include names like “SPEAKER 1:”.
• Press Copy or Download to grab the finished .txt file.

Why convert YouTube captions to plain text

A .sbv file is built for YouTube's caption pipeline, not for reading. Stripping it down to plain text is almost always about what happens next:

• Reason: Turning a YouTube video's auto-captions into a blog recap or show notes, where timing is just noise.
• Reason: Feeding the transcript to an AI summarizer or chatbot, which reads continuous prose far better than hundreds of timed fragments.
• Reason: Pasting the dialogue into meeting notes or a project doc after downloading auto-generated captions from a recorded webinar or interview uploaded to YouTube.
• Reason: Sending a transcript out for translation or copyediting, where translators and editors work with paragraphs, not caption blocks.
• Reason: Archiving a video's dialogue as a searchable, readable record once the original upload no longer needs to be kept around.

Before and after: a real example

A short SBV export from YouTube Studio, speaker prefix included, converted with Merge into paragraphs and Strip speaker labels both on (the default state on this page):

0:00:01.200,0:00:04.000
SPEAKER 1: Welcome back, today we're covering the Q3 numbers.

0:00:04.300,0:00:07.900
SPEAKER 2: Thanks for having me. Let's dive right in.

0:00:08.100,0:00:11.500
SPEAKER 1: Revenue was up eight percent year over year.

Welcome back, today we're covering the Q3 numbers. Thanks for having me. Let's dive right in. Revenue was up eight percent year over year.

Every timing line and both SPEAKER 1: and SPEAKER 2: prefixes are gone. What's left is exactly what was said, reflowed into readable sentences.

The SBV format, byte for byte

A single SBV block looks like this, no cue number, no arrow:

0:00:03.500,0:00:06.120
Thanks for joining the call today.

The two timestamps are joined by a single comma with no surrounding spaces, each in H:MM:SS.mmm form. One or more lines of caption text follow directly beneath, and a blank line separates each block from the next. Multi-line blocks are joined with a line break inside the block; SubToolDesk treats that internal break as a soft wrap, not a sentence boundary, when merging into paragraphs.

Why strip speaker labels before merging?

YouTube's auto-captions and manually uploaded tracks frequently prefix each line with a speaker identifier so a viewer can track who's talking. That's useful on screen, but it breaks the flow of a paragraph-style transcript and reads oddly repeated every sentence. Stripping speaker labels before the paragraph merge keeps the output publication-ready.

Privacy by architecture, not by policy

Competing converters typically upload your file to a server to parse it, which means your confidential meeting recording, legal deposition, or unreleased video script passes through someone else's infrastructure. SubToolDesk's SBV to TXT tool is built the opposite way: parsing, cleaning, and rendering all happen in JavaScript running in your tab. There is no upload endpoint for this feature to hit. It's not a policy promise, it's a structural guarantee.

Common use cases for SBV to TXT

• Blog recaps and show notes: turn a YouTube video's caption download into a readable draft in seconds instead of re-watching to write notes from scratch.
• Translation prep: hand a translator continuous paragraphs instead of fragmented timed cues, which read far more naturally in a second language.
• Feeding an AI summarizer: most language models produce better summaries from flowing prose than from a timing-riddled file, and paragraph merging does that reformatting for you.
• Searchable archives: plain-text transcripts are easier to full-text search, tag, and store in a documentation or knowledge-base system than a timed caption file.

Common problems and how to fix them

• Timing or stray commas are still in the output: check the format badge above the converter actually reads SBV, not Unknown; a truncated paste can break block detection.
• SPEAKER 1: or similar names are still prefixing lines: turn on Strip speaker labels, it only catches a leading name pattern and won't fire if it's off.
• The transcript reads as one sentence per line instead of flowing paragraphs: turn on Merge into paragraphs.
• Accented letters or non-English text show up as garbled characters like é: the source .sbv wasn't saved as UTF-8; re-export or re-save it as UTF-8 and re-upload.