# DaVinci Resolve Unable to Find Media Storage Location, Fixed

> **Quick answer:** DaVinci Resolve throws this error when a path in Preferences > Media Storage, usually the first one used for cache and gallery stills, no longer exists or can't be reached. Fix: open Preferences > Media Storage, remove the broken path, add the drive back with a local SSD listed first, then reopen the project and reconnect any offline clips.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-07-22 · DaVinci Resolve 21.0.2 (July 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-unable-to-find-media-storage-location-error*

You open a project, or you're mid-session and Resolve tries to write a cache file, and instead of working it stops cold with some version of the same message: it can't find a media storage location. No footage plays. No proxy generates. No gallery still saves. And your first thought, understandably, is that something just ate your project.

It didn't. This error is DaVinci Resolve telling you, in its own blunt way, that one folder path it depends on no longer exists where it expects it. That's a settings problem, and settings problems are fixable in minutes. Below is every place that path can break, in the order that actually clears the error fastest, followed by the harder cases: network drives, Blackmagic Cloud, projects handed off from another machine, and what to do if the straightforward fix doesn't stick.

## Why does DaVinci Resolve say it can't find a media storage location?

Resolve keeps a list called Media Storage Locations in Preferences, under the Media Storage tab. Think of it as the set of drives and folders Resolve is allowed to treat as scratch disks, places it can write to on its own, not just read from. Per Blackmagic's own manual, this list is what "defines the scratch disk of the system," and critically, "the first volume in this list is where Gallery stills and cache files are stored" ([DaVinci Resolve Manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part122.htm)). When any path in that list stops existing, a drive unmounts, a folder gets deleted or renamed, a network share drops, Resolve doesn't quietly work around it. It throws the error, because the thing it was told to treat as reliable storage just proved it isn't.

**A missing media storage location is a settings problem, not a data-loss problem.** Your footage sits wherever you originally imported it from, on a completely different path than the one Resolve is complaining about. The confusion happens because the symptom looks identical to real data loss: a frozen interface, clips refusing to load, an error that sounds final. It isn't. Here's the full list of what actually breaks this, ranked roughly by how often each one shows up in real reports:

| Cause | How common | What actually happened |
| --- | --- | --- |
| First Media Storage Location's drive disconnected or unmounted | Very common | The cache and Gallery stills path Resolve checks constantly went offline |
| External drive reassigned a different letter (Windows) or mount name (Mac) | Very common | The path string in Preferences no longer matches the drive's current identity |
| Folder deleted, renamed, or moved on an otherwise-connected drive | Common | The drive is fine, but the specific subfolder Resolve expects is gone |
| Project's own Working Folders settings point somewhere Preferences no longer lists | Common | The project-level cache/proxy/gallery path and the global Preferences path disagree |
| Network share or NAS mount dropped or changed address | Common | SMB, NFS, or a cloud-sync mount briefly disconnected or remounted under a new path |
| Blackmagic Cloud Project Library storage unreachable | Occasional | Cloud-linked storage lost connection, distinct from the local media cache path |
| Project opened on a different machine or OS than it was created on | Occasional | The saved path (a Windows drive letter, say) doesn't exist on this system at all |
| Permissions changed on the storage folder | Occasional | The path exists and is visible, but Resolve was denied write access to it |
| Cache drive full | Rare as the direct cause, common as a compounding factor | The path is technically reachable but Resolve can't write new cache data to it |

**DaVinci Resolve builds its working folders from the first entry in Media Storage Locations, so one broken path there can lock up cache, gallery stills, and every clip a project tries to load.** That single design choice is why this error feels so disproportionate to its actual cause. One folder goes missing, and suddenly nothing in the project seems to work.

## What's the fastest fix, step by step?

Before touching anything else, open **Preferences > Media Storage** and look at the Media Storage Locations list itself. In the large majority of reports across the Blackmagic Forum, the broken entry is visibly different from the others: greyed out, marked with a warning icon, or simply missing the drive icon the healthy entries show ([Blackmagic Forum: Media Storage Location](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=175162)).

