YouTube Video Choppy in DaVinci Resolve? AV1 and VP9 Fix

Why is YouTube footage choppy in DaVinci Resolve?#

YouTube footage is choppy in DaVinci Resolve because the downloaded file usually holds AV1 or VP9 video. Both are long-GOP delivery codecs, built to stream small, not to be scrubbed on a timeline.

The codec comes from the download tool, not from your project. The yt-dlp README ranks video codecs in the order av01, vp9.2, vp9, h265, h264 once resolution, frame rate and HDR tie. As of September 2026, that ranking means an MP4 from YouTube usually carries AV1 or VP9 video with Opus audio, whatever app ran yt-dlp.

AV1 is the royalty-free codec published by the Alliance for Open Media, and VP9 is the WebM Project codec that came before it. A long-GOP codec stores complete frames only at intervals and describes the rest as changes. To show one frame, Resolve decodes a chain of others, so scrubbing, reverse play and J K L shuttling multiply the work. The mechanism is laid out in why H.264 and AV1 are hard to edit.

Ema Zamboni, the video editor who built B-ROLL, met this on a DaVinci Resolve Studio timeline on Windows 11. 4K60 AV1 footage downloaded from YouTube was heavy to play back, and AV1 or VP9 downloads crashed Resolve at times. B-ROLL’s automatic ProRes and DNxHR conversion was built to solve exactly that.

The fixes differ in effort and in how long they last. The table compares the five options an editor has, from a one-time conversion to a playback setting.

How do you check the codec of a clip in Resolve?#

Check the codec in DaVinci Resolve’s Media Pool before you change any setting: switch the Media Pool to list view and read the Video Codec column. The Metadata panel shows the same codec, plus resolution and frame rate, for the selected clip.

The codec name tells you which fix you need. Each entry gives what the name means for playback on Windows, according to Blackmagic Design’s supported codec list for DaVinci Resolve 20 (July 2025), and what to do.

• AV1: decodes in MOV, MP4 and MKV, GPU accelerated. Playback depends on your graphics card; edit a DNxHR or ProRes copy.
• VP9: decodes in MOV and MP4, and inside MKV. WebM is not in the list of supported formats; edit a DNxHR or ProRes copy.
• H.264: decodes 8-bit profiles that Windows supports, with more profiles and GPU acceleration in Studio. Still long-GOP; a copy scrubs better.
• DNxHR or ProRes: intraframe and already edit-ready. If these stutter, look at the grade, effects or disk speed instead of the codec.

B-ROLL helps with the other half of the diagnosis. Every card shows the real bitrate and resolution of the finished file, for example “Real bitrate 8.2 Mbps · 1080p”, but not the codec. A low bitrate does not mean an easy decode: a small AV1 file still asks for the full long-GOP work. How the three YouTube codecs differ is in YouTube codecs explained: H.264 vs VP9 vs AV1.

What is the lasting fix for choppy AV1 in Resolve?#

The lasting fix for choppy YouTube footage in DaVinci Resolve is an intraframe DNxHR or ProRes copy, not cache settings. DNxHR and ProRes store every frame whole, so Resolve decodes only the frame under the playhead.

B-ROLL makes that copy for you. Choose DNx or ProRes in the Format menu, and B-ROLL downloads the best streams into an MKV master, then ffmpeg converts the master into a .mov with the same name. Resolution and frame rate are kept, so a 4K60 upload stays 4K60, and the audio becomes uncompressed 16-bit PCM.

B-ROLL picks the tier automatically. It measures the source bitrate on the master and takes the lightest tier whose data rate is at least 10 times the source; a 10-bit source converted to DNx always gets DNxHR HQX.

A worked example shows the scale. A 2160p 60 fps source at 25 Mbps gets DNxHR LB, which the app estimates at 288 Mbps (36 Mbps at 1080p 29.97 fps x a scale of 8.008), or 2.16 GB per minute (288 x 60 / 8 / 1000). Every tier and switch point is on download YouTube videos in ProRes or DNxHR.

The cost is time and disk. The conversion runs one file at a time on every CPU core, and a card reads done only after it finishes. If it fails, B-ROLL keeps the MKV master and logs “DNx transcode failed; keeping the MKV.” In that case, download again instead of importing the master.

Already have the AV1 file and cannot download it again? Resolve’s optimized media or proxies ease playback without replacing the original, and proxies vs transcoding for YouTube footage weighs both routes.

Does hardware decoding help with AV1 in Resolve?#

Hardware decoding helps with AV1 in Resolve, and on Windows it is the decode path Blackmagic lists. Blackmagic’s Resolve 20 codec list marks AV1 decoding on Windows as “Yes, GPU accelerated”, with no Studio-only note.

The same list treats H.264 and H.265 differently: both editions decode the profiles Windows supports (8-bit for H.264, 8-bit or 10-bit for H.265), with “More profiles and GPU acceleration in Studio”. AV1 is the exception, because its GPU acceleration is listed without that Studio line. Read that way, your graphics card, not your Resolve edition, sets the ceiling for AV1 playback.

A graphics card needs an AV1 decoder in its video engine for that acceleration, and older cards lack one. Check the video decode section of your GPU maker’s specification page for AV1. Resolve’s hardware decode controls sit under Preferences, System, Decode Options.

Hardware decoding does not remove the long-GOP structure. Reverse play and scrubbing still rebuild frames from their chain, and frame size multiplies the work: 4K at 60 fps is 497,664,000 pixels per second (3840 x 2160 x 60), eight times 1080p at 30 fps (1920 x 1080 x 30 = 62,208,000). When Resolve cannot decode a file at all, the clip shows Media Offline instead of stuttering; that case is covered in DaVinci Resolve Media Offline on a YouTube video.

How do you avoid choppy YouTube clips next time?#

Avoid choppy YouTube clips by choosing the edit format before you download, not after the clip is on the timeline. Five habits keep AV1 and VP9 out of a Resolve project.

1. Pick DNx or ProRes first. Set the Format menu before you paste links; MP4, MKV and WEBM keep YouTube’s own codecs.
2. Match the Quality cap to the delivery. Choose 1080p when the timeline and the export are 1080p; Best keeps 4K for reframing.
3. Download only the part you need. Only a part: ask me which each time in Advanced options converts a short cutaway instead of a full hour of footage. B-ROLL prefers YouTube’s HLS streams for parts, which cleared stalls on clips from deep inside long videos.
4. Read the card before you import. The real bitrate and resolution confirm what arrived, and the DNx or ProRes badge confirms the format.
5. Import only finished files. Wait for done; an MKV master in the folder means the conversion did not complete.

The full import routine, from the Format menu to the Media Pool, is in download YouTube videos for DaVinci Resolve. Other download problems, from sign-in prompts to HTTP 403, are collected in YouTube downloader not working? Fixes for editors.