How to Fix DaVinci Resolve Unable to Import Media?
DaVinci Resolve can leave the Media Pool empty after you select a video, even though that file plays normally elsewhere. Sometimes the clip appears, but only its audio is available or the viewer shows Media Offline instead of a picture.

Playback in another app does not guarantee editing support. Resolve needs access to the complete file and a decoder for its particular recording format. Two MP4 files can contain different video formats, and support can differ between operating systems and Resolve Free or Studio.
| What happens | Relevant check |
|---|---|
| Nothing enters the Media Pool. | Import a fully downloaded local copy. |
| The drive or folder is missing inside Resolve. | Add its Media Storage location. |
| The clip imports without video or stays black. | Check its codec and edition support. |
| A previously working clip now says Media Offline. | Reconnect its drive or relink the moved footage before converting anything. |
1. Import One Complete Local File
A file listed in cloud storage or on your phone may not be fully downloaded. Testing a local copy leaves footage already used in your project untouched.
- Create a test folder outside cloud storage, such as
C:\ResolveMedia\Teston Windows orMovies/ResolveMedia/Testinside your Mac home folder.

- Fully download the recording, then copy it there. Finish any phone transfer or archive extraction first.
- In Resolve, select File > Import > Media, choose the copied file and click Open. On the Media page, double-click the imported clip to check its picture and sound.

A local copy confirms whether Resolve can import the file without cloud, phone, external-drive, or network access getting involved.
A working copy makes the original location worth checking, not replacing the external drive.
Only drag-and-drop fails on Windows? Close Resolve and launch it normally, not as administrator. If enabled on its shortcut, clear Properties > Compatibility > Run this program as an administrator. Different privilege levels can prevent dragging from Explorer.
In Project Manager (home icon), choose New Project and import the same file plus a previously working clip. Success there narrows the problem to the original project without proving corruption.
2. Add the Missing Folder to Media Storage
A drive visible in Finder or Explorer may be missing from Resolve’s browser. Adding its location makes it available in Media Storage, without adding codec support.
- Open DaVinci Resolve > Preferences > System > Media Storage.
- Click Add, select the media folder or drive, and click Save.

Resolve reads media from locations listed in Media Storage, so broken or missing entries can hide files from the Media page. - Restart Resolve, open the Media page, and browse that location. Drag the required clip from Media Storage into the Media Pool.
Keep the existing locations and order. The first entry affects default cache and gallery storage; changing it is unnecessary.
3. Check the Recording Format and Resolve Edition
Sound without a picture suggests Resolve can decode the audio but not the video. The filename extension alone cannot explain that difference.
- Open the original recording in the desktop version of MediaInfo and select View > Text.
- Read the video Format, Profile, Bit depth, Chroma subsampling and Frame rate mode, plus the audio format.

The extension only tells you the container, while the codec and bit depth decide whether Resolve can decode the media. - Check DaVinci Resolve > About DaVinci Resolve for your version and edition. Compare the file against the Decode column in Blackmagic’s supported-codec document for that release and operating system.
These distinctions come from the Resolve 21 codec list. For another major version, get its matching document from the Blackmagic Support Center.
| Format or system | What to check |
|---|---|
| Windows H.264 / HEVC | Free supports OS-supported 8-bit H.264 and 8/10-bit HEVC profiles. Studio supports additional profiles; not every 10-bit file requires Studio. |
| macOS | Do not apply Windows-only codec restrictions to a Mac. Check the macOS rows for the exact format. |
| Linux | H.264/H.265 require Studio in the cited list. AAC audio is unsupported, including in Studio; DNxHR with PCM audio avoids those limits. |
| AV1 or 4:2:2 camera footage | Match the profile and GPU requirements, not just the codec name. |
If MediaInfo cannot identify a video stream, re-copy or re-export the original recording. Missing metadata is not something a Resolve setting can reliably repair.
4. Make a Compatible Editing Copy
A compatible editing copy can avoid buying Studio for one troublesome format. Keep the original: conversion changes the recording, even when it looks similar.
- Add the clip to Shutter Encoder. Under Choose function, select DNxHR and a MOV output.
- Choose HQ for 8-bit video or HQX for higher bit depths. Keep the source resolution; under Audio settings, choose PCM and retain the required channels.

A clean constant-frame-rate editing copy is easier for Resolve to import and decode than unstable long-GOP or phone footage. - Select a separate output folder and click Start function. Allow extra disk space: DNxHR files are much larger than compressed camera recordings.
- Import the converted copy. Check picture, duration, colour and audio sync before converting the rest.
The screenshot uses Adobe Media Encoder; Shutter Encoder also exports DNxHR. Renaming .mp4 to .mov is not a conversion.
For variable-frame-rate screen recordings on Windows or macOS, another option is HandBrake’s H.264 (x264) with AAC audio. In Video, choose Same as source and Constant Framerate.
Variable frame rate can affect timing and playback; it does not make every recording incompatible.

