SRT to VTT Converter

Subtitles arrive in two common flavours. SRT is the classic desktop format, while VTT is the format HTML5 video players expect on the web, and the two differ in small but strict ways: VTT needs its header line, and its timestamps use dots instead of commas. Converting by hand is tedious and error-prone across a long file.

This converter handles the mechanical parts for you. Paste SRT text, and it adds the WEBVTT header, rewrites every timestamp line from commas to dots, and leaves the subtitle text and numbering untouched, so the result drops straight into a video element.

Quick Answer: Turn SRT subtitle text into valid WebVTT for use with HTML5 video.

Free Online Tool

Paste SRT subtitles and convert them to WebVTT.

SRT subtitles

How to Use the SRT to VTT Converter

Enter or upload your input in the box above.
Check the settings match what you need before you run it.
Press the main button to run the conversion.
Review the result shown below the controls.
Copy the result or download it, then use it wherever you need it.

Key Features

Runs entirely in your browser, so nothing is uploaded to a server.
No account, sign-up, or installation is needed to use it.
Works on desktop and mobile browsers alike.
Adds the required WEBVTT header automatically.
Rewrites timestamp commas to dots on every cue line.
Keeps subtitle text and cue order exactly as pasted.

Best Practices and Tips

Double-check your input before running the tool, since the output is only as good as what you enter.
Keep a copy of the original input until you have confirmed the result works.
Check that your SRT uses the standard arrow format before converting.
Save the result with a .vtt extension so players recognise it.
Test the file in a browser video player before publishing.

Common Mistakes to Avoid

Running the tool on incomplete input and trusting the first result without a glance.
Forgetting to save or copy the output before closing the tab.
Forgetting the WEBVTT header, which makes browsers reject the file.
Leaving commas in timestamps, which VTT parsers treat as invalid.

Frequently Asked Questions

What does the SRT to VTT Converter do?

The SRT to VTT Converter takes SRT subtitle text and turns it into valid WebVTT subtitle text, right in your browser. You do not need to install anything or create an account, and the result is ready in seconds. It is built for everyday jobs where you want a quick, reliable answer without opening a heavy desktop program or uploading your files anywhere.

Is my input private when I use this tool?

Yes. Everything you type, paste, or upload is processed locally in your own browser tab, so it never travels to a server run by this site. The only exception is a feature that explicitly needs a device, such as a camera or microphone, and even then the media stays on your device. Closing the tab ends the session, and nothing about your input is stored on the site.

What should I do if the result looks wrong?

First, check the input for typos, missing values, or an unsupported format, because most unexpected results come from the input rather than the tool. Try a small, simple example you can verify by hand, then compare it with the tool output. If the simple case works and the real case does not, the difference usually points to the part of the input that needs fixing.

What is the difference between SRT and VTT?

SRT is a plain subtitle format used by desktop players, while VTT is designed for the web and supports styling and positioning. The core difference for conversion is the WEBVTT header and the dot-based timestamps, both of which this tool fixes for you.

Can I convert VTT back to SRT?

The reverse conversion is mostly removing the header and swapping dots back to commas in timestamps. This tool is built for the SRT-to-VTT direction, which is the one web publishing usually needs.

Can I use this tool on a mobile phone?

Yes. The tool is built with the same responsive layout as the rest of the site, so controls, inputs, and results adapt to a phone screen. Buttons are large enough to tap comfortably, text fields accept mobile keyboards, and results wrap instead of overflowing. If a feature needs a device capability, such as a camera, the tool will say so on that device rather than failing silently.