DaVinci Resolve Media Offline: Every Cause, and How to Fix It

You open your project and everything in the edit has gone offline. Two words, Media Offline, and hours of work look like they just evaporated.

They almost certainly did not. In the overwhelming majority of cases the footage is still sitting on the disk, untouched, and the fix takes under a minute once you know which of the twelve or so possible causes you are actually dealing with.

This guide runs through every cause of DaVinci Resolve media offline, in order from most frequent to most obscure, with the fix for each. There is also a triage section at the top, because the single biggest time-waster with this error is applying the fix for cause number one when you actually have cause number eight.

What media offline in DaVinci Resolve actually means

One thing to understand before any of the fixes make sense.

DaVinci Resolve does not copy your files into the project, and it does not move them. When you import footage, Resolve simply writes down where that video lives, in an internal database, and from then on it reads from that location every single time you scrub the edit.

So Media Offline is not a corruption message. It means one thing: "I looked where I noted this lives, and there is nothing readable there."

That sentence covers a lot of different situations. The video might be gone. It might be there under another name. The disk might be unmounted, or mounted somewhere new. A file might be perfectly present and perfectly readable by your operating system, but unreadable by your particular version of Resolve because of the format inside it. All of those produce the same red frame.

Once you hold that idea, diagnosis stops being guesswork.

Triage: three questions before you touch anything

Answer these first. They will send you straight to the right section instead of making you work through the whole list.

• Is everything offline, or only some shots?
• Does the Media Pool still show a location for the offline clip?
• Is it offline at all times, or only during playback?

Let me explain :

1. Is everything offline, or only some shots?

Everything offline usually points at a disk, a location, or a project-level issue: an unmounted volume, a changed drive letter, a moved folder. A handful of offline items points at those specific media files: renamed, deleted, or in a format your version will not decode.

2. Does the Media Pool still show a location for the offline clip?

Hover over it in the Media Pool on the Edit page. If Resolve shows you an address, it still knows what it is looking for and simply cannot find it, which means relinking is your answer. Now copy that address and go look at it in Finder or File Explorer. Is the file sitting right there? If yes, and DaVinci Resolve still refuses it, you have a format or a permissions issue, not a location issue.

3. Is it offline at all times, or only during playback?

A timeline clip that goes offline when you park on a frame is genuinely missing or undecodable. Footage that looks fine when parked but flickers during playback is a completely different issue: your storage cannot feed frames fast enough. That one is covered further down, and relinking will do nothing for it.

Now, the solutions :

1. The media moved, or the disk is disconnected

By far the most common cause, and it happens to everyone, including people who have been doing this for twenty years.

You reorganised a folder, renamed a parent directory, cleaned up your desktop, or archived last month's job. Resolve goes looking at the old address and finds nothing.

It also happens when you did not touch anything. External disks are the classic case: on Windows the letter assigned to a volume can change between sessions depending on what else was plugged in at boot, and on macOS a second mount of the same volume can appear as /Volumes/Disk 1 instead of /Volumes/Disk. The files are identical, their address is not, and Resolve has no idea they are the same thing.

The fix. Right-click the offline items in the bin and choose Relink Selected Clips. Point Resolve at the folder that now holds your media. It will match everything it can find by name.

One tip that saves a lot of repeat work: select the parent directory rather than the exact subfolder. The search runs downward through subfolders, so aiming at the top of your media tree relinks the whole job in one pass instead of one camera card at a time.

If you want to see what Resolve is looking for before you start, right-click an offline item and check its stored location in the Inspector or in the clip attributes. Comparing that address with reality usually explains everything in two seconds.

2. The media was renamed

This one looks identical on screen and behaves completely differently. Relink will not save you here, no matter how many times you aim at the right directory. Matching happens on the name, and the name it wants no longer exists anywhere.

The fix. Tell Resolve to replace rather than relink. Right-click the offline item in the bin, choose Clip Attributes or Clip Operation, then Replace Selected Clip, and pick your renamed video.

The good news is that this is non-destructive to your edit. Every cut, every keyframe, every grade you already built survives. The database entry is simply updated with the new name and location.

If a whole batch was renamed by a script or a card-offload tool, and the renaming followed a consistent pattern, it is usually faster to rename everything back to the original scheme than to replace fifty items one by one.

3. Media was deleted from the Media Pool

This is the one that generates panic calls, because the whole edit goes offline and the obvious fix does nothing.

Somebody deletes a bin, thinking they are only cleaning up. Every shot in the timeline loses its source and goes offline. The natural reflex is to re-import, which puts your files back in the bins, and the edit stays stubbornly offline. DaVinci Resolve does not automatically connect newly imported footage to orphaned shots in a sequence.

The fix. You have to make the connection explicitly. Two routes:

• Reconform From Bins, for the whole timeline at once. Right-click your timeline in the Media Pool, then Timelines > Reconform From Bins, and select the bins holding the re-imported footage.
• Conform Lock With Media Pool Clip, item by item. Select the shot in the bin and its counterpart in the edit, right-click the second one, and apply it.

