"Cannot find essential data" — Premiere / Resolve Error

This message — sometimes phrased as "cannot find essential data" or "essential data missing" — usually comes from Adobe Premiere Pro or Media Encoder when importing a damaged MP4 / MOV. The same underlying problem can produce different messages in DaVinci Resolve ("media offline" / "unsupported format") and Final Cut Pro ("file not in a supported format").

The error is more specific than it sounds. The editor has identified the file as a video container but can't find the metadata tables it needs to mount the streams. In MP4 / MOV terms, those tables are inside the MOOV atom — stsd (sample description), stts (frame timing), stco/co64 (chunk offsets), stsz (sample sizes), stss (sync samples). If any of these are missing, malformed, or contain inconsistent values, Premiere bails with this generic message.

The four common causes

In rough order of frequency:

1. MOOV is entirely missing

The recording was interrupted before the index could be written. See the MOOV atom not found page for the canonical version of this case. Premiere reports this as "essential data missing" because, from its perspective, the essential metadata tables aren't there to be read.

2. MOOV is present but partially damaged

The file has a MOOV atom that parses — the editor opens it — but one or more child atoms inside MOOV are corrupted. Often this is a partial write: the camera or external recorder began finalising the recording, made it part-way, and was interrupted. The file looks superficially complete but the index has gaps.

3. stco overflow on a file > 4 GB

If a third-party tool wrote the recovered file using 32-bit chunk offsets (stco) instead of 64-bit (co64), files larger than 4 GB get silently corrupted offsets in the second half. Premiere reads the early offsets fine and hits invalid offsets later. The error sometimes manifests as "cannot find essential data" rather than a clean offset-overflow message.

4. Container/codec mismatch

The file's container declares one codec; the actual frame data is something else. Common after partial recovery attempts where the codec parameters were guessed wrong. Premiere mounts the streams, tries to decode, and bails partway through.

How to figure out which one

Run ffprobe on the file:

ffprobe -v error -show_format -show_streams broken.mp4

Three patterns to recognise:

• No output at all (just "moov atom not found") → cause #1.
• Stream info that looks valid (resolution, codec, duration) → cause #2 or #4. The MOOV is parsing; something inside it is wrong.
• Stream info but with Invalid data found warnings → cause #2.
• Output looks fine but file is > 4 GB and the second half plays as garbage → cause #3.

For cause #3 specifically, you can inspect the atom layout with:

ffmpeg -v debug -i broken.mp4 2>&1 | grep -i "stco\|co64"

If the file was written with stco and is over 4 GB, that's the bug.

What you can try yourself

For cause #1, follow the MOOV recovery guide.

For causes #2–#4, try a re-mux:

ffmpeg -err_detect ignore_err -i broken.mp4 -c copy out.mov

This often rebuilds the index from what's actually in the file, bypassing whatever was wrong with the original MOOV. If the codec data is intact, the re-mux usually works.

If that fails, drop into a different container:

ffmpeg -i broken.mp4 -c copy out.mkv

MKV's more permissive than MP4 about index consistency.

How our recovery handles "essential data" cases

We don't trust the existing MOOV. The diagnostic pass:

• Walks the byte stream looking for atoms by signature.
• Validates each atom's declared size against next-atom-found cross-checks (don't trust declared sizes).
• Identifies cause #1 (no MOOV at all) vs cause #2 (MOOV present but broken) and routes accordingly.
• For files > 4 GB, always uses co64 for chunk offsets — never stco.
• For container/codec mismatch, identifies the actual codec from frame markers and rebuilds the container around the truth, not the lie.

What you do

1. Upload the file. Up to 50 GB.
2. ~1 minute later you get a diagnostic + free preview.
3. Pay only if the preview works.

FAQ

Premiere Pro says "essential data missing" but Resolve mounts the file. Should I worry? Possibly the file is borderline — Resolve's importer is more permissive than Premiere's. If Resolve can play it, you can transcode from Resolve to a clean MOV / MP4 and bypass Premiere's complaint. If you need to deliver the original file, recovery is still the answer.

The file imports into Premiere but the timeline shows offline media halfway through. That's likely the co64 overflow (cause #3). Recovery rebuilds the file with proper 64-bit offsets and the second half mounts cleanly.

My file plays in QuickTime but Premiere refuses to import it. Premiere is stricter than QuickTime about index consistency. The recovery pass produces a file both will accept.

Is my footage safe? Server in France, auto-deleted after 48 hours, never used to train anything or shared. Privacy policy.

Related

• MOOV atom not found
• Invalid data found when processing input
• How our recovery engine works

Upload your file →