1. **Identify the broken path.** It's usually, though not always, the first entry in the list, the one reserved for cache files and Gallery stills.
2. **Remove it.** Select the broken entry and click the minus button or Remove. This only deletes the reference inside Resolve. It has no effect on the actual folder or any files inside it.
3. **Add the correct path back.** Click Add, then browse to wherever that drive or folder currently lives. If the drive got a new letter or name, point Resolve at the new one, not the memory of the old one.
4. **Move a local SSD to the top of the list.** Drag your fastest, always-on internal or directly-attached drive to the first position. Reserve that top slot for cache and Gallery stills specifically; don't let a network share or removable drive sit there.
5. **Check the affected project's own Working Folders.** Open **Project Settings > Master Settings > Optimized Media and Render Cache**, and look at the Cache files location, Proxy generation location, and Gallery stills location shown under Working Folders. A project can hold its own stale path independent of what you just fixed in Preferences.
6. **Quit Resolve completely, not just the project, then relaunch it.** This forces Resolve to re-read the corrected Media Storage list from a clean state rather than carrying over whatever it had cached in memory.
7. **Relink any clips still showing offline.** In the Media Pool, right-click the red clips and choose Relink Clips for Selected Bins. Resolve automatically reconnects files with matching names once the underlying path problem is gone.

For most single-machine, local-drive setups, steps one through four alone clear the error. The remaining steps matter more once a project has actually been saved with the broken path baked into its own settings, which is the scenario covered next.

## What exactly is a Media Storage Location, and why does the first one matter so much?

It helps to actually understand what this list is for, because half of the confusion around this error comes from treating Media Storage Locations like a simple list of drives you import from. It isn't that. It's closer to a permission list: these are the only places Resolve is allowed to both read footage from and write its own working files to.

Per the manual, the Media Storage tab lets you configure several things per path, not just the folder location itself:

- **Mapped Mount**, which lets you specify "translatable media path mapping between Mac, Linux, and Windows file system conventions," so a shared project can resolve the same drive under different names on different operating systems ([DaVinci Resolve Manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part191.htm)).
- **Direct I/O**, which "allows DaVinci Resolve to write directly to the drive using the kernel buffers, bypassing the normal storage cache in RAM," intended to squeeze more sustained throughput out of a fast local drive ([DaVinci Resolve Manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part122.htm)).
- **List order**, which is the part most people never touch, and the part that causes this exact error more than any other single setting.

That last point is worth sitting with. Resolve doesn't ask you, each session, where to put cache files and Gallery stills. It just takes the first path in your Media Storage Locations list and combines it with two fixed folder names to build what's called the Working Folders path automatically, per Frame.io's own configuration documentation for Resolve setups: "DaVinci Resolve uses the first path listed in System > Media Storage > Media Storage Locations plus the names of two specific folders to create the expected Working Folders path" ([Frame.io V4 Knowledge Center](https://help.frame.io/en/articles/14442067-davinci-resolve-mounted-storage-optimization)). Those two folders are typically named CacheClip and .gallery, and they get created automatically the first time Resolve needs them, inside whatever drive sits first on your list.

**The first entry in your Media Storage Locations list is not decorative. It is where Resolve writes your cache and your Gallery stills.** If that entry is a drive that's asleep half the time, an external SSD you sometimes forget to plug in, or a network share with an unreliable connection, you've built a single point of failure into every session, whether you meant to or not.

This is also exactly why Blackmagic's own manual warns about what happens when that first entry stops being reachable: "If the volume you've selected to use for the cache becomes unavailable, DaVinci Resolve will warn you with a dialog" ([DaVinci Resolve Manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part122.htm)). That dialog is the error you're reading this article to fix. It isn't a bug. It's Resolve behaving exactly as documented, the moment its assumed-reliable first storage path turns out not to be reliable that day.

## Why does Resolve keep pointing at a drive that's already gone, even after you fix Preferences?

This is the part that frustrates people most, and it's the single most-repeated complaint pattern across forum threads on this topic going back years. You fix the path in Preferences. You reopen the same project. The error comes right back, sometimes referencing the exact same dead drive by name.

The reason is that Resolve stores this information in two places, not one. Global Preferences hold your Media Storage Locations list. But an individual project, once it's been saved at least once, also stores its own Working Folders paths under Project Settings, and those two records can drift apart. A project saved three months ago with an external drive as its cache location keeps that reference baked into its own settings, independent of whatever you've since changed in Preferences.