Reconform From Bins is dramatically faster when there is a lot to reconnect. The per-item option is there for the awkward leftovers that did not match automatically.

4. Hardware: cable, port, power, or a dying disk

Sometimes the issue is not the content, it is the container.

If you work off external disks or SSDs, check the whole chain before you blame Resolve:

• The USB or Thunderbolt port itself, which can be failing or simply underpowered.
• The cable. A worn one causes intermittent disconnections that look exactly like random red frames mid-session.
• Power. Bus-powered units hanging off an unpowered hub are a recurring culprit, especially when several devices share it.
• The disk itself, which may be starting to fail. Intermittent, moving, unrepeatable failures on a volume that has been fine for years deserve a SMART check.

The simplest test in the world: copy your media to internal storage and open the project again. If the trouble vanishes, your external storage or its connection is the culprit, not your edit.

On internal storage, check that Resolve has permission to open the volume, and that aggressive disk sleep settings are not spinning it down mid-session.

5. Format: H.265, 10-bit, and 4:2:2

A very common cause for anyone shooting on a phone, a recent GoPro, or a DJI drone, and one that confuses people because the video plays fine in every other app on the machine.

Here the honest answer is more nuanced than the one you usually read. "The free version is 8-bit only" is too broad to be useful. What actually matters is the combination of your operating system, your version of Resolve, and the exact flavour of the codec inside the file.

Blackmagic publishes a supported-codec matrix, and it is organised by platform for a reason. On Windows, some H.265 profiles decode in the free version while others do not, and the case that trips people up most often is 10-bit 4:2:2 HEVC, which is exactly what a lot of recent hybrid cameras record. It also relies on the HEVC Video Extensions from the Microsoft Store for some HEVC decoding, and their absence produces black frames or offline clips. On macOS, the hardware-accelerated H.264 and H.265 paths are not marked as Studio-only in the same way. On Linux, both require Studio.

So before assuming anything, inspect the file. MediaInfo is free and tells you container, codec, profile, bit depth, chroma subsampling and frame rate in one window. Compare what it reports against Blackmagic's supported codec list for your platform and your version. That takes two minutes and beats a week of forum threads.

To fix the media offline error in this case, in order of preference:

1. If the profile is simply unsupported on your platform, transcode to an editing codec. DNxHR on Windows, ProRes on macOS. Shutter Encoder is free, well maintained and built for exactly this. Handbrake also works.
2. Install the HEVC Video Extensions from the Microsoft Store if they are missing.
3. Upgrade to Studio if your workflow genuinely lives on these formats, but only after confirming with a test video that Studio is what makes the difference on your machine.

Transcoding is not a defeat, by the way. Long-GOP HEVC is a delivery codec, not an editing one, and cutting from DNxHR or ProRes will make your whole edit behave better regardless of the offline question.

6. Variable frame rate footage

Closely related, and worth separating because the fix is the same but the symptom is different.

Phones, action cameras and screen-recording software very often write variable frame rate video. The camera drops or adds frames depending on light and processing load, so there is no single stable rate. Editing software expects a constant one. The mismatch produces drifting audio sync, stutter, and sometimes an outright offline clip.

The fix. Transcode to a constant frame rate before importing, with the same tools as above. Decide what rate you actually want (the nominal one is usually the right answer) and convert. Do it before you start cutting, because doing it afterwards means reconnecting everything.

7. Offline only during playback

If the viewer shows the image when you park on a frame, but flickers while playing, nothing is offline in the database sense. Resolve simply cannot pull data fast enough to keep up.

Usual reasons: high-bitrate footage on slow external storage, a USB 2 connection where you assumed USB 3, a cache volume that is full, or a network share with limited throughput.

The fix. Move your media files, the cache, or both to faster local storage. Check that your cache location has free space. Generate optimised media or proxies at a manageable resolution and switch playback to them. And confirm what your cable and port actually negotiate, since a working cable that runs at USB 2 speeds is a classic silent bottleneck.

8. Corrupt cache, optimised media, or proxies

When Resolve has generated cache, optimised media or proxies, it may use those instead of your originals. If that generated material is damaged, or sits somewhere failing or full, you can get red frames even though the source is perfectly healthy.

The tell is that everything looks fine in the Media Pool and broken in the edit, or that the issue follows a specific set of shots you recently cached.

The fix. On the Edit page, go to Playback > Delete Render Cache > All and let Resolve rebuild. When you render the cache again, watch whether the same items break a second time.

For proxies and optimised media, toggle proxy mode off and see whether the clips come back; if they do, regenerate. If it keeps happening, move the cache to a healthy volume in Project Settings > Master Settings.

9. GPU drivers and decode settings

A cause that rarely appears on lists like this one, and that I have watched cost an editor an entire afternoon.

