Troubleshooting · Final Cut Pro & Premiere

Your downloaded video won't import. Here's why.

The download finished. The file plays fine in QuickTime or VLC. Then Final Cut Pro greys it out, or Premiere imports it and gives you a red screen, or audio with no picture. Nothing is corrupted — the file almost certainly contains something your editor cannot read.

The container is not the codec

This is the whole confusion in one sentence: .mp4 is a box, not a format.

The extension tells you how the file is packaged. What matters to an editor is which codec the video was compressed with, and that is invisible from the filename. An .mp4 can hold H.264, which every editor on earth reads, or it can hold AV1, which most of them do not.

This is also why the trick you may have already tried does not work. Renaming a .webm to .mp4 changes the label on the box and nothing inside it. The editor opens the box, finds a codec it cannot decode, and refuses exactly as before.

What your editor actually wants

Final Cut Pro and Premiere Pro are built to ingest a fairly narrow set of codecs natively:

• H.264 and HEVC (H.265), with AAC audio — the everyday delivery codecs.
• Apple ProRes, the family both applications are happiest editing.

What they generally will not take from a web download:

• VP9 — Google's codec, served by YouTube above 1080p and often at 1080p too.
• AV1 — the newer one, increasingly served on popular videos.
• Opus audio, which is what usually rides along inside a .webm.

Premiere is somewhat more forgiving than Final Cut here, and both have changed what they accept across versions, so the same file can import on a colleague's machine and not yours.

How to tell what you've actually got

You do not need to install anything. Two native ways:

QuickTime Player. Open the file, then Window ▸ Show Movie Inspector, or just press ⌘I. The Format line names the codec.

Terminal, if you prefer it in one line:

mdls -name kMDItemCodecs /path/to/your-file.mp4

You will get something like:

kMDItemCodecs = (
    "H.264",
    "MPEG-4 AAC"
)

That file will import. You are looking for anything that isn't H.264, HEVC or AAC — and note that macOS prints the raw four-character codec tag rather than the marketing name, so VP9 appears as vp09 and AV1 as av01. Opus shows up under its own name.

If it comes back (null), there are two possible reasons and they point in opposite directions. Either Spotlight has not indexed the file — common for anything sitting in iCloud Drive rather than on the disk — or the file is a .webm, which macOS has no reader for at all. In that second case the (null) is your answer: QuickTime will not open it either, and that refusal is the confirmation.

The three ways out

1. Take the H.264 version instead

The fastest fix, and the one most people skip because it feels like a downgrade. H.264 is served up to 1080p, it imports with no further work, and if your finished sequence is 1080p it is not costing you anything visible. Most downloaders let you pick the format rather than accepting whatever is largest.

2. Convert it

HandBrake is free and will transcode VP9 or AV1 into H.264. This works, and it costs you a full re-encode: time proportional to the length of the clip, plus a generation of quality loss, because you are decoding a compressed file and re-compressing the result.

For a single clip that is a minor annoyance. For a shot list of twenty, it is an evening.

3. Transcode to ProRes

This is what a post workflow would normally do with any awkward source: convert once, to the codec the editor is built around, and work from that. ProRes files are much larger than the download, and they scrub, trim and render without the stutter you get from editing long-GOP footage directly.

That larger file size is the trade. On a laptop with limited disk it is a real cost; on a working edit drive it is usually the right call anyway.

Where ReelPull fits

We built ReelPull around this specific wall, because it is the point where a free download stops being free of effort.

The free tier covers case 1 at 720p: it prefers H.264/AAC and remuxes it into an MP4 without re-encoding, so the video data is untouched and the file imports natively. Remuxing swaps the container only — it is close to instant and costs no quality. It is uncapped and needs no account, which makes it a genuine way to test whether the import problem goes away on your own footage.

Pro raises the ceiling to full 1080p and the source's own maximum, which is where the codec problem starts in earnest.

Above 1080p, no amount of remuxing helps: remuxing cannot change a codec, so the transcode has to happen somewhere. YouTube hands over VP9 or AV1, and changing the wrapper leaves that untouched. So Pro transcodes to ProRes 422 HQ on the way out — case 3, done automatically, so a 4K source lands as a file Final Cut and Premiere ingest natively with no HandBrake pass in the middle.

That transcode is the part you are actually paying for, and now you know precisely what it does and why remuxing cannot substitute for it.

For transparency: ReelPull is a native Mac app built around yt-dlp and ffmpeg, both long-standing open-source projects — the licences are listed here. If you run yt-dlp yourself and it has suddenly stopped working, that is a different problem with its own three causes. It refuses DRM-protected streaming services by design, which is covered in more depth in is it safe to download YouTube videos.

You can download the free tier and test the 720p path on your own footage — if the file imports, you have confirmed the diagnosis for free, and you then know exactly what the paid tiers are buying you.