DaVinci Resolve "GPU memory full" on Mac: how to fix it

When DaVinci Resolve says the GPU memory is full on a Mac, it means the image processing for the current frame needs more graphics memory than Resolve can get. The fastest fixes, in order: lower the timeline resolution while you work, ease off temporal noise reduction, trim or cache heavy nodes, and play from optimized or proxy media. In many cases of "davinci resolve gpu memory full", the first two changes are enough. Below: why it happens, how to find the clip that triggers it, and how to stop it coming back.

The message itself usually suggests a lower timeline resolution or fewer correctors. Take that literally: those are the two biggest levers.

Why Resolve runs out of GPU memory on a Mac

Resolve does nearly all of its image processing on the GPU. Every frame you play is decoded, scaled to the timeline resolution, then passed through each node, effect and Fusion tool on the clip. Each step can hold its own copy of the frame in memory, and some effects hold several frames at once.

How much room there is depends on the Mac.

• Apple silicon. The CPU and GPU share one pool of unified memory. There is no separate graphics card with its own fixed amount, but macOS limits how much of that pool the GPU may use, and everything else open on the Mac draws from the same pool. A 16 GB machine running Resolve, a browser and a messaging app has noticeably less headroom than the number on the box suggests.
• Intel Macs with a discrete GPU. The graphics card has its own fixed video memory, often modest on laptops. Once that fills, there is nowhere else for the frame to go.

So the error is rarely a bug. It is a sum: frame size, times the operations that need a full copy of the frame, against the memory free at that moment.

Find the clip that triggers it

Before changing settings, note where the error appears. It almost always shows up on specific clips, not across the whole timeline.

• Play through the timeline and mark the clips where the warning or a red playback indicator appears.
• On each one, open the Color page and look at the node tree. Count the nodes and note any heavy tools: temporal or spatial noise reduction, Magic Mask, Face Refinement, lens blur style effects, Super Scale in Clip Attributes, or a Fusion composition.
• Disable nodes one at a time (select a node and toggle it off) until playback recovers. The node that brings the error back is your main suspect.

This saves you from lowering quality across a whole project to fix three shots.

What to change first

1. Lower the timeline resolution while you work

This is usually the most effective fix. Open Project Settings, then Master Settings, and set the timeline resolution lower, for example 1920x1080 instead of UHD or 6K. Every node and effect then processes a smaller frame, which cuts memory use substantially. If a timeline uses its own settings rather than the project defaults, change the resolution in that timeline's Timeline Settings instead.

Resolve is resolution independent, so sizing, windows and tracking scale with the change. Two cautions apply. Some effects measured in pixels, such as blur radius or sharpening, can look slightly different at another resolution, and changing timeline resolution after a project is graded is safest on a duplicate project or timeline. Before the final render, set the resolution back to your delivery size and review the heavy shots.

If you would rather leave the project untouched, use the Playback menu and set the timeline proxy resolution to half or quarter. That lowers processing resolution for playback only and has no effect on the render.

2. Rein in noise reduction

Temporal noise reduction is one of the most common causes of this error. It compares the current frame with neighbouring frames, so every extra frame you ask it to analyse adds another full-resolution frame to GPU memory.

• Reduce the number of frames in the temporal settings. Fewer frames often look almost the same on lightly noisy footage.
• Set motion estimation to the faster mode while you work.
• If you use both temporal and spatial noise reduction, check whether the shot actually needs both.
• Put noise reduction on its own node early in the tree, then cache that node (right-click the node and turn on its node cache, with the Render Cache set to Smart or User in the Playback menu), so Resolve renders it once instead of recomputing it on every pass.

Temporal and spatial noise reduction are part of DaVinci Resolve Studio, so if you are on the free version and still see the error, look at the other causes below.

3. Count your nodes

A long serial chain of simple corrections costs little. A handful of heavy tools stacked on one clip costs a lot. Common culprits are Magic Mask, Face Refinement, Super Scale, several tracked windows with large softness values, and third-party OpenFX plug-ins.