This exact pattern shows up on the Blackmagic Forum in a thread describing an error where users are told to "update the cache files location in project settings as the current location is offline or inaccessible," a message that reportedly appears often right after upgrading from one major Resolve version to another, such as 19.4 to 20 ([Blackmagic Forum](https://forum.blackmagicdesign.com/viewtopic.php?f=40&t=219785)). The upgrade itself isn't the cause. It's a trigger, because a version jump is one of the more common moments a preferences file gets rewritten or a previously-tolerated stale path finally gets checked and flagged.

It's also not a new problem specific to recent versions. On a Creative COW thread going back to Resolve 8 and 8.1, one user, Barry Goch, described losing the drive he'd set for cache and Gallery stills entirely: "The drive I had set on the config page as the location for the Cache files and Gallery Stills died," and found that simply changing the setting once didn't clear the problem. Another user, Jake Blackstone, explained the actual fix required going into each affected project individually: open the project, change the drive location there too, and in some versions delete and recapture stills so "Resolve will stop bugging you for the old drive" ([Creative COW](https://creativecow.net/forums/thread/resolve-working-folder-problem-cache-and-gallery/)). More than a decade and several major versions later, the underlying mechanism, a project holding its own stale path independent of global preferences, hasn't fundamentally changed.

**A path that worked yesterday can vanish today if a drive letter, a mount point, or a permission changes overnight**, and Resolve has no way to know that in advance. It only finds out when it tries to use the path and fails.

The practical fix: don't stop at Preferences. Open the specific project throwing the error, go to **Project Settings > Master Settings > Optimized Media and Render Cache**, and check the Working Folders section directly. If the Cache files location, Proxy generation location, or Gallery stills location shown there still references the dead path, correct it there explicitly. Do this for every project that was actively open or recently saved while the old drive was still connected, not just the one you happen to be working in right now.

## Is this the same problem as media offline, or something different?

No, and mixing them up sends people down the wrong troubleshooting path constantly. They feel related because they show up together so often, but they're not the same failure and they don't share a fix.

| | Media Storage Location error | Media offline (in Media Pool) |
| --- | --- | --- |
| What's actually missing | Resolve's own working folder: cache, proxy, or Gallery stills path | Your original source footage |
| Where it's fixed | Preferences > Media Storage, and Project Settings > Working Folders | Media Pool, right-click clip, Relink Clips |
| Typical trigger | A scratch drive, cache path, or its folder disappeared | Footage was moved, renamed, or its drive disconnected |
| Does it block playback of everything | Yes, cache and background operations across the whole project | No, only the specific clips whose source moved |
| Does relinking clips fix it | Not directly, though clips often reconnect on their own afterward | Yes, this is the direct and correct fix |

The overlap happens because a broken storage location can make Resolve unable to do the background reads and writes it needs to render thumbnails, waveforms, and proxies, and clips that can't complete that background work sometimes get flagged offline as a side effect, even though the source file itself is perfectly fine and still sitting where you left it. If you jump straight to relinking clips without fixing the underlying storage path first, you'll relink the same footage, watch it go offline again a few minutes later, and conclude, wrongly, that your drive or your files are corrupted.

**The drive did not lose your footage. Resolve just stopped looking in the right place for its own scratch files.** Fix the storage location error first. If clips are still red afterward, then move to relinking them in the Media Pool as a separate, second step.

## How do you fix it when the storage is a network share, NAS, or Blackmagic Cloud?

Network and cloud storage make this error more likely, not less, because the connection itself has more ways to fail than a local drive plugged directly into your machine. A Wi-Fi hiccup, a VPN reconnecting, a NAS going to sleep, or a cloud-sync client remounting a share under a slightly different address are all invisible to you in the moment and instantly fatal to a path Resolve was relying on.

Frame.io's guidance for setting up Resolve against mounted or shared storage is direct on the ordering question: "Make sure the first path in the list is a local SSD, not a mounted Project," and only after that's established should you "add your team's Mounted Storage drives to the list" as additional entries ([Frame.io V4 Knowledge Center](https://help.frame.io/en/articles/14442067-davinci-resolve-mounted-storage-optimization)). Cache files and Gallery stills specifically should stay on local SSD storage, never on the network drive, for both reliability and speed. The same source recommends enabling Direct I/O for each entry in the Media Storage list once local-first ordering is in place.

For Blackmagic Cloud Project Libraries specifically, there's an added wrinkle: the cloud connection governs your project database and collaboration state, while your actual media cache path is a completely separate, local concern. Losing the cloud connection can produce error dialogs that look similar to a media storage location failure but stem from an unrelated cause, your internet connection or Blackmagic Cloud's service status, rather than a local drive problem. If the error appears specifically after a Wi-Fi drop or while working from a Blackmagic Cloud Project Library, check your internet connection and Blackmagic's own service status before touching local Media Storage settings at all.

Practical checklist for network and cloud setups:

- Keep a local SSD as the first Media Storage Location, always, no exceptions for convenience.
- Add NAS, SMB shares, or cloud-synced drives as second, third, or later entries, used for footage, not cache.
- If a share reconnects under a new address after your router or NAS restarts, that new address needs to be re-added; the old one won't auto-update.
- For Blackmagic Cloud Project Libraries, treat a connectivity failure as a separate troubleshooting branch from a local storage location error, even though the symptoms can look alike.
- Avoid syncing your cache or Gallery stills folder itself through Dropbox, Google Drive, iCloud, or similar clients; those clients write their own lock files into synced folders, which is a documented cause of exactly this kind of path confusion and, in worse cases, project corruption.

## What if the error appears when you open a project from another machine or a different OS?

This is one of the more common triggers, and it's structural rather than accidental. A project created on a Windows machine stores its Working Folders paths using Windows drive-letter conventions, something like `D:\Resolve\Cache`. Open that same project on a Mac, and there is no `D:\` drive, full stop. The path doesn't exist because the entire addressing scheme is different, not because anything went missing.

This is exactly what Mapped Mount and Path Mapping exist to solve. Blackmagic's manual describes Path Mapping as letting teams "set up your project's media locations so that they can easily be shared and translated with other DaVinci Resolve users," and specifically calls out that a single user moving between systems, say a laptop used both in an office and remotely, "could setup a link from their local media folder to their NAS" and have Resolve translate between the two automatically rather than relinking everything by hand each time ([DaVinci Resolve Manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part191.htm)).

Without that mapping configured in advance, a project handed off across machines or operating systems will almost always throw a storage location error the first time it opens somewhere new, because it's looking for a path that has no equivalent on the new system at all. The fix in the moment is the same as everywhere else: open Preferences > Media Storage on the new machine, add the correct local path, and update the project's own Working Folders settings to match. The fix for next time is setting up Path Mapping before you hand the project off, so Resolve translates the path automatically instead of erroring out.

A related but distinct trigger: opening a project that was last saved by a newer version of Resolve using an older installation. Version upgrades occasionally change how paths or database formats are handled internally, and an older copy of Resolve encountering settings it doesn't fully recognize can misreport them as missing rather than simply incompatible. If the machine throwing the error is running an older Resolve version than whatever last touched the project, update it to match before assuming the storage path itself is the problem.

## Does this look different on Windows versus Mac?

The underlying mechanism is identical on both platforms, Resolve losing track of a path it depends on, but the specific way that path breaks differs enough to matter for troubleshooting.

**On Windows:**
- Drive letters aren't permanent. Plugging in additional USB devices, or Windows reassigning letters after a reboot, can silently turn your `E:` drive into `F:`, and Resolve's saved path still says `E:`.
- Real-time antivirus scanning a cache folder can intermittently block writes to it, which produces symptoms that look like a missing path even though the folder still technically exists.
- Long, deeply nested project folder structures can bump into Windows' historical 260-character MAX_PATH limit, especially on cache and proxy subfolders that already have long auto-generated names.
- External drives formatted exFAT for cross-platform use occasionally get remounted read-only after an unclean disconnect, which Resolve can report as an inaccessible path rather than a permissions issue specifically.

**On Mac:**
- macOS permission prompts around Full Disk Access and folder access, particularly for drives or folders outside your user directory, can block Resolve from writing to a path that's otherwise perfectly intact and visible in Finder.
- External drives that go to sleep under macOS power management, or that were connected through a dock or hub that itself lost power, disappear from Resolve exactly the same way a physically unplugged drive would.
- SMB network shares mounted through Finder sometimes unmount silently after a sleep/wake cycle, without any visible warning until Resolve tries to use the path and fails.
- Case-sensitive versus case-insensitive APFS volumes can, in rare setups, cause a path that matches visually in Finder to not match exactly what Resolve has stored internally.

Neither platform is inherently more prone to this error than the other. The failure just wears a different disguise depending on which operating system's specific quirks happen to be in play that day.

## How do you stop this from happening again?

Once the immediate error is cleared, the more useful question is preventing the next one. A few habits account for most of the difference between editors who see this error once a year and editors who fight it every few sessions.

**Reconnecting a path takes two minutes. Rebuilding a project from scratch takes a weekend.** That asymmetry is the entire argument for spending five minutes on prevention now.

1. **Dedicate one always-on local SSD specifically as your first Media Storage Location.** Not a drive you sometimes unplug for other work, not the same external drive you use to back up your phone. One drive, always connected, always first on the list.
2. **Never let a network share, cloud-sync folder, or removable drive sit first in the Media Storage Locations list.** Add them as additional entries below your dedicated local drive, for footage access, not for cache or Gallery stills.
3. **Set up Path Mapping in advance for any project that will move between machines or operating systems**, rather than discovering the mismatch the first time someone else opens it.
4. **Check Project Settings > Working Folders after any drive reshuffle**, a new external SSD, a NAS migration, a fresh install on a new machine, before you assume Preferences alone covers it.
5. **Avoid syncing your cache, proxy, or Gallery stills folders through Dropbox, Google Drive, or iCloud.** Those clients actively write metadata and lock files into synced folders while Resolve is trying to write its own data, a documented source of exactly this kind of path confusion.
6. **Leave real free space on your cache drive.** A technically-reachable but full drive can produce write failures that present almost identically to a missing storage location, and it's an easy thing to rule out early rather than last.
7. **After any major Resolve version upgrade, open Preferences > Media Storage once, deliberately, and confirm every entry still resolves correctly**, rather than waiting for an error to tell you one didn't.

## What is a Media Storage Location conceptually, and why does DaVinci Resolve organize storage this way at all?

It's worth zooming out for a moment, because the design decision behind Media Storage Locations explains a lot of behavior that otherwise looks arbitrary. Long-time DaVinci Resolve trainer Larry Jordan, describing how Resolve fundamentally differs from Premiere Pro or Final Cut Pro in how it handles projects, put it plainly: "Resolve doesn't store files by project. Instead, it stores everything inside a folder which YOU create when you first install Resolve" ([Larry Jordan](https://larryjordan.com/articles/how-i-lost-all-my-davinci-resolve-projects-and-how-you-can-save-yours/)).

That single architectural choice ripples through everything covered in this article. Resolve isn't managing one project's cache in isolation. It's managing one shared pool of scratch storage, defined by your Media Storage Locations list, that every project you touch draws from. Media files stay separate from that pool entirely, which is why a broken cache path never means lost footage. But it also means a single bad entry in that one shared list can affect every project you open, not just the one you happened to be working on when the drive disappeared.

Understanding it this way changes how you troubleshoot. You're not debugging one project's settings. You're debugging one shared resource list that every project depends on identically. Fix it once, correctly, with a dedicated local drive at the top, and the fix protects every project you'll ever open on that machine, not just the one throwing the error today.

## What if you've tried everything and the error still won't clear?

Most cases resolve with the steps above. A small number don't, and they tend to fall into one of a few remaining categories.

**Permissions the operating system is silently blocking.** On Mac, check System Settings > Privacy & Security > Full Disk Access and confirm DaVinci Resolve is listed and enabled. On Windows, right-click the drive or folder in question, check Properties > Security, and confirm your account has full read/write access, not just read.

**A corrupted preferences file rather than a genuinely missing path.** If the path shown in Preferences looks correct, the drive is definitely connected and accessible in Finder or File Explorer, and the error persists anyway, Resolve's own preferences file may have become corrupted. Blackmagic support can walk you through resetting preferences to default, which clears this class of problem but requires re-entering any other custom preferences you've set.

**A genuinely dead drive**, not asleep, not disconnected, actually failed. If the drive doesn't mount at all in Disk Utility or Disk Management outside of Resolve, this stops being a Resolve problem and becomes a hardware recovery problem. Stop trying to fix it inside Resolve's preferences and address the drive itself first.

**Database-level issues masquerading as a storage error.** In rarer cases, what looks like a Media Storage Location error is actually a symptom of a project database problem, particularly after an unclean shutdown or a shared database being written to from two machines at once. If storage paths check out completely correct and the error still won't clear, it's worth ruling out database corruption as a separate track, which is its own troubleshooting path with its own fixes.

If none of the above resolves it, Blackmagic support can often help directly, particularly if you can supply your project file and a description of exactly which path is failing. Community threads on the Blackmagic Forum are also worth searching for your exact symptom; this is one of the more heavily documented recurring issues in Resolve's own user community, across versions going back over a decade ([Blackmagic Forum: Davinci Can't Find Media](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=225864)).

## Does using an AI assistant while editing help you catch this kind of thing sooner?

Some editors reach for a course or a written guide the moment something in Resolve breaks. That works, eventually, but it means translating a written instruction written for someone else's screen onto your own project, your own drives, your own file paths, which is exactly the kind of setting-by-setting troubleshooting this article has walked through.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words, and Uncle points at the exact control on your screen. Instead of reading "open Preferences > Media Storage" and hunting for it yourself, you ask what's wrong and Uncle draws a box around the exact entry in your actual Media Storage Locations list that's causing the problem, live, on your actual project.

That's a different category of tool than the alternatives currently getting recommended for Resolve. Assistants like Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai mostly automate edits or answer questions in a separate chat window, disconnected from what's actually on your screen. TryUncle instead watches your screen directly and shows you where a setting or a control lives inside Resolve itself, which matters specifically for a problem like a broken storage path, where the fix is finding the right checkbox or the right list entry inside your own preferences, not getting a generic written answer that doesn't reference your machine at all.

TryUncle is a paid macOS app, currently in founder pricing for early seats, cancel anytime; check [TryUncle](https://tryuncle.com/?utm_source=davinciresolve21&utm_medium=blog&utm_campaign=davinci-resolve-unable-to-find-media-storage-location-error) for the current rate. It's macOS only, and it needs an internet connection since the reasoning that understands your screen runs in the cloud. If you're on Windows or working offline most of the time, it isn't an option for you right now, and a written guide like this one is the better fit.

## Related problems worth checking while you're in here

A few adjacent issues tend to travel with this one, and it's worth ruling them out while your Media Storage and Project Settings are already open.

If imports were also stalling before this error appeared, that's frequently the same root cause wearing a different face: [DaVinci Resolve import stuck at 0 percent](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-import-stuck-at-0-percent) covers the full list of causes, including a missing scratch disk entry identical to what's covered here, alongside codec decode issues and cloud-sync placeholder files that produce a similar-looking freeze.

If a whole project seems to have disappeared rather than just thrown a storage error, that's a different failure with a different fix, covered in [DaVinci Resolve project not showing in Project Manager](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-project-not-showing-in-project-manager). A missing project is almost always a wrong-database or wrong-library problem, not the same mechanism as a broken cache path.

Since a lot of what causes storage location errors, cloud-synced database folders, drives running low on space, unclean shutdowns, overlaps heavily with what causes outright project corruption, it's worth reading [how to prevent DaVinci Resolve project corruption](https://tryuncle.com/learn/davinci-resolve/how-to-prevent-davinci-resolve-project-corruption) alongside this one. The prevention habits in both articles reinforce each other rather than duplicating.

And if you're not entirely sure what your current autosave and backup settings actually are, which matters a lot when you're mid-troubleshooting and don't want to risk losing work, [DaVinci Resolve Live Save settings explained](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-live-save-settings-explained) covers exactly what's protecting you right now and what isn't.

## The verdict

This error looks catastrophic and almost never is. It's Resolve refusing to proceed because one folder path it depends on, usually the first entry in your Media Storage Locations list, stopped being reachable. Fix that path in Preferences, check the affected project's own Working Folders settings separately, put a dedicated local SSD first on the list going forward, and this specific error stops being a recurring event in your editing life rather than a monthly fire drill.

If you're still fighting it after working through every step above, stop suspecting your footage and start suspecting the specific mechanism: permissions, a genuinely dead drive, or a corrupted preferences file. All three have known fixes. None of them mean your project is gone.

## FAQ

### What does DaVinci Resolve's Unable to Find Media Storage Location error actually mean?

It means one of the folder paths in Preferences > Media Storage, the list of Media Storage Locations Resolve treats as its scratch disks, no longer points at a real, reachable folder. Usually it's the first entry in that list, the one Resolve reserves for cache files and Gallery stills, since that's the path it checks most aggressively on launch and on every save. The drive got unplugged, renamed, reassigned a new letter, or the folder itself was deleted or moved, and Resolve is telling you flatly that it can't do the background work it needs to do without it.

### Did I lose my media, or just my settings?

Almost always just your settings. Your original footage lives wherever you imported it from, a completely separate concept from Media Storage Locations, which govern where Resolve writes its own working files: cache, proxies, and Gallery stills. The error is Resolve failing to find a folder it manages itself, not failing to find your source clips. Clips can still show offline afterward, but that's usually a side effect of Resolve refusing to do background work while the storage location is broken, not the original cause.

### Why does DaVinci Resolve keep asking for a drive that's already disconnected, even after I fix the path?

Because the broken path can be saved in two different places at once: your global Preferences and the individual project's own settings, inherited from whichever Working Folders configuration was active the last time that project saved. Fixing Preferences alone doesn't retroactively rewrite a project that already committed a specific cache and gallery path to its own database. You often need to open the affected project, go to Project Settings > Master Settings > Working Folders, and repoint the cache and gallery paths there too, on top of fixing Preferences globally.

### Is this the same problem as media showing offline in the Media Pool?

No, though the two frequently show up together and get confused. Media offline means Resolve can't find your source footage, the actual video files you imported, and the fix is relinking clips in the Media Pool. Unable to Find Media Storage Location means Resolve can't find its own working folder, the place it writes cache, proxies, and stills, and the fix is in Preferences and Project Settings, not the Media Pool. Fix the storage location first. Clips that show offline because Resolve was stuck often reconnect on their own once the underlying path error clears.

### Does this happen on network drives, NAS, or Blackmagic Cloud projects too?

Yes, more often than on local drives, because network paths are more likely to sleep, get remounted under a different address, or briefly drop during a Wi-Fi hiccup. The fix is the same in principle, repoint Media Storage to a reachable path, but the recommended setup differs: keep your first Media Storage Location on a local SSD for cache and Gallery stills, and add your network or cloud storage as a second or third entry for actual footage. That single ordering choice prevents most of the network-drive version of this error before it starts.

### Is there an app that helps you while using DaVinci Resolve catch a broken storage path before it turns into this error?

Yes. TryUncle is a paid macOS app whose assistant, Uncle, watches your DaVinci Resolve screen and can point at your actual Media Storage list and Working Folders settings live, on your actual project, so you can see which path is broken and where, instead of guessing from memory or a years-old forum screenshot that doesn't match your version.

### What's the very first thing I should check when this error appears?

Open Preferences > Media Storage and look at the Media Storage Locations list before you touch anything else. Any path shown in red, greyed out, or missing its drive icon is the broken one. In the large majority of reports, it's the very first entry in the list, the one Resolve uses for cache and Gallery stills by default, and fixing that one path alone resolves the error without needing to touch Project Settings at all.

## Sources

- [DaVinci Resolve Manual: Media Storage (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part122.htm)
- [DaVinci Resolve Manual: Project Media Locations and Path Mapping (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part191.htm)
- [Frame.io V4 Knowledge Center: DaVinci Resolve Mounted Storage Optimization](https://help.frame.io/en/articles/14442067-davinci-resolve-mounted-storage-optimization)
- [Larry Jordan: How I Lost All My DaVinci Resolve Projects, and How You Can Save Yours](https://larryjordan.com/articles/how-i-lost-all-my-davinci-resolve-projects-and-how-you-can-save-yours/)
- [Blackmagic Forum: Update the cache files location in project settings](https://forum.blackmagicdesign.com/viewtopic.php?f=40&t=219785)
- [Creative COW: Resolve Working Folder Problem, Cache and Gallery](https://creativecow.net/forums/thread/resolve-working-folder-problem-cache-and-gallery/)
- [Blackmagic Forum: Media Storage Location](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=175162)
- [Blackmagic Forum: Media Storage, First Location Is Not Where Cache Is Stored](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=73566)
- [Blackmagic Forum: Cache File Location Won't Save](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=69659)
- [Blackmagic Forum: Davinci Can't Find Media (Any of It)](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=225864)
- [WP Email Log: Why DaVinci Resolve Won't Import Media and How to Fix It](https://wpemaillog.com/2025/10/31/why-davinci-resolve-wont-import-media-and-how-to-fix-it/)