HDR or log footage: retain its colour information with a suitable higher-bit-depth output. An SDR conversion is not required for import.
The illustration mixes interfaces: HandBrake’s Summary format selects a container, not a video codec. Follow the Shutter Encoder steps for DNxHR. A Windows HEVC extension does not unlock every camera profile.
5. Allow Access to the Folder Resolve Cannot Read
A clip that imports from one folder but not another deserves an access check before another conversion.
On macOS
- Open System Settings > Privacy & Security > Files & Folders.
- Enable Resolve’s access to the location containing your media, such as Downloads or Removable Volumes. Quit and reopen Resolve.

Permission blocks can make supported clips disappear or fail to import from protected folders and drives.
Apple’s folder-access controls allow narrower permissions.
If access still fails, open Privacy & Security > Full Disk Access, add the trusted Resolve installation and restart it. This grants broader access; remove it if nothing changes.
On Windows
Check the media folder’s Properties > Security tab for your account’s Read permission. On a managed computer, ask the administrator rather than changing ownership or disabling security.

The example shows Unblock on an Excel file, not a video-codec fix. Read-only media can still import. Controlled Folder Access protects writes; do not disable it for an import failure.
If the same file still fails from an accessible local folder, changing more security settings is unlikely to help.
6. Test a Short, Plain File and Folder Name
Names containing emojis or unusual characters have prevented imports even when the video itself was readable.
- Make a copy of an ordinary standalone video in a folder named ResolveMedia.
- Rename the copy to something short, such as
test-video.mp4, keeping its actual extension unchanged. Use plain letters, numbers, hyphens or underscores. - Import that copy and check playback.

Short local folders and simple file names remove a surprising number of file-access and import edge cases.
Leave camera-card structures and numbered image sequences intact. Renaming originals already used in a project can break their existing links.
7. Preserve Camera Folders and Group Image Sequences Correctly
Camera recordings can span several files or rely on neighbouring metadata. A numbered image sequence also needs different handling from separate photographs.
- Copy the entire camera-card structure to your editing drive, including its metadata folders. Do not rename or discard individual parts.
- Browse the copied folders from the Media page’s Media Storage panel.
- For numbered stills, open the three-dot menu in Media Storage, not the Media Pool menu, before importing.

Camera metadata folders and image-sequence settings can decide whether Resolve sees footage correctly.
- One continuous sequence: turn Show Individual Frames off.
- Separate still images: turn it on.
Import into a new bin; the option does not regroup existing clips. If the sequence appears correctly, keep that setting and leave clips used in existing edits alone.
8. Test Without H.264/H.265 Hardware Decoding
Supported H.264 or HEVC footage can still show black or intermittent offline frames when hardware decoding misbehaves. Software decoding is a reversible comparison, although playback may be slower.
- Open DaVinci Resolve > Preferences > System > Decode Options.
- If available, uncheck Decode H.264/H.265 using hardware acceleration. The screenshot highlights the checkbox; the test requires it to be off.

Disabling hardware decode helps confirm whether the import failure is tied to GPU decoding instead of the file itself. - Click Save, restart Resolve and test the same clip. Restore the setting if nothing changes.
The option varies by edition, platform and version. Its absence is not an installation fault, and turning it off cannot unlock an unsupported codec.
If the picture works only with decoding off, keep that workaround or use an editing copy.
On Windows, try a compatible GPU driver update from the GPU or computer manufacturer, then retest. Mac graphics-driver updates come through macOS.
If a driver update restores playback, re-enable hardware decoding and retest before keeping it disabled.
9. Clear Render Cache for Clips That Already Imported
Cache is relevant when the original plays correctly but an existing timeline shows stale or offline frames. It will not make an invisible or unsupported file import.
- Note the current cache mode, then select Playback > Render Cache > None and test the affected clip.

- If disabling cache restores the picture, select Playback > Delete Render Cache > All in that project.

Cache cleanup and current Resolve builds help when thumbnails, proxies, optimized media, or RAW plugins are stale. - Save and close Resolve, restart the computer, and reopen the project. Restore your preferred cache mode once playback works.

This removes generated render cache, not your source recordings or edits. Rebuilding it takes time. Proxies and optimized media are separate; this command does not clear them or repair RAW decoders.
When Supported Files Still Will Not Import
Before updating or reinstalling, export important projects: in Project Manager, right-click a project and select Export Project to save a .drp. Keep the original footage separately; a project export does not contain it.
Before a major upgrade, open the library pane in Project Manager, click its Info button and choose Back Up. Check the release’s OS/hardware requirements before installing a compatible stable Free or Studio build from Blackmagic’s Support Center.
Reinstalling does not remove format restrictions.
If a previously working clip still fails in a new project, report your import behaviour, Resolve version/edition, OS, GPU/driver, MediaInfo report and comparison results.
Free-edition support is through the Blackmagic community forum; Studio users can also contact Blackmagic Support. Share only material you have permission to disclose. If just one file fails, include that distinction in your report.