• Merge simple corrections that do the same job into one node.
• Cache the nodes that hold heavy effects, or bake them in with Render in Place from the clip's context menu. Resolve keeps a link to the original clip, so you can go back to it if you need to change the grade later.
• Check timeline-level nodes and adjustment clips. A grade applied to the whole timeline runs on every clip beneath it, which multiplies the cost.
• Set the Render Cache to Smart or User in the Playback menu so Resolve stores finished results on disk instead of recomputing them on every playback.

4. Use optimized or proxy media

Optimized media and proxies help most when the source is a heavy long-GOP or raw format at high resolution. Right-click clips in the Media Pool and generate optimized media or proxy media, then make sure the Playback menu is set to use them when available. In Master Settings you can choose the optimized media resolution and format, such as a ProRes or DNxHR flavour.

Be realistic about what this solves. Optimized media lowers decode cost, which helps playback. It does not reduce what a heavy noise reduction node or Fusion composition asks of the GPU at full timeline resolution. That is why timeline resolution and node choices come first.

Settings worth checking on a Mac

A few preferences and habits affect how much memory Resolve can actually use.

• GPU processing mode. In Preferences, under System and then Memory and GPU, Resolve on a Mac uses Metal. Leave GPU selection on automatic unless you have a reason to change it.
• Close other heavy apps. Browsers with many tabs, other video apps and 3D tools all compete for the same unified memory on Apple silicon.
• Fewer open timelines and Fusion compositions. Open Fusion compositions and extra timelines can hold memory. Close what you are not using.
• External displays. High-resolution external displays use GPU memory too. On a smaller machine, a large viewer on a 5K or 6K screen adds to the load.
• Update deliberately. Resolve and macOS updates often change GPU behaviour. Read the release notes on the DaVinci Resolve support page, update between projects rather than in the middle of one, and keep a backup of your project library first.

Restarting Resolve clears memory that has built up over a long session. If the error only appears late in the day and vanishes after a restart, that points to accumulated cache and open timelines rather than a single heavy clip.

How to stop it recurring

The error tends to come back on the same kinds of projects. A few habits prevent most of it.

• Set the working resolution at the start. Edit and grade at HD on a 4K or larger project if your Mac struggles, then switch to delivery resolution for review and render.
• Denoise once, early. Decide on noise reduction per camera or per scene, apply it on a cached node, and avoid adjusting it on every pass.
• Build node trees with intent. Use a consistent tree layout so you know where heavy tools live, and cache those nodes as a habit.
• Generate optimized media on ingest for heavy formats, before you start cutting.
• Know your machine's ceiling. On a lower-memory Mac, plan for fewer simultaneous heavy effects. On Apple silicon, memory cannot be upgraded later, so if you buy a new Mac for grading, unified memory is worth prioritising.

If the error persists on modest timelines with light grades, post the details (Resolve and macOS versions, Mac model, memory, codec and a failing node tree) to Blackmagic's forum or support.

FAQ

Does lowering timeline resolution reduce my final render quality?

Not if you set it back before rendering. Resolve is resolution independent, so your grade, sizing and windows scale with the change. Review shots with pixel-based effects such as blur or sharpening after switching back, since they can look slightly different.

Will more RAM fix GPU memory full on Apple silicon?

More unified memory gives the GPU more room, so a Mac with more memory hits the limit later. It does not remove the cost of heavy effects at high resolution, so the same habits still apply on a larger machine.

Is the free version of Resolve more likely to show this error?

Not inherently. The free version lacks some of the heaviest tools, such as temporal noise reduction, so it may trigger the error less often on the same footage. The causes and fixes are the same in both.

When the tool itself is the problem

Most GPU memory errors in Resolve are fixable with the steps above, and Resolve remains one of the strongest grading tools on a Mac. If the bigger issue is that Resolve feels heavy or hard to learn for the work you do, Is DaVinci Resolve too complicated? looks at why, and DaVinci Resolve alternatives for Mac editors compares the realistic options, including cinemaOS, with their limits stated plainly.