DaVinci Resolve crashing on Mac: causes and fixes

When DaVinci Resolve keeps crashing on a Mac, the cause is usually one of six things: a version that does not match your macOS release, GPU or memory pressure, a stale cache, a damaged project or database, a third-party OpenFX plug-in or font, or a specific media file Resolve struggles to decode. Protect your project first, note exactly when the crash happens, then work through the list below in order. In many cases one of these steps isolates the cause, and if none does, you will have the evidence Blackmagic support asks for.

Protect the project before you troubleshoot

Resolve does not save projects as loose files the way many editors do. They live inside a project library (called a database in older versions), so a crash at the wrong moment can affect more than one timeline.

1. Open the Project Manager, right-click the project and choose Export Project to write a .drp file somewhere safe. Do this for every project you care about.
2. If you can, back up the whole library from the Project Manager as well. A library backup is the only copy that carries every project at once.
3. Check Preferences > User > Project Save and Load. Turn on Project Backups if it is off, and note where backups are written. Live Save is useful too, but it saves over the same project, so it is not a substitute for backups.

Then write down the pattern: on launch, when one project opens, on a particular page, on certain clips, or at random after a long session. Each points somewhere different.

Step 1: Check your Resolve and macOS versions

Version mismatch is a common cause of Mac crashes: a new macOS release installed before Resolve supports it, or a fresh Resolve update with a bug that affects your setup.

• Open the release notes for your Resolve version on the Blackmagic support site and check which macOS versions it lists as supported. If yours is newer than anything listed, that alone may explain the crashes.
• If the crashes started right after updating Resolve, the update is the main suspect. Older installers are available from the Blackmagic Design support page.
• Before rolling back, remember that opening a project library in a newer version can upgrade it, and an older version may not open it afterwards. That is why the export and backup above matter. Our guide to what to do when a software update broke your project covers this trap in more detail.

Step 2: Look at GPU and memory pressure

Resolve leans heavily on the GPU, and on Apple silicon the GPU shares unified memory with everything else on the Mac. When that memory runs short, you may see a "GPU memory full" message, or Resolve may simply quit.

• In Preferences > System > Memory and GPU, confirm that GPU processing mode is set to Metal or Auto, and that the memory limits have not been changed to something unusual.
• Close other heavy apps and watch memory pressure in Activity Monitor while you reproduce the crash.
• Lower the timeline proxy resolution or playback quality while you work, and switch off temporal noise reduction and other heavy effects temporarily to see if the crash stops.

If crashes cluster on the Color page or during playback of graded shots, read our dedicated guide on the DaVinci Resolve GPU memory full error. The causes overlap heavily.

Step 3: Clear caches and check disk space

Render cache, optimized media and proxies make Resolve faster, but a half-written cache file can trigger crashes during playback or scrubbing.

1. Use Playback > Delete Render Cache and choose to delete all.
2. In Preferences > Media Storage, check where the cache is written. Put it on a fast drive with plenty of free space.
3. Make sure your startup disk is not nearly full. A Mac with very little free space struggles with swap, and Resolve is one of the first apps to show it.

Relaunch and test. The first playback will be slower while caches rebuild.

Step 4: Test the project and the library

If one project crashes and a new, empty project does not, the problem is in the project, not the app.

• Import your exported .drp into a fresh project library and open it there. This rules out damage elsewhere in the old library.
• Duplicate the problem timeline and delete half of it. If the crash goes away, the problem is in the half you removed. Keep halving until you find the clip, effect or Fusion composition responsible.
• If the project will not open at all, restore the most recent file from your project backups. For a broader walk through recovery options, see lost work after a frozen save.

Step 5: Rule out plug-ins and fonts

Third-party OpenFX plug-ins load inside Resolve, so one outdated plug-in can bring down the whole app, sometimes only on a particular page or at render time.

1. On a Mac, OpenFX plug-ins are usually installed in /Library/OFX/Plugins. Move the contents to a folder on your desktop temporarily.
2. Relaunch and test. If Resolve is stable, return the plug-ins a few at a time until the crash comes back.
3. Check each vendor's site for compatibility with your exact Resolve and macOS versions, and update or remove the culprit.

Fonts are a less obvious suspect. Editors regularly report that a damaged or duplicate font can crash Resolve on launch or when a title is opened. If the crash happens on launch or on the Edit page with titles, validate your fonts in Font Book and disable recently installed ones as a test.

Step 6: Find the media file Resolve cannot handle

If the crash happens when you play, scrub or render particular clips, the source media is the suspect.

• Variable frame rate phone recordings, screen recordings and some long-GOP camera formats are frequent troublemakers. Transcode the suspect clips to ProRes, relink and test again.
• Generating optimized media or proxies for the timeline is a quick way to tell decoding problems apart from everything else.
• Check whether the decode path differs between the free version and DaVinci Resolve Studio for your codec. Hardware decoding support varies by version and format, so confirm in the release notes for your version rather than assuming.

If a single file reliably crashes Resolve, keep a copy. It is the most useful thing you can send to support.

What to send Blackmagic support

When nothing above helps, contact support with evidence instead of a description.

• Use Help > Create Diagnostics Log on Desktop right after a crash. It gathers logs and system information into one archive.
• Include your exact Resolve version, whether it is the free version or Studio, your macOS version and your Mac model.
• Describe the crash pattern you wrote down at the start, and the steps you have already tried.
• If a specific clip or project triggers it, say so, and offer a short sample file if you are allowed to share it.
• Open the Console app, look under Crash Reports for recent Resolve entries, and note any plug-in or library name near the top of the crashed thread.

If project names or paths are confidential, check the archive before sending it.

When crashes keep coming back

Sometimes Resolve still crashes on your particular setup. That is not a verdict on Resolve, which remains one of the strongest editing and grading tools on the Mac. But if instability is costing you deadlines, it is reasonable to look at how other editors behave when something goes wrong.

cinemaOS is a Mac-native editor for Apple silicon, built by Momentum Studios. The part of its design that matters here is that projects are local-first .mntm files with recovery, saved on your own drive rather than inside a shared project library. Recovery cannot recreate source media that no longer exists, and no editor can promise it will never crash, so keep backups whichever tool you use.

If you want to try it on a real project, Resolve can export your timeline as an XML or EDL, and cinemaOS imports it and shows a conform report with any warnings to review. The tutorial on importing a cut shows the steps. Grades, Fusion compositions and effects do not translate, so expect to rebuild those. cinemaOS costs $9.99 USD per month excluding VAT, with 60 days free, no card and no automatic charge.

FAQ

Is the free version of DaVinci Resolve more likely to crash on a Mac?

Not inherently. The free version and Studio share most of their code, and both can crash for the reasons above. Studio adds some heavier tools, so the specific crash can differ, but the troubleshooting order is the same.

Will reinstalling DaVinci Resolve fix the crashes?

Sometimes, if the installation itself is damaged. More often the cause is a plug-in, font, cache, project or media file that survives a reinstall. Export your projects and back up your library first, then reinstall only after you have worked through the other steps.

Can I lose my projects if Resolve crashes during a save?

It is possible, which is why exported .drp files and project backups matter. Projects live inside a library, so back up the library regularly and keep exports of important projects on a separate drive. If a project will not open after a crash, restore from the most recent backup rather than repairing the only copy.