You downloaded a YouTube video for your edit. You drag it into Final Cut Pro and — nothing. “Media unsupported.” Or it imports with audio and a black screen. Or QuickTime shrugs and offers to search the App Store.
The file isn’t broken. It’s just speaking a language your editor doesn’t.
Here’s what’s actually happening, how to check it in ten seconds, and three ways to fix it — including how to stop it happening in the first place.
The short answer
YouTube doesn’t store videos in an editor-friendly format. For most videos — and almost everything above 1080p — YouTube serves video encoded as VP9 or AV1, usually inside a WebM container, with Opus audio. Those formats are great for streaming in a browser. QuickTime and Final Cut don’t speak them.
What your Mac tools want is H.264 (or HEVC) video with AAC audio in an MP4 file. That combination opens everywhere: QuickTime, Final Cut, Premiere, CapCut, iMovie.
So when a downloader hands you exactly what YouTube serves, you get a file that streams beautifully and edits terribly.
Containers vs codecs — the two-second version
This trips everyone up once, so here it is plainly:
- The container is the box:
.mp4,.webm,.mkv,.mov. It’s just packaging. - The codec is what’s inside: H.264, VP9, AV1, HEVC for video; AAC, Opus for audio.
This is why a file ending in .mp4 can still fail — the box is right, but the contents aren’t. An MP4 containing AV1 video will still confuse most Mac editing apps.
Check what you actually have
Two quick ways:
- QuickTime: open the file (if it opens at all) and press ⌘I. The inspector shows the format — if you see “VP9”, “AV1”, or “Opus”, that’s your culprit.
- VLC or IINA: open the file, then look at the media information window (⌘I in both). These players handle almost anything, which is exactly why “it plays in VLC” doesn’t mean it will edit anywhere.
If the video won’t open in QuickTime but plays fine in VLC, you can be nearly certain it’s a codec problem, not a corrupt file.
Fix 1: re-encode with HandBrake (free)
HandBrake converts almost anything to an editor-friendly file:
- Open your file in HandBrake.
- Pick the Fast 1080p30 preset (or match your resolution).
- Under Video, make sure the encoder is H.264 (x264).
- Under Audio, make sure the codec is AAC.
- Start the encode.
The downside: it’s a second pass of compression, it takes time on long videos, and you’ll do this dance for every single download.
Fix 2: re-encode with ffmpeg (free, command line)
If you’re comfortable in Terminal:
ffmpeg -i input.webm -c:v libx264 -crf 18 -preset medium -c:a aac output.mp4-crf 18 keeps quality visually lossless for most footage. Same downside as HandBrake — every file, every time, plus a re-compression generation.
Fix 3: get the right file in the first place
The dance above only exists because the download handed you a streaming format. The cleaner fix is a downloader that delivers editor-ready files from the start.
That’s the entire reason we built Blip: it downloads YouTube videos and automatically delivers QuickTime-friendly H.264/AAC MP4s — up to 4K, with YouTube chapter markers preserved. Paste a link, press download, drag the file straight onto your timeline. No inspector, no HandBrake, no Terminal.
Why “it worked last week” stops working
YouTube continuously shifts which formats it serves — by resolution, by video, by experiment. A 720p file might arrive as H.264 today and the 4K version of the same video as AV1. That’s why this problem feels random: it is. The only stable strategy is converting to (or directly getting) H.264/AAC, which has been the editing lingua franca for over a decade.
The bottom line
- Won’t open in Final Cut or QuickTime, but plays in VLC → it’s the codec, not the file.
- YouTube serves VP9/AV1/Opus; your editor wants H.264/AAC.
- One-off fix: HandBrake or ffmpeg. Every-time fix: download it editor-ready with Blip — 5 free downloads to try, $14.99 once if it earns its keep.
Repurposing clips across platforms? Read Repurposing TikToks to YouTube Shorts on a Mac next.