Convert VTT to SRT Online

How to convert VTT to SRT

Converting takes a few seconds and never involves a server. Follow these steps:

1. Drop your VTT file — Drag the .vtt file onto the box above, or click to browse. The file stays on your device; nothing is uploaded to any server.
2. Confirm the format and encoding — Badges show the detected format and encoding. WebVTT files are normally UTF-8, but captions saved on Windows may use GBK or Windows-1252 — those are detected automatically so accented and Chinese characters survive.
3. Shift the timing if needed — Enter a value in seconds in the Time shift field if captions appear too early (negative) or too late (positive) against the video.
4. Convert — Click Convert to SRT. Cue settings, NOTE blocks and CSS markup that SRT cannot store are removed, and each timestamp is rewritten with a comma before the milliseconds.
5. Preview and download — Check the preview for correct characters and timing, then click Download to save the .srt file next to your original.

What is a VTT file?

VTT (WebVTT) is the W3C caption format designed for the web. It must begin with a WEBVTT header line, and its cues use a dot for milliseconds (00:01:23.456 --> 00:01:26.456). Beyond plain text, WebVTT supports optional cue identifiers, cue settings such as line, position, align and size, limited inline markup for bold and italics, voice spans for speaker labels, and NOTE blocks for comments. Because browsers implement it natively through the <track> element, it is the format of choice for HTML5 video, course platforms and most streaming pipelines.

What is a SubRip file?

SRT (SubRip Subtitle) is the plainest and most universally accepted subtitle format in existence. Each cue consists of a sequence number, a start --> end line using a comma for milliseconds (00:01:23,456 --> 00:01:26,456), the text itself, and a blank line. It has no styling, no positioning and no metadata. That lack of features is precisely its strength: professional editors, hardware players, smart TVs, USB media sticks and burning tools such as HandBrake and FFmpeg all read .srt reliably.

VTT vs SRT: what actually changes

Here is exactly what the conversion alters and what it preserves, so there are no surprises when you play the result:

Why convert VTT to SRT?

WebVTT is the web's native caption format, but most desktop and hardware software still expects SRT. Converting VTT to SRT removes the cue settings, notes and CSS hooks that SRT cannot store, keeping exactly the text and timing. As long as your captions were plain text without positioning, nothing meaningful is lost.

Common use cases

Editing in Premiere, DaVinci or Final Cut

Professional editors import SRT far more reliably than VTT. Converting first avoids import errors and keeps the caption track editable on the timeline.

Burning captions into a video

Tools such as HandBrake, FFmpeg and most cloud encoders take SRT as the subtitle input. Converting gives you a file those tools accept without extra flags.

Playing on a TV or USB stick

Smart TVs, set-top boxes and USB media players almost universally read .srt. WebVTT support on those devices is inconsistent at best.

Delivering captions to a client

SRT remains the safest delivery format because it opens everywhere. Sending a VTT risks a support email from a client whose player cannot read it.

Tips and troubleshooting

Keep the VTT as your master

Cue positioning and styling cannot come back once they are removed, so archive the original .vtt before overwriting anything.

Positioned captions will move to the bottom

Any cue that used line or position settings renders in the default bottom-centre area after conversion. Re-add placement manually if the original layout mattered.

Styling disappears

Colours, italics applied through ::cue and voice spans are not representable in SRT and are stripped. The words and their timing remain.

Fix drift before converting

Apply the Time shift while converting so you only download one corrected file instead of re-syncing later in an editor.

Naming your subtitle files so players find them

Most desktop and mobile players load a subtitle file automatically when two conditions are met: the subtitle sits in the same folder as the video, and both files share the same base name. A video called movie.mp4 is matched by movie.srt, movie.en.srt or movie.en.forced.srt, but not by subtitles.srt or movie (1).srt. The language code in the middle is optional and is used by players that offer a subtitle track menu.

If captions do not appear, the problem is almost always the file name rather than the file contents. Rename the subtitle to match the video exactly, or use the player's subtitle menu to load it manually once. On macOS, Total Video Player Pro goes a step further and matches subtitle files to your video automatically, including subtitle tracks already embedded inside MKV and MP4 files.

Using the converted SRT file

Name the .srt exactly like your video and place it in the same folder — movie.srt beside movie.mp4 — and most players load it automatically, including VLC, IINA and Total Video Player Pro for Mac. If it does not appear, open the player's subtitle menu and choose "Add subtitle file", or check that the two files really share the same base name.

In Premiere Pro and DaVinci Resolve you can import the .srt as a caption track and edit the text directly on the timeline. To burn the captions permanently into a video, the usual tools are HandBrake's Subtitles tab or FFmpeg: ffmpeg -i movie.mp4 -vf subtitles=movie.srt out.mp4. Because SRT carries no styling, the appearance is decided by whichever player or encoder renders it.

Privacy: nothing leaves your browser

Most online subtitle converters work by uploading your file to a server, processing it there and letting you download the result. That approach has three practical drawbacks: your subtitle text passes through someone else's machine, you wait for the upload and the download, and the service can impose file size limits, queues or watermarks.

This converter does none of that. It is built with JavaScript and runs inside your browser tab. When you drop a VTT file, the browser reads it from your disk, parses it in memory, converts it to SRT and hands the result straight back to you — no network request ever carries your content. That has a useful side effect: there is no queue, no server-side size limit and no watermark, and the tool keeps working even if you lose your connection after the page has loaded. If you handle unreleased footage, confidential transcripts or anything you would rather not share with a third party, local processing is the safer default.

Frequently asked questions