Decoding is hardware accelerated, so a graphics driver that is broken, mismatched with your build of Resolve, or freshly updated by Windows overnight can produce black frames, an offline error on import, or clips that decode on one machine and not on the one sitting next to it. The same goes for a decode option pointing at hardware that is no longer there, which happens after a GPU swap.

The fix. Update to the studio or production branch driver listed as supported for your build rather than the newest one available, and restart. On an NVIDIA card, check Preferences > Decode Options and try switching hardware decoding off for a test: if the picture comes back, the driver is your answer. Confirm Resolve is using the GPU you think it is in Preferences > Memory and GPU, and give it enough RAM there if you are on a machine with plenty.

10. Permissions and network storage

A file can be present in a readable format, and still refused, because Resolve is not allowed to open it.

On macOS this comes up when DaVinci Resolve lacks Full Disk Access, or when your media sits in a protected place such as Desktop, Documents or an external volume that never got an access prompt. Grant access in System Settings > Privacy & Security > Full Disk Access and restart.

On network storage, the usual suspects are a share that mounted after launch, expired user credentials, an address that resolves differently for different people on the same NAS, or read-only permissions. Mount the share before opening the project, and make sure the mount point is identical to the one used at import.

11. Fusion compositions that are too short

A lesser-known case, and one that catches people out because nothing in the bins is wrong.

You are working inside a Fusion composition and you extend its duration. Media Offline appears inside the composition, because the material used within it does not cover the new length. Fusion has nothing to work with past the end of what it was given.

The fix. Open the Keyframes panel on the Fusion page and check that every media node covers the full duration of the composition. Extend the sources as needed.

12. Blackmagic Cloud and shared projects

On a cloud or shared database workflow, offline media is usually a mapping issue rather than missing footage. Each machine may see the same storage under a different root, and the job carries one set of addresses.

Naming matters more than people expect here. Special characters and accented letters in file and folder names are a recurring source of trouble on cross-platform setups. Keep names plain.

The fix. Map the locations per machine in the project settings so that each workstation knows how its local mount point corresponds to what was stored, and standardise your directory structure across the team before a job starts rather than after.

13. Offline media after importing an edit from another NLE

This one deserves its own section because the cause is structurally different, and the usual advice sends people down the wrong road entirely.

When you bring an edit into Resolve from another application through XML, FCPXML, AAF or EDL, what you import carries no media at all, whichever interchange format you choose. It is a set of instructions: names, in and out points, track layout, and addresses written exactly as they existed on the machine that exported them. If your files are not at those exact addresses, everything lands offline on arrival.

That is expected behaviour, not a failed import. The fixes are the ones above, mostly relinking at the parent folder level, but knowing the cause saves you from re-exporting five times looking for an issue that was never in the file.

Some related failure modes are specific to interchange imports rather than to Resolve itself: frame rate mismatches that put everything at the wrong length, stereo audio arriving as two mono tracks, an hour of timecode offset. We have written those up separately in our XML import troubleshooting guide, which walks through the five distinct failures and how to tell them apart.

A disclosure, since it is relevant here. We build PR2XML, a paid tool that converts Premiere Pro projects into Resolve's native .drp format as well as FCPXML and XML. It removes a specific class of trouble, namely the fidelity loss that comes from exporting an interchange file out of Premiere, and it lets you work from a .prproj when you no longer have an Adobe subscription running. It does not remove this one. No converter can, because no interchange file carries your footage. If your media has moved since the original edit, you will relink, whichever road you took to get there. Our Premiere Pro to DaVinci Resolve guide covers the full migration path if that is where you are, and you can run a project file through the converter in your browser without installing anything. If all you need is a finished file rather than an editable edit, our guide on getting an MP4 out of a project file without Premiere covers that route instead.

14. The nuclear option: restore a backup

If none of the above explains it, the database entry itself may be damaged.

DaVinci Resolve keeps automatic backups. Go to File > Project Manager, right-click the job, and choose Project Backups. Restore a project file saved before the trouble appeared, then check what you lose between that point and now.

Which is the argument for never disabling automatic backups in Preferences > User > Project Save and Load, and for exporting a manual .drp before any major restructuring session.

DaVinci Resolve media offline: the quick diagnosis table

How to stop it happening again

Most offline errors are a storage-hygiene issue wearing a software costume. A few habits remove almost all of them:

Decide your directory structure before you import, not after. One root per job, media inside it, and no reorganising while it is live.

Never rename after import. Rename at offload, before anything touches the files. Renaming is the one case where relinking cannot help you.

Keep a stable mount point. On Windows, assign a fixed letter to your media volume in Disk Management. On macOS, avoid mounting the same one twice and watch for /Volumes/Name 1 appearing.

Transcode problem codecs at offload. If your camera writes 10-bit 4:2:2 HEVC or a variable rate, deal with it once, at the start, rather than mid-edit.

Use Media Management for archives. File > Media Management copies or transcodes only what the edit actually uses, into a self-contained directory. That is a far safer archive than moving things around by hand and hoping.

Leave automatic backups on. They cost almost nothing and they are the last line of defence.

FAQ