SRT to VTT Converter

Convert SRT subtitles to WebVTT for HTML5 video. Fixes broken accents, checks for errors and lets you preview the result on your own video.

  • Free, no sign-up
  • Files never leave your browser
  • No size limit
  • Several files at once

How to convert SRT to VTT

  1. Add your SRT files

    Drop them on the converter, browse, or paste the text. Several files at once work too.

  2. Check the result

    Read what changed, fix any reported problems and preview the subtitles on a video.

  3. Download the VTT

    Save one .vtt file or a ZIP of all of them, and add it to your player with a <track> element.

SRT and WebVTT, explained

Both are plain-text subtitle files: a list of timings, each followed by the text to show. They differ in where they work and in what they can do.

SRT SubRip Subtitle, .srt

The oldest and most widespread subtitle format. It comes from SubRip, a program that copied subtitles from DVDs around 2000. Each subtitle has a number, a timing line and one or two lines of text.

Strengths

  • Read almost everywhere: desktop players such as VLC, video editors, YouTube, Vimeo and Facebook.
  • Simple to read and edit in any text editor.
  • The format most translators and subtitling services deliver.

Limits

  • Browsers can’t play it: HTML5 video only accepts WebVTT.
  • No official standard, so files vary. Older ones are often not saved as UTF-8, which breaks accents.
  • No standard way to place or style subtitles beyond italics, bold and underline.

Best for: video platforms, editing software, translation.

WebVTT Web Video Text Tracks, .vtt

The subtitle format of the web, standardized by the W3C. It’s based on SRT, with a WEBVTT header, a dot before the milliseconds and extra features for web players.

Strengths

  • Built into browsers: HTML5 video players read it, Fluid Player included.
  • Can place subtitles (top, middle, left, right) and style them with CSS.
  • Always UTF-8, and can hold speaker names, comments and chapters.

Limits

  • Some editing software, TVs and platforms still only accept SRT.
  • Stricter: with a missing header or a badly written timestamp, the browser silently shows nothing.
  • Positions and styles don’t look the same in every player.

Best for: websites and HTML5 video players.

Which one should you use? For a website, WebVTT: it’s the only format browsers play. For anything else, such as YouTube, a video editor or a translator, SRT is the safe choice. This converter switches between the two at any time.

SRT vs VTT: what changes

subtitles.srt
1
00:00:01,200 --> 00:00:03,800
Once upon a time…
subtitles.vtt
WEBVTT

1
00:00:01.200 --> 00:00:03.800
Once upon a time…

A WebVTT file starts with WEBVTT, uses a dot instead of a comma before the milliseconds and must be saved as UTF-8. That’s why renaming a .srt file to .vtt isn’t enough.

Subtitles not showing?

  • Your server sends the file with the text/vtt content type.
  • The file is on the same domain as the page, or its server allows cross-origin requests (CORS).
  • The file starts with WEBVTT and is saved as UTF-8.
  • You’re testing through a web server: browsers don’t load subtitles for a page opened as a local file.
  • In Fluid Player, the track uses kind="metadata" and subtitlesEnabled is on.

Questions

Is my file uploaded anywhere?

No. The conversion runs in your browser, on your device. Nothing is sent to us or anyone else: you can check it in the network tab of your browser’s developer tools. A video you pick for the preview also plays from your computer.

Can I just rename .srt to .vtt?

No. A WebVTT file must start with a WEBVTT line and use a dot instead of a comma before the milliseconds (00:00:01.200). Browsers ignore a renamed SRT file without showing an error.

Why do accents look broken in my subtitles?

Many older SRT files are saved in a Windows encoding (Windows-1252 for Western European languages) instead of UTF-8, which WebVTT requires. Read with the wrong encoding, “é” turns into “é” or “�”. The converter detects the encoding and converts the text to UTF-8. If the result still looks wrong, pick the right encoding in the Encoding menu, which appears when you add a file.

Will italics and positions be kept?

Yes. Italics, bold and underline are kept, and position tags such as {\an8} (subtitles at the top) become WebVTT positions instead of being deleted. Font colors from <font> tags are removed, because WebVTT sets colors with CSS. The “What changed” list shows everything that was changed or removed.

My subtitles are out of sync. Can I fix that?

Yes. If every subtitle is early or late by the same amount, enter the difference in milliseconds in Shift timing (a minus sign shows them earlier). If they drift further and further out of sync, the subtitles were made for another frame rate: pick the right pair in Frame rate, such as 23.976 to 25 fps.

Can I convert VTT back to SRT?

Yes, with the VTT to SRT Converter. The VTT → SRT switch above the converter takes you there with your subtitles.

How do I add the VTT file to Fluid Player?

Add a <track> element with kind="metadata" inside your <video> tag and set subtitlesEnabled: true in the player options. The code under the preview is ready to copy. See Subtitles in the Fluid Player documentation (opens in a new tab) for all the options.

More free tools

  • VTT to SRT Converter

    Convert WebVTT subtitles to SRT for YouTube, video editors and media players. Keeps positions, checks for errors and previews the result.

  • Player Builder

    Set up Fluid Player visually, with video ads, subtitles and your colors, and copy ready-to-use code.