Toolsky

Free Online Tools & Utilities for Every Task.

SRT to VTT Converter

Easily convert SRT subtitle files to WebVTT format for web video compatibility.

Conversion successful! You can now download your VTT file.
Technical Conversion Standards
  • Mandatory WEBVTT header is added to the top of the file.
  • Timecode separators are converted from commas (,) to dots (.) for VTT compliance.
  • Subtitle indices are preserved to maintain track structural integrity.
  • UTF-8 encoding is enforced for maximum player compatibility.

Your video editor, captioning service or transcription tool exported the subtitles as an SRT file — and then you tried to attach them to a video on your own website and hit a wall. The HTML5 video player built into every browser does not accept SRT. It wants WebVTT, a close cousin with a different header, different timestamp punctuation and a few extra abilities. An SRT to VTT converter performs that translation for you: upload the SRT, download a WebVTT file your web video can actually use.

What Changes When SRT Becomes WebVTT

The two formats carry the same information — a numbered sequence of cues, each with a start time, an end time and one or more lines of text — but they write it differently. SRT separates the seconds and milliseconds in its timestamps with a comma (00:01:02,500); WebVTT, defined by the W3C's WebVTT specification, uses a full stop (00:01:02.500). WebVTT files must also open with the word WEBVTT on the first line, a header SRT does not have. Beyond the syntax, WebVTT is built for the web: it works with the HTML track element, supports styling and positioning information, and can carry chapters and metadata alongside captions. The converter handles the punctuation swap and the header automatically, line by line, without disturbing your timings or your text.

What the Converter Handles

  • Every cue in the file — the full sequence is translated, timings preserved to the millisecond.
  • Timestamp conversion — comma decimal separators become the periods WebVTT requires, throughout the file.
  • The mandatory WEBVTT header — added at the top so browsers accept the file as valid WebVTT.
  • Your text, untouched — the words, line breaks within cues and the reading order stay exactly as you wrote them.
  • A clean .vtt output file — ready to reference from a track element alongside your video file.

How to Convert an SRT File to VTT

  1. Locate the finished SRT file — check it is the final version, since the conversion will faithfully preserve any mistake in it.
  2. Upload the .srt file to the converter.
  3. Run the conversion and download the resulting .vtt file.
  4. Place the VTT file on your server alongside (or near) the video it belongs to.
  5. Attach it to your video with a track element, marking it as subtitles or captions and setting its language — for example, an English track labelled for your viewers.
  6. Play the video in a browser with captions switched on and spot-check a few cues at the beginning, middle and end against the audio.
  7. If you ever need the reverse journey for an editing tool, the VTT to SRT converter takes files back the other way.

Example: One Cue, Before and After

The translation is easiest to see on a single caption. In the original SRT file, cue twelve reads:

12
00:01:02,500 --> 00:01:05,000
And that is how you knead the dough.

After conversion, the same moment appears in the VTT file as:

WEBVTT

00:01:02.500 --> 00:01:05.000
And that is how you knead the dough.

The spoken words arrive at exactly the same instant — 62.5 seconds in — and leave at the same moment. Only the notation changed: the cue number is no longer required, the commas became full stops, and the file declares itself with the WEBVTT header. Multiplied by the few hundred cues in a typical video, that is a conversion nobody should be doing by hand with find-and-replace, because one missed comma produces a file the browser silently ignores. If instead your workflow needs the text burned permanently into the picture, hardcoding subtitles is the other route — each approach has its place.

Subtitle Conversion Gotchas Worth Knowing

Encoding causes the most confusing failures. Subtitle files with accented characters, non-Latin scripts or smart punctuation must be saved as UTF-8; a VTT file in an old Windows encoding will show garbled characters on the web even though the conversion was perfect. Check a cue containing an é, an ü or an Arabic or Urdu line after converting. Styling is the second gotcha: SRT's loose support for basic tags like bold and italics mostly survives, but positioning tricks and font tags from SRT have no exact WebVTT equivalent and may be dropped or ignored — a fair trade, since WebVTT has its own styling system. Third, conversion cannot repair timing: if the SRT drifted out of sync because it was made for a different cut of the video (a common problem with files made for a 25 fps version used on a 23.976 fps master), the VTT will be faithfully, uselessly out of sync too. Fix sync in an editor first, then convert. Finally, validate by playing: browsers fail silently on malformed VTT, so one broken timestamp can disable the whole track without any error message.

Frequently Asked Questions About Converting SRT to VTT

Why won't browsers just accept my SRT file?

Because the HTML standard specifies WebVTT as the text-track format for the track element, and browsers implemented that specification. SRT remains the common format of editing and captioning tools, which is why conversion is a standard step in web publishing.

Does the conversion change my subtitle timings?

No. Every cue's start and end are carried across to the millisecond; only the notation changes, from comma to full-stop decimal separators. If the converted file seems out of sync, the original SRT was made for a different version of the video.

Will I lose formatting like bold or italics?

Basic emphasis tags generally carry over, since WebVTT supports equivalents. SRT-specific positioning and font colour tags may not survive, because WebVTT handles appearance through its own cue settings and CSS instead.

What is the track element, and do I need it?

Yes — it is the HTML element that connects a subtitle file to a video. It sits inside the video element and names the VTT file, its kind (subtitles or captions), its language and the label viewers see in the player's menu.

Can WebVTT do things SRT cannot?

Several: cue styling and positioning, chapter markers for navigation, and metadata tracks. For plain subtitles the two formats are equivalent in what the viewer sees, but WebVTT is the one the web platform builds on.

Why do accented characters appear garbled after conversion?

Almost always an encoding mismatch: the original file was saved in a legacy encoding rather than UTF-8. Re-save the SRT as UTF-8 in a text editor and convert again; the characters will come through correctly.

Do I need to renumber the cues?

No. WebVTT does not require cue numbers at all — identifiers are optional — so the converter handles their removal or retention without affecting playback.

Subtitles Your Web Player Can Actually Read

Captions are finished work only when the audience can switch them on. Converting SRT to WebVTT is a small, mechanical step, but it is the one that stands between a subtitle file sitting in a folder and subtitles actually appearing on your website's videos.