Cutsio Blog

[DaVinci Resolve Project](https://cutsio.com/blog/how-to-fix-corrupted-project-files-davinci-resolve) Won't Open: 9 Ways to Fix It

Fix a DaVinci Resolve project that will not open by checking backups, databases, disk space, plugins, cache, permissions, and corruption.

A project not opening in DaVinci Resolve is typically caused by a corrupted cache, an incompatible plugin, or a database connection error.

Here are the direct methods to fix a project that refuses to open.

How do you fix a DaVinci Resolve project that will not open?

Fix a DaVinci Resolve project that will not open by protecting the original project, checking disk space and database access, bypassing suspect plugins, and opening a backup or duplicate before attempting repair. Cutsio can preserve searchable source footage outside the project file, which makes a damaged Resolve project less costly to rebuild.

If DaVinci Resolve crashes immediately while loading the project, a third-party OpenFX plugin or audio VST is likely crashing the software.

To open a project by bypassing plugins:

1. Open DaVinci Resolve and wait for the Project Manager window to appear.
2. Do not click your project yet.
3. Hold down the Shift key on your keyboard.
4. While holding Shift, double-click your project to open it. This launches the project in "Safe Mode," temporarily disabling all plugins so you can delete the corrupted effect causing the crash.

How do you fix a project stuck at 100% loading?

If the project loading bar reaches 100% but freezes forever, the render cache or optimized media folder is corrupted and confusing the software.

To fix a project stuck at 100% loading:

1. Close DaVinci Resolve completely (Force Quit if necessary).
2. Open your operating system's file browser (Finder or Windows Explorer).
3. Navigate to your DaVinci Resolve CacheClip folder. (By default, this is usually in your main video drive or Documents folder, depending on your initial setup).
4. Delete the folder inside CacheClip that corresponds to your project, or delete all contents within CacheClip.
5. Reopen DaVinci Resolve. The project will now open and slowly rebuild the cache from scratch.

How do you fix database connection errors?

If the Project Manager is entirely empty or says "Local Database Disconnected," DaVinci Resolve cannot find the folder where your project files are saved.

To fix a disconnected database:

1. Click the Project Libraries button (top left of the Project Manager window).
2. Click the Add Project Library button.
3. Select the Connect tab.
4. Click Browse and navigate to the folder on your hard drive where your Resolve database was stored (usually C:\Users\[Name]\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\Resolve Disk Database on Windows, or Library/Application Support/Blackmagic Design/DaVinci Resolve/Resolve Disk Database on Mac).
5. Click Connect to restore access to your projects.

How do you restore an auto-save backup?

If the project file itself is completely unreadable, you must load an auto-save backup.

To restore an auto-save backup:

1. Open the Project Manager.
2. Right-click the project that won't open.
3. Select Project Backups.
4. A list of recent auto-saves will appear. Select the most recent working backup and click Load. Resolve will create a copy of the project from that exact moment.

How do you tell whether the project or the database is damaged?

Try opening a different project from the same database. If other projects open normally, the failing project or one of its dependencies is the likely problem. If no projects open, test the database connection, disk permissions, available storage, and Resolve installation before repairing an individual project.

Create a new empty project and import a small test clip. This separates a project-file problem from a media, GPU, or application problem. Do not repeatedly force-open the original while troubleshooting; work from a duplicate or backup so a failed repair does not remove your best recovery point.

What should you check before restoring a backup?

Check the backup timestamp, timeline version, media paths, and recent editorial changes before loading an auto-save. A backup may open successfully but predate the latest work. Save the restored copy under a new name and compare it with the original rather than overwriting the only project reference.

Also check for third-party plugins, missing fonts, offline media, and external database paths that the backup expects. A project can appear to freeze while it waits for a network volume or plugin to respond. Disconnecting a problematic dependency on a duplicate test can reveal the actual boundary.

How can you prevent a Resolve project from becoming unrecoverable?

Enable regular project backups, keep the database on reliable storage, and create named versions at major milestones. Store project backups separately from the only copy of the source media. A backup protects the project structure; it does not replace camera originals, audio, graphics, or exported masters.

For footage-heavy workflows, keep source material searchable outside the Resolve project as well. Cutsio's Visual Intelligence can help locate the relevant clips when a project must be rebuilt, while Resolve remains the finishing environment for timelines and grades.

FAQ

Why does DaVinci Resolve freeze while opening a project?

Resolve may be waiting on a plugin, network storage, missing media, corrupted cache, or a damaged project database.

Should you delete the project that will not open?

No. Preserve the original and attempt recovery from a duplicate, backup, or auto-save copy.

Can a backup restore missing source media?

No. A project backup restores project structure and settings, but the original media still needs to be online or relinked.

How do you reduce the chance of a future project-opening failure?

Keep Resolve updated within a tested version, avoid filling the system drive, maintain project backups, and close external media or database services cleanly before shutting down. Create a recovery copy before installing a new plugin or changing the database location.

When a project includes large source libraries, keep those originals separately backed up and searchable. Cutsio can help recover the editorial context and locate source footage when a Resolve project must be restored from an older backup.

How do you recover when both the project and database seem unavailable?

Work from the narrowest recovery boundary. First test a new project, then reconnect the database, then open a duplicate or auto-save. Check whether the database folder is readable and whether the account has permission to access it. If the database is on removable or network storage, copy a recovery version to a local working disk before testing.

Do not delete database folders, cache directories, or project backups while diagnosing the issue. Preserve the original state, record the paths you tested, and make each repair against a copy. Once a project opens, immediately save a new version and verify the timeline, media, and recent edits.

What should you do after a project opens again?

Save the recovered copy under a new name, check the timeline and media pool, and render a short section before resuming production. Reconnect plugins and external storage one at a time so a second failure does not hide the original cause.

Keep the damaged project untouched until the recovered copy has passed those checks. If only the project database was affected, export or duplicate the working project into a healthy database and record the recovery date.

If the project opens only after plugins or media are disconnected, reconnect those dependencies one at a time. The first dependency that reproduces the failure is the best lead for a permanent fix. Keep a working recovery copy before attempting the plugin update or media relink.

After recovery, create a named milestone backup before making new edits. Check the project on the same storage and account that will be used for the next session, because a project that opens only under one temporary path is not fully recovered.

Use a recovery checklist for future incidents: preserve the original, test another project, test a new project, verify the database path, check free space, disable suspect plugins on a copy, load an auto-save, then save a new milestone. This order keeps the problem bounded and avoids destructive trial and error.

Document the working Resolve version and plugin set alongside the recovered project. Reopening a project on a different version or machine can introduce a second variable, so keep the recovery environment stable until the project has been checked and backed up.

If a backup opens cleanly, compare its timelines and recent media with the failed project before continuing. Restore only the work you need, then create another backup immediately. This gives the team a known-good recovery point instead of turning the emergency copy into the next single point of failure.

Avoid treating a successful open as proof that every dependency is healthy. Scrub a representative timeline, check audio playback, open the Media Pool, and perform a short test export. A project can load while still containing offline files or a plugin that will fail later during rendering.

Confirm the recovered project remains usable after restarting Resolve once.