How to Batch Convert VTT Subtitles to SRT

VTT (WebVTT) is the web’s subtitle format — it’s what YouTube, Vimeo, and HTML5 video players use. SRT is the universal format — it works in virtually every video player, editor, and device ever made. When you download subtitles in bulk (a course, a video series, an archive) and they’re all VTT, converting them one by one is miserable. Batch conversion does the whole folder at once.

This guide covers three no-code-friendly ways to batch convert VTT to SRT: Subtitle Edit’s batch mode (easiest), ffmpeg (most powerful), and free online converters (no install). Plus what actually changes between the formats and how to verify your output.

VTT vs SRT: What Actually Changes in Conversion

The formats are close cousins, so conversion is mostly mechanical. Here’s what the converter handles:

In practice: the converter strips the WEBVTT header, swaps periods for commas in timestamps, drops positioning/style metadata, removes comments, and adds sequence numbers. The spoken text and timing survive intact. What you lose is web-specific presentation data — which doesn’t apply outside a browser anyway.

One caution: if your VTT files rely heavily on positioning (e.g., subtitles placed to identify speakers on left/right), that information is lost in SRT. For standard bottom-of-screen subtitles, nothing meaningful is lost.

Before You Start: Organize Your Files

Batch conversion goes smoothly with 30 seconds of prep:

1. Put all VTT files in one folder. Copy them (don’t move your only copies) into a dedicated folder like vtt-to-convert.
2. Check the filenames. The output SRTs will usually take the same base name (lecture01.vtt → lecture01.srt). If two files would produce the same output name, rename first.
3. Spot-check one file. Open one VTT in a text editor. Confirm it starts with WEBVTT and the timestamps look sane. If a file is malformed, the batch may skip it — better to know which one upfront.
4. Back up the originals. Keep the VTT files until you’ve verified the SRTs. Conversion is non-destructive when done right, but backups are free.

Method 1: Subtitle Edit Batch Convert (Easiest, No Code)

Subtitle Edit is a free, open-source subtitle editor for Windows, and its batch converter is the friendliest way to convert a folder of subtitles.

Step-by-step:

1. Open Subtitle Edit. Go to Tools → Batch convert.
2. Add your files. Click the add button (or drag and drop) and select all your VTT files — or point it at the whole folder.
3. Set the input format. It usually auto-detects VTT, but verify the format column shows WebVTT.
4. Set the output format to SubRip (SRT). This is the key setting — it’s a dropdown in the batch convert window.
5. Choose the output folder. Best practice: a new empty folder, so inputs and outputs don’t get mixed up.
6. Check the options. There’s typically an option for encoding — leave it on UTF-8 unless you have a reason to change it. You can also set filename patterns here.
7. Click Start/Convert. Subtitle Edit processes every file and reports any errors.

Why this method wins for most people: it’s visual, it shows you exactly what it’s doing, it handles encoding correctly, and it flags problem files instead of silently producing bad output. If you’ve never used a command line, start here.

Method 2: ffmpeg (Fastest for Large Batches)

ffmpeg is a free, open-source command-line multimedia tool. If you’re comfortable with a terminal (or willing to copy-paste one command), it’s the fastest way to convert hundreds of files.

Install ffmpeg: download from the official site (ffmpeg.org) for your OS. On Windows, there are easy builds; on Mac, brew install ffmpeg; on Linux, it’s in most package managers.

Convert a whole folder — open a terminal in the folder containing your VTT files and run:

On Mac/Linux:

for f in *.vtt; do ffmpeg -i "$f" "${f%.vtt}.srt"; done

On Windows (PowerShell):

Get-ChildItem *.vtt | ForEach-Object { ffmpeg -i $_.FullName ($_.BaseName + ".srt") }

That’s it. Each VTT becomes an SRT with the same base name, in the same folder. ffmpeg handles the timestamp conversion, strips the WEBVTT header, and numbers the cues.

Tips for ffmpeg batch conversion:

