Premiere Pro VP09 Not Compatible: Fix for YouTube Files

What does “unsupported compression type VP09” mean?#

Premiere’s VP09 error means the file uses the VP9 codec, which Premiere does not import natively. VP09 is not a file type: vp09 is the four-character code that labels a VP9 video track inside an MP4, as defined in the VP Codec ISO Media File Format Binding.

VP9 is the WebM Project’s open video codec, and YouTube uses it for delivery. Premiere Pro reads the MP4 container and the vp09 track label, but VP9 is missing from the formats Adobe lists for Premiere Pro, so the import stops there.

Premiere import errors on YouTube files come in a few wordings. The table pairs each message with what is inside the file and the fix.

Why do YouTube files trigger the VP09 error in Premiere?#

YouTube files trigger the VP09 error because YouTube delivers video in VP9 and AV1 as well as H.264. As of September 2026, a download of YouTube’s best streams usually holds VP9 or AV1 video with Opus audio.

The file extension hides that. A downloader merges the video and audio streams into whatever container you chose without re-encoding them, so an .mp4 can carry VP9 just as a .webm does. Which codec a given video gets depends on the video and its resolution, as YouTube codecs explained: H.264 vs VP9 vs AV1 lays out.

B-ROLL has no codec setting: its MP4, MKV and WEBM keep the codec of the streams yt-dlp picks. Renaming a .webm to .mp4, or rewrapping it without re-encoding, changes the box and leaves the VP9 inside, which is why the container swap alone never fixes the error. How the four containers behave in an editor is compared in MOV vs MP4 vs MKV vs WEBM for video editing.

Premiere is not alone: on Ema Zamboni’s own DaVinci Resolve timeline, AV1 or VP9 downloads crashed Resolve at times, the problem B-ROLL’s automatic conversion was built to solve.

What is the quickest fix for the VP09 error?#

The quickest fix for the VP09 error is to replace the file with a ProRes or DNxHR .mov, a codec pair that Premiere Pro imports natively on Windows. You get one either by downloading the video again with B-ROLL’s ProRes or DNx format, or by converting the file you already have.

Download it again with B-ROLL. Switch Format to ProRes or DNx and click ↻ on the finished card: B-ROLL downloads the video again with the current settings, then converts it to a .mov. Download YouTube videos in ProRes or DNxHR explains the tier B-ROLL picks.

Convert the file you have. When the link is gone, convert the VP9 file with ffmpeg, the same tool B-ROLL runs for its own conversions. The command writes a DNxHR SQ .mov with uncompressed audio:

ffmpeg -i "clip.mp4" -c:v dnxhd -profile:v dnxhr_sq -pix_fmt yuv422p -c:a pcm_s16le "clip_dnxhr.mov"

A conversion decodes VP9 and encodes a new picture, so it adds a generation of compression. Converting once, straight after the download, keeps it to that single step.

How do you check a YouTube file’s codec before importing it into Premiere?#

Check a YouTube file’s codec by reading its stream line with ffmpeg: Windows file properties do not show it, and B-ROLL’s cards show bitrate and resolution only. The line names the codec and its four-character code.

ffmpeg -hide_banner -i "clip.mp4"

ffmpeg lists each stream, then ends with a harmless note that no output file was given. For a VP9 file the video line contains Video: vp9 and (vp09 / 0x39307076), and the audio line contains Audio: opus. The vp09 in that line is the same label Premiere reports. An avc1 or h264 video line with aac audio is a file Premiere Pro can usually open as it is.

B-ROLL installs its own ffmpeg.exe in %LOCALAPPDATA%\Broll. Run the command from that folder, or with the full path, when ffmpeg is not on your PATH.

Which B-ROLL settings avoid the VP09 error?#

The B-ROLL setting that avoids the VP09 error is Format: choose ProRes or DNx, never MP4, MKV or WEBM, for anything that goes into Premiere Pro. B-ROLL’s MP4 can contain VP9, so only the converted .mov is a safe import.

With ProRes or DNx selected, B-ROLL merges the best streams into an MKV master, converts it with ffmpeg into a .mov with the same name, and deletes the master when the conversion succeeds. The .mov keeps the source resolution and frame rate and carries 16-bit PCM audio, so the Opus problem disappears along with the VP9 one.

Two more settings save time. Quality caps the height (Best, 4K, 1080p, 720p, 480p), so match it to your sequence. Only a part: ask me which each time in Advanced options downloads just the range you mark, and the conversion then runs on seconds instead of a whole video. Different settings count as a new download, so switching the format never stops at the Already downloaded dialog.

The full Premiere workflow, from the format choice to the sequence settings, is in download YouTube videos for Premiere Pro and After Effects.

Why does an MKV import without audio in Premiere?#

An MKV from YouTube imports without audio because its sound is Opus, an audio codec missing from Adobe’s list for Premiere Pro. Matroska is not on that list either, so Premiere Pro handles an MKV only partly, if at all.

YouTube pairs VP9 and AV1 video with Opus audio in most of its streams, and B-ROLL’s MKV keeps both as they are. The same happens with an MP4 whose video Premiere can decode but whose audio is Opus: the picture arrives, the audio track does not.

Rewrapping the MKV as an MP4 leaves the Opus stream untouched and gives the same silent clip. A ProRes or DNxHR .mov from B-ROLL carries uncompressed 16-bit PCM audio instead. If the same YouTube file also fails in DaVinci Resolve, DaVinci Resolve media offline on a YouTube video covers the Resolve side, and every other download and import error is collected in YouTube downloader not working? Fixes for editors.