
A Reddit editor described a particularly confusing version of the DaVinci Resolve media offline problem: the files were linked, the paths were correct, audio waveforms were visible, and the same project worked on a collaborator's computer. Yet the timeline still displayed red Media Offline frames.
This example matters because relinking the same files again will not fix a codec, cache, proxy, GPU, or timeline conform problem. The correct DaVinci Resolve media offline fix starts by matching what you see to the most likely cause.
Start here: If every clip from one folder is offline, relink that folder first. If audio works but video is offline, check the codec. If the clip works in the Media Pool but fails on the timeline, repair its timeline association.
Table of Contents
Media Offline means DaVinci Resolve cannot read or display the frames it expects from a clip. The source file may have moved, but that is only one possible cause. Resolve can also show the warning when a codec cannot be decoded, a proxy is missing, a damaged cache is being used, or a timeline clip is connected to the wrong Media Pool item.
In practical terms, Resolve knows that a clip belongs in the edit, but it cannot retrieve or decode the correct picture at that moment. Your edit decisions usually remain intact.
Use the symptoms below to identify where to begin:
| What You See | Likely Cause | Try First |
|---|---|---|
| An entire folder or drive is offline | Files moved, drive disconnected, drive letter changed, or permission lost | Reconnect the drive and relink the clips |
| Audio plays but the picture is offline | Unsupported or unavailable video decoder | Check the codec, bit depth, chroma sampling, OS, and Resolve edition |
| Only random frames flash Media Offline | Render cache, GPU decoding, or variable-frame-rate footage | Disable the cache, test camera originals, and check frame-rate mode |
| Clip plays in the Media Pool but not on the timeline | Timeline conform mismatch | Use Conform Lock With Media Pool Clip |
| Project works on another computer only | Different paths, permissions, codecs, drivers, or Resolve editions | Compare the two systems instead of changing the edit |
Work through these fixes in order and stop when the clips return. The early steps repair common file-path problems; the later steps address clips that are visible and linked but still cannot be displayed.
Before changing Resolve settings, verify that the source file is present and readable.
If the file is missing, reconnect the external drive, download the file from cloud storage, or restore it to the expected folder. A cloud placeholder must be fully downloaded before Resolve can use it.
Also check whether the filename or folder name changed after the clip was imported. Resolve links to a specific location; renaming either part of that location can break the connection.
If the original files open normally outside Resolve, reconnect them to the project:

4. Select the folder that now contains the original files.
5. Let Resolve search the folder and reconnect matching filenames.
If Resolve does not find the files, choose a higher-level parent folder so the search includes its subfolders. Confirm that the restored files have the same names as the clips originally imported.
When an entire camera card or project folder was moved, select all affected clips before relinking. Resolve can reconnect them together instead of making you locate every file individually. This method has also been confirmed to be effective by Reddit users.
A drive can be connected while Resolve still sees a different path.
D:\Footage will not automatically use the same folder on E:\Footage.Open Preferences > System > Media Storage and confirm that the drive or media root is accessible. Then relink the clips to their current location.
Sometimes the clip is online and playable in the Media Pool, but its timeline instance remains offline. This points to an incorrect association between the timeline and the Media Pool item.
On the Blackmagic forum, a user resolved this issue with Conform Lock With Media Pool Clip.

5. Check the start frame and playback before repeating the process for other clips.
This tells Resolve exactly which Media Pool clip the timeline item should use. It is particularly useful when clips have matching timecode, similar filenames, or material from multiple camera cards.
If a timeline item still points to the wrong file, select the correct source in the Media Pool, right-click the timeline clip, and use Replace Selected Clip. Check the clip's timing immediately after replacement.
A damaged render-cache file can display Media Offline even while the original recording remains healthy. Some users said restoring playback by disabling cache or deleting generated cache files.