• Output to a separate folder by adding a path: "converted/${f%.vtt}.srt" (create the folder first).
• Overwrite protection: ffmpeg asks before overwriting existing files. Delete or move old SRTs first if you’re re-running.
• Check one file first. Convert a single file (ffmpeg -i lecture01.vtt lecture01.srt), inspect it, then run the loop on the rest.
• Weird filenames: the quoted "$f" in the loop handles spaces in filenames. Don’t remove the quotes.

Method 3: Free Online Converters (No Install)

If you only have a few files and can’t install software (a work computer, a Chromebook), online converters work:

1. Search for a VTT-to-SRT converter with batch/multi-file support — not all of them accept multiple files.
2. Upload your VTT files (check the site’s file-count and size limits first).
3. Convert and download the SRTs, usually as a ZIP.

Caveats worth knowing: upload speeds make this painful for large batches; free tiers often cap file counts; and you’re uploading your content to a third-party server — fine for public course subtitles, not fine for anything confidential. For more than a dozen files, installing Subtitle Edit (a two-minute job) pays for itself immediately.

Verifying Your Converted SRTs

Don’t trust a batch conversion blindly. Verify:

1. Count the files. The output folder should contain exactly one SRT per input VTT. Missing files mean something failed — check the converter’s error log.
2. Open one SRT in a text editor. Confirm: no WEBVTT header, timestamps use commas (00:00:01,000), sequence numbers run 1, 2, 3…, and there’s a blank line between blocks.
3. Check special characters. Open a file with accents, non-Latin scripts, or symbols. If they show as garbage, the encoding went wrong — reconvert with UTF-8 explicitly set.
4. Play one video with its SRT. The ultimate test: load an SRT alongside its video in VLC or any player and watch a minute. Subtitles should appear at the right times.
5. Compare cue counts. A quick sanity check: the number of subtitle blocks should match between the VTT and the SRT. A big discrepancy means cues were dropped — usually malformed input, occasionally a converter bug.

Common conversion issues and fixes:

• Dropped cues: usually a malformed VTT (missing blank lines, bad timestamps). Fix the VTT or convert that file individually.
• Wrong characters: encoding mismatch — reconvert specifying UTF-8 on both input and output.
• Timestamps shifted: rare, but some converters mishandle VTT files with header timestamps. Compare a few cues against the original.
• Empty output file: the input wasn’t valid VTT (sometimes a file with a .vtt extension is actually something else). Open it and look.

Frequently Asked Questions

Will I lose anything converting VTT to SRT?

You lose web-specific features: cue positioning, styling, and metadata comments. The dialogue text and timing — what actually matters for watching — convert perfectly. For standard subtitles, the SRT is functionally identical.

Can SRT be converted back to VTT later?

Yes, all three methods work in reverse. But note the conversion is one-way for the dropped features: positioning and styling info lost in the VTT→SRT step won’t magically reappear. Keep your original VTTs if you might need those features.

How many files can I convert at once?

Subtitle Edit and ffmpeg have no practical limit — hundreds or thousands of files work fine. Online converters usually cap at somewhere between 5 and 50 files per batch on free tiers. For large jobs, local tools are the answer.

Do I need to install anything to batch convert?

Not strictly — online converters need no install. But for anything beyond a handful of files, installing Subtitle Edit (free, two minutes) is dramatically faster and keeps your files on your own machine.

Why do some of my converted SRTs have wrong characters?

Encoding mismatch. VTT files are supposed to be UTF-8, but some are saved in other encodings. When converting, explicitly set UTF-8 for input and output. If characters are already garbled in the VTT itself, fix the source file first — conversion can’t recover what was already broken.

Is ffmpeg safe to download?

Yes, from the official source (ffmpeg.org) or your OS package manager. It’s one of the most widely used open-source multimedia tools in existence. Avoid random re-uploads on download aggregator sites — get it from the official builds.

Conclusion

Batch converting VTT to SRT is a solved problem — pick the method that matches your comfort level. Subtitle Edit’s batch converter is the sweet spot for most people: free, visual, and reliable. ffmpeg is unbeatable for huge batches if you don’t mind a terminal. Online converters fill the gap when you can’t install anything. Whichever you choose, organize your files first, verify the output (counts, encoding, a playback spot-check), and keep the original VTTs until you’re sure. Twenty minutes of methodical work beats an afternoon of converting files one by one.