Premiere Pro won’t import your .vtt captions
Premiere Pro won’t import VTT
Seen in: Adobe Premiere Pro
What is actually wrong
WebVTT is a web-player format. Premiere Pro’s caption importer reads SRT, SCC, MCC, EBU STL and DFXP, but not .vtt, so the file is either rejected outright or imports with nothing on the track. The cues themselves are fine; only the container syntax is wrong for Premiere.
Fix it here: VTT to SRT
Drop the file. It is detected and converted in your browser; nothing is uploaded. Free to start, no signup.
Convert a file now
Conversions …
Drop EDL, SRT, VTT, .prtranscript, or transcript files
Any caption, transcript or timeline file: CutConvert picks the converter and shows what survives · up to 100 KB per file
The fix, step by step
Drop the .vtt here
The converter reads the WEBVTT header, cue identifiers, timestamps and text, and ignores the styling blocks Premiere cannot use.
Download the SRT
You get a standard SubRip file with numbered cues and comma-separated milliseconds.
Import into Premiere
File > Import the SRT, then drag it above your sequence. Premiere builds a caption track with the original timing.
How VTT differs from SRT
WebVTT and SubRip look alike, and that is exactly why editors get stuck: the file opens, the cues are readable, and Premiere still refuses it. The differences are small but every one of them matters to a strict parser:
- VTT starts with a
WEBVTTheader line. SRT has no header. - VTT timestamps use a dot before the milliseconds (
00:01:02.500). SRT uses a comma (00:01:02,500). - VTT allows cue settings after the timing line (
align:start position:10%). SRT has nothing after the arrow. - VTT may include
NOTE,STYLEandREGIONblocks, and inline tags like<c.yellow>or<v Speaker>. SRT supports only a handful of HTML-style tags. - Cue numbers are optional in VTT and mandatory in SRT.
A find-and-replace of dots for commas gets you halfway and then breaks on the first cue with positioning or a voice tag. A converter handles all five differences at once.
Where the .vtt came from
Zoom cloud recordings, Vimeo, YouTube (choose the .vtt download), Descript, Rev, Otter and most transcription APIs hand you WebVTT because browsers play it natively. None of that helps in an NLE.
What the conversion keeps and drops
Timing is kept to the millisecond. Line breaks inside a cue are kept. Speaker voice tags are written into the text as a name prefix, so nothing is lost, and positioning and colour classes are dropped, because SRT has no place for them and Premiere would ignore them anyway. If you need the positioning to survive, the right destination is a caption XML or SCC workflow, not SRT.
Doing it without uploading the file
The conversion on this page runs in a Web Worker in your browser. The .vtt is read locally, the SRT is written locally, and the only thing that touches a server is a count of the conversion. For a client’s unreleased footage that is the difference between a tool you can use and one you cannot.
FAQ
- Will speaker names in the VTT survive?
- Yes. A <v Name> voice tag becomes a "Name:" prefix on the cue text, which Premiere shows as part of the caption.
- What happens to VTT styling?
- Colour classes, positioning and STYLE blocks are dropped. SRT has no way to carry them and Premiere does not read them from SRT.
- Does this work for Premiere Pro 2023 and earlier?
- Yes. SRT import has been in Premiere since caption support moved to the Text panel, and the SRT written here is the plain, tag-free form every version reads.