Toolsky

Free Online Tools & Utilities for Every Task.

VTT to SRT Converter

Convert WebVTT subtitle files to the widely supported SRT format for offline video players.

Conversion successful! You can now download your SRT file.
Technical Conversion Standards
  • Strips mandatory WEBVTT header and metadata blocks.
  • Converts timecode separators from dots (.) to commas (,) for SRT compliance.
  • Restructures cues into the standard SubRip numbering format.
  • UTF-8 encoding is maintained for maximum player compatibility.

WebVTT is the caption format of the HTML5 web, but step outside the browser and support thins out fast. Many desktop media players, set-top boxes, older smart TVs and video-editing tools still expect the older SRT format instead. The VTT to SRT Converter rewrites a WebVTT subtitle file as a clean SubRip (.srt) file so your captions keep working in offline players and editing software.

How WebVTT and SRT Differ

Both formats store the same essential information — subtitle text with a start and end time — but they write it differently. A WebVTT file must begin with a WEBVTT header line, and its timestamps use a period before the milliseconds: 00:01:02.500. SRT has no header, numbers each cue in sequence, and uses a comma: 00:01:02,500. That comma-versus-period detail is exactly why a VTT file renamed to .srt usually fails to load.

WebVTT also supports things SRT does not: cue settings for position, styling through CSS-like tags, voice spans that label speakers, and comment blocks beginning with NOTE. SRT is plain by design — sequence number, time range, text, blank line. Converting therefore means keeping the text and timing faithfully while letting the web-only extras go. The W3C WebVTT specification documents the full source format if you need the technical detail.

Features of the VTT to SRT Converter

  • Correct timestamp translation: periods become commas and every cue is renumbered in SRT sequence automatically.
  • Header handled: the WEBVTT header and NOTE comment blocks are removed, as SRT requires.
  • Timing preserved: cue start and end times carry across unchanged, so subtitles stay in sync with the audio.
  • Plain-text output: a standard .srt file that offline players, editors and subtitle tools can open directly.

How to Convert a WebVTT File to SRT

  1. Locate your .vtt file — for example, captions downloaded from an online course platform or exported from a web video tool.
  2. Upload or select the file in the converter.
  3. Start the conversion.
  4. Download the resulting .srt file.
  5. Give the SRT the same filename as your video (for example, lecture.mp4 and lecture.srt) so players load it automatically.
  6. Play a few minutes of the video to confirm the captions appear and stay in sync.

Worked Example and Typical Situations

A single cue shows the whole transformation. In WebVTT it appears as:

00:00:12.500 --> 00:00:15.000
Welcome back to the workshop.

After conversion, the SRT version reads:

7
00:00:12,500 --> 00:00:15,000
Welcome back to the workshop.

The text and timing are identical; only the punctuation, the added sequence number and the missing header changed. This is the conversion you need when a university lecture platform only offers VTT downloads but you watch offline in a desktop player, when an editor imports SRT but not VTT, or when archiving a video library in the most widely supported subtitle format. If your workflow runs the other way — publishing SRT captions to the web — the reverse SRT to VTT Converter handles that direction, and if you want subtitles permanently baked into the picture instead, the subtitle hardcoding tool is the relevant option.

What Gets Lost, and What Goes Wrong, in Conversion

Styling and positioning are lost. SRT cannot express VTT's colours, fonts, cue positioning or karaoke-style timing. Speaker labels written as voice spans are flattened to plain text. If a caption file depends on those features, expect a plainer result.

Keep the encoding as UTF-8. Accented characters and non-Latin scripts survive conversion when the file stays in UTF-8. If captions show garbled characters in a player, the player is usually misreading the encoding rather than the converter corrupting the text.

Check for overlapping cues. Sloppily authored VTT sometimes contains cues whose times overlap. SRT players handle overlaps inconsistently, so a quick skim of the output around dense dialogue is worthwhile.

Filenames must match. The most common "conversion didn't work" report is actually a naming problem: the .srt file must share the video's filename and sit in the same folder for most players to pick it up automatically.

Multi-line cues and reading speed carry over as-is. Conversion changes the container, not the captioning quality. If the VTT packed three long lines into a one-second cue, the SRT will demand the same impossible reading speed. Dense passages in the source are worth a skim after conversion, especially for children's content or language learners, so you can spot cues that flash past before anyone can read them.

Frequently Asked Questions About VTT to SRT Conversion

Can I just rename a .vtt file to .srt?

No. The header line, the period in the timestamps and the missing cue numbers all break SRT parsers. A real conversion rewrites those elements; a rename changes nothing but the extension.

Will the subtitle timing stay in sync after conversion?

Yes. Start and end times are carried across unchanged — only their punctuation is rewritten — so captions remain aligned with the audio exactly as they were in the VTT file.

What happens to colours and positioning in my VTT file?

They are dropped, because SRT has no way to represent them. The words and timings remain; visual styling, cue placement and speaker voice tags are simplified to plain text.

Which players need SRT instead of VTT?

Many desktop players, older smart TVs, set-top boxes and several video editors either prefer SRT or support only SRT. VLC and most modern software accept both, but SRT remains the safer common denominator.

Does the converter translate my subtitles into another language?

No. It changes the file format, not the language. The caption text comes out word-for-word as it went in.

My SRT shows strange characters instead of accents. Why?

That is an encoding mismatch. Make sure the output is saved and opened as UTF-8; players set to a legacy regional encoding will misread accented characters even in a perfectly converted file.

Can I convert the SRT back to VTT later?

Yes — timing and text convert back cleanly. What cannot be recovered is the styling and positioning information that SRT never stored, so keep your original VTT if you may need those again.

Captions That Play Anywhere

SRT is the subtitle format with the widest reach beyond the browser. Converting your WebVTT files takes seconds and means the captions you already have will work in the players and editors your audience actually uses offline.