DaVinci Resolve Cannot Decode / Media Offline — Fix

DaVinci Resolve is the most permissive of the three major NLEs (Resolve / Premiere / Final Cut). When Resolve says it can't decode a file, it usually means something genuinely structural is wrong — Resolve has tried hard and given up.

Common phrasings:

• "Media offline" — the file Resolve is supposed to play isn't where it expected, OR the file is there but Resolve can't read it.
• "Unsupported format."
• "Could not decode media."
• A red "X" thumbnail in the media pool.

This page is about the second flavour: file is present, Resolve can't read it.

Why Resolve fails when other tools succeed

Resolve has its own media engine (BMG / DaVinci Media Decoder). For most codecs it's broader than Premiere's; for some it's narrower. Specific gaps:

• DNxHR-LB (the lowest-bitrate DNxHR variant) — sometimes fine, sometimes flagged.
• HEVC Main 4:2:2 on Windows builds without the optional HEVC pack from Resolve's installer.
• Cineform — supported on macOS, Windows install needs the Cineform codec separately for some Resolve versions.
• AV1 — supported in recent Resolve, not in older builds.
• MJPEG with non-standard markers — Resolve's MJPEG decoder is strict.

For all of those, the file isn't broken. The Resolve install just doesn't have the decoder.

The other reason: file is genuinely broken

The cases where Resolve refuses a file and QuickTime / VLC also can't play it:

• MOOV missing or malformed.
• File truncated.
• Codec data damaged.
• Container/codec mismatch.

These are recovery cases. See MOOV not found, file truncated, the document could not be opened.

Diagnose

ffprobe -v error -show_streams broken.mov

If ffprobe returns useful stream info → file is structurally fine, Resolve has a codec gap. Solution below.

If ffprobe returns errors or empty → file is broken, recovery applies.

Cross-check: try playing in VLC. VLC's decoder library is usually broader than Resolve's for codec compatibility.

What to do per case

Resolve codec gap

Transcode to a Resolve-friendly codec:

ffmpeg -i source.mov -c:v dnxhd -profile:v dnxhr_hq -c:a copy resolve_friendly.mxf

DNxHR HQ at 4K is a Resolve-native target. The transcoded file imports cleanly.

If the codec is HEVC Main 4:2:2 specifically, install Resolve Studio (paid) or use Resolve Studio's HEVC decoder. The free Resolve has limitations here.

File genuinely broken

Recovery flow.

How our recovery handles Resolve-target cases

Resolve is one of our internal compatibility targets. The recovered file is verified to:

• Import into Resolve without "media offline" warnings.
• Play in the source viewer without stutter.
• Mount on the timeline with the correct duration and frame rate.
• Include all detectable audio tracks.

If a recovered file fails any of these in Resolve, that's a regression we treat as a bug.

Specifically:

• Codec preserved. ProRes stays ProRes, H.265 stays H.265. We rebuild the container, not the codec data — the recovered file is byte-for-byte identical to the original at the codec level.
• co64 for files over 4 GB. Resolve handles co64 correctly; tools that use stco for large files produce media-offline behaviour partway through the timeline.
• Audio chunk placement matches Resolve's expectations (start of video group, not end), so audio doesn't drift relative to picture.

What you do

1. Upload the file.
2. Free 5-second preview. If it plays in your browser, the recovered file plays in Resolve.
3. Pay only if it works.

FAQ

Resolve marks the clip "media offline" but the file is right where it should be on disk. Common causes: file moved/renamed in macOS Finder while Resolve project was open (Resolve cached the path), file's MOOV got corrupted post-import (rare), or the file's index has values Resolve refuses (re-mux fixes this in many cases).

Resolve plays but with a red flash / single black frame at the start. Often a missing or wrong stss (sync sample) in the rebuilt MOOV — Resolve seeks to a non-keyframe. Recovery rebuilds stss from observed IDR positions; if your file is from another tool's recovery, our redo fixes this.

Resolve says "could not decode media" specifically on H.265. Free Resolve has limited HEVC decode on Windows. Either install Resolve Studio, transcode to ProRes / DNxHR, or update macOS for hardware decode.

Resolve drops audio on import even though ffprobe shows audio. Sometimes a sample-rate mismatch between Resolve's project setting and the file's audio. Try changing project settings to match (48 kHz is the most common camera rate).

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

Related

• Premiere Pro import failed
• Cannot decode H.265 on Mac
• How our recovery engine works

Upload your file →