Skip to content
Pixora

VTT to SRT Converter

Processed locally in your browser — nothing is uploaded.

Quick answer

To convert VTT to SRT you remove the WEBVTT header, change each timestamp’s period to a comma (00:01:02.500 → 00:01:02,500), number the cues, and drop any WebVTT cue-positioning settings that SubRip cannot represent. This tool does all of that in your browser and hands back a clean .srt file for VLC, YouTube and desktop players. No file ever leaves your device.

How to vtt to srt converter

  1. Load your VTT file

    Drag a .vtt file in or paste WebVTT text. The tool recognises the WEBVTT header automatically.

  2. Convert to SubRip

    It strips the header and cue settings, renumbers the cues from 1, and switches timestamps to the comma form SubRip uses.

  3. Save the SRT

    Download the .srt file or copy it, ready for VLC, Premiere, or a YouTube caption upload.

Why convert VTT back to SRT?

WebVTT is the web’s format, but a lot of the world still runs on SubRip. Desktop players expect .srt sidecar files, most editing suites import SRT more reliably than VTT, and plenty of TV and set-top players only read SubRip. If you pulled a .vtt from a streaming page or an HTML5 player and now want it to “just work” in VLC or on a USB stick plugged into a TV, SRT is the safe target.

What gets lost converting VTT to SRT?

SubRip is a simpler format, so a downconversion necessarily drops anything VTT could express that SRT cannot:

  • Cue positioningline:, position:, align: and size: settings that place a caption on screen. SRT has no concept of position.
  • Regions and `::cue` CSS styling — WebVTT’s advanced layout is discarded.
  • Voice and class spans<v Bob> speaker tags are flattened to plain text.

What is fully preserved is the part that matters most: the cue text and the exact timing. Basic <i> and <b> tags are kept because SubRip tolerates them too.

VTT features and whether SRT can hold them.
WebVTT featureSurvives in SRT?
Cue text and line breaksYes
Start/end timingYes (exact)
Italic / bold tagsYes
Cue position & alignmentNo
Regions / ::cue CSSNo
<v> speaker voicesFlattened to text

Does the VTT file get uploaded?

No. Everything happens locally in your browser — the WebVTT is parsed and rewritten in memory, with no network request. Open DevTools → Network and watch: converting a file sends nothing. Captions for confidential footage stay on your machine.

Need to go from SRT to VTT for a web player instead? Use SRT to VTT. For any other pair, the universal converter covers ASS, SBV and TTML. If the file is out of sync once converted, the subtitle shifter fixes the offset, and you can burn the subtitles into the video when you are done.

Your files never leave your device

Processed locally in your browser — nothing is uploaded. You can verify it yourself: open your browser’s developer tools, watch the Network tab, and use the tool — no upload request is ever made.

Frequently asked questions

Will VTT to SRT change my subtitle timing?

No. Timing is copied exactly; only the decimal separator changes from a period to a comma and cue numbers are added.

Why did my caption positions disappear?

SubRip has no way to store on-screen position. WebVTT cue settings like line: and align: are dropped because there is nowhere in the SRT format to put them.

Does the converter add cue numbers automatically?

Yes. WebVTT cue numbers are optional, but SubRip expects a number before each cue, so the tool renumbers everything from 1.

Can I upload the resulting SRT to YouTube?

Yes. YouTube accepts SubRip .srt files for captions. The converted file is standard SRT.

What happens to speaker tags like <v Bob>?

They are flattened — the name is removed and only the spoken text remains, since SRT has no voice/speaker markup.

Is there a file size or count limit?

No practical limit. Subtitle files are small text, and because processing is local there is no server quota to hit.