3. Play the affected section again.
4. If the picture returns, go to Playback > Delete Render Cache > All.
5. Re-enable Smart or User cache only after confirming that the source plays correctly.
Deleting render cache removes temporary files generated by Resolve. It does not delete the original recordings, timeline edits, transitions, or color grades.
If the project was edited with proxy media, Resolve can continue looking for proxies that were moved, deleted, or stored on another computer.
If the original footage works, the problem is limited to the proxy files. Delete or unlink the missing proxies, then generate new ones from the online camera originals.
This is also an important test when a project works on a collaborator's machine. Their computer may have access to a proxy folder that does not exist on yours. Turning off proxy viewing and deleting render cache on both systems before comparing the projects.
If Resolve imports the clip and displays its audio waveform but the picture remains offline, inspect the video codec. The container alone is not enough: two MP4 or MXF files can contain different codecs, bit depths, profiles, and chroma formats.
Pay close attention to H.264 and H.265 footage recorded in 10-bit or 4:2:2, along with camera-specific MXF formats. Codec support depends on the complete format combination, not merely the file extension.
If the format is not supported on the current system, transcode the original file to an editing format such as DNxHR or ProRes. Keep the same resolution and frame rate, import the transcoded file, and relink or replace the offline clip.
For HEVC footage on Windows, install the official Microsoft HEVC Video Extensions when the required HEVC decoder is missing, restart the computer, and test the file again.
When Media Offline appears for only a few frames, the source path is usually not the problem. Test the decoding path instead.

In Resolve Studio, open Preferences > System > Decode Options and temporarily disable hardware acceleration for H.264 and H.265. Restart Resolve after changing this setting.
If playback becomes stable with hardware decoding disabled, keep it disabled for the project or install the latest stable GPU Studio driver before testing acceleration again.
Phone recordings, screen captures, meeting recordings, and gameplay footage often use a variable frame rate. Their frame timing changes during recording, which can cause offline flashes, skipped frames, or audio-sync errors during editing.
This method is supported by several user reports. In one iPhone HEVC discussion, users identified the changing frame rate and recommended transcoding to DNxHR with a constant frame rate.
Match the new file's frame rate to the intended recording rate, such as 23.976, 25, 29.97, 30, or 60 fps. If the recording was intended to be 30 fps, select 30 fps and enable the encoder's constant-frame-rate option.
Once the project is working, a consistent media structure prevents the same issue from returning.
For collaborative projects: Agree on one folder structure before editing starts. Each editor should use the same source filenames, compatible codecs, Resolve version, plugins, and project settings.
A camera cannot repair an unsupported codec, disconnected drive, or broken Resolve link. However, a controlled recording workflow can reduce the number of capture problems that reach the edit.
For presentations, interviews, classes, performances, and live events, OBSBOT Tail 2 provides an in-camera recording option through its MicroSD slot alongside HDMI, 3G-SDI, USB 3.0, Ethernet, and supported NDI workflows. You can select a recording route that fits the production, then copy the resulting files into one organized project folder before importing them into Resolve.
Useful features for an editing workflow:
Resolve displays Media Offline when it cannot find, access, decode, or correctly associate the video frames required by a clip. Check the source path first. If the path is correct, test the codec, proxies, render cache, GPU decoding, and timeline conform association.
The audio and video streams can use different codecs. Resolve may decode the audio while failing to decode the video. Inspect the video codec, profile, bit depth, and chroma sampling, then compare them with the official support list for your operating system and Resolve edition.
The other computer can have a different drive path, proxy folder, codec component, Resolve edition, GPU driver, or media permission. Compare those items before modifying the timeline. If both systems can open the source file, switch to camera originals and clear the local cache.
No. Render-cache files are temporary media generated to improve playback. Deleting them leaves source recordings, cuts, effects, grades, and timeline structure unchanged. Resolve can rebuild the cache later.
Select all offline clips from that folder in the Media Pool, right-click, and choose Relink Selected Clips. Point Resolve to the folder's current location. Select a parent folder when the material is divided across several subfolders.
Brief red frames usually point to corrupted cache files, unstable GPU decoding, damaged media, or variable-frame-rate footage. Disable render cache, test camera originals, turn off hardware decoding, and convert variable-frame-rate clips to a constant frame rate.
The fastest way to fix Media Offline in DaVinci Resolve is to follow the symptom. Relink files that moved, repair timeline conform mismatches, test camera originals, clear damaged cache, and inspect the codec when audio works without video. Once the footage returns, organize the project into one stable folder before continuing the edit.



