You launch DaVinci Resolve, click over from the Cut page to Edit, and the entire app locks up for 15 to 30 seconds. No progress bar, no beach ball that makes sense — just a frozen window that makes you wonder if you need to force-quit and start over. Then it never happens again for the rest of the session.
That single, reproducible freeze on the first tab switch has editors and mixers across forums asking the same handful of questions. Here are the answers that actually get you back to work.
What's actually causing the freeze?
The freeze lines up almost exactly with how Resolve compiles and caches GPU shaders the first time a page renders. Each page in Resolve — Cut, Edit, Fusion, Color, Fairlight, Deliver — uses its own set of UI shaders and rendering pipelines. On first launch, none of those shaders are compiled or cached yet, so the moment you switch to a new tab, Resolve has to build that shader set from scratch on your GPU before it can paint the interface.
This explains why the freeze is so consistent: it happens once, on the first switch, and never again in that session. Once Resolve compiles the shaders and stores them in cache, every subsequent tab switch uses the cached version and the delay disappears.
It also explains why the freeze length varies by machine. A newer discrete GPU with fast VRAM compiles shaders quickly. An older integrated GPU, or a laptop running on battery-saver mode, takes noticeably longer — which is where you get the reported 15 to 30 second stalls.
Is this a corrupted project or a bad install?
No, and this is the misconception that sends people down the wrong troubleshooting path first. Reinstalling Resolve, rebuilding the project database, or starting a fresh project file won't fix this, because your GPU driver state and shader cache cause the freeze — not your project or your install. If you've already tried a clean reinstall and still hit the same freeze on tab one, that actually confirms the shader-compilation theory rather than pointing to corruption.
The tell is in the pattern. A corrupted project usually produces crashes, missing media links, or inconsistent behavior across sessions. This freeze is boringly predictable: same trigger, same one-time occurrence, same recovery. Treat it as a rendering pipeline warm-up cost, not a data integrity problem.
How do I fix it right now, today?
The fastest workaround is to force the shader compilation to happen before you need to work, rather than in the middle of your session. After launching Resolve and before you touch your real project, open a blank test project and manually click through every page tab once — Cut, Edit, Fusion, Color, Fairlight, and Deliver — then close that test project. See read about how to produce psychedelic trip music: a producer's guide for additional background.
This pre-warms the shader cache for all pages in one shot. You absorb the freeze on throwaway content instead of on your actual timeline.
A second option works almost as well: open your real project directly on the page you plan to use most, skip the Cut page entirely if you don't need it, and expect the first switch to whichever page you land on to carry the delay. Either approach moves the pain to a moment you control instead of one that ambushes you mid-edit.
Does my GPU driver or settings matter here?
Yes, significantly. Outdated GPU drivers compile shaders more slowly and occasionally hit compatibility snags that stretch a 5-second delay into a 30-second one. Update to the current driver from your GPU vendor before doing anything else — this single step resolves the worst-case freeze durations for many affected users.
Beyond driver version, check your GPU processing mode inside Resolve's preferences under the Memory and GPU tab. If you're on a laptop, make sure Resolve uses the discrete GPU rather than the integrated one, and confirm your OS power settings aren't throttling GPU performance to save battery during that first launch. On Windows, verify that hardware-accelerated GPU scheduling is enabled in your display settings, since this affects how quickly the OS hands shader compilation tasks to the GPU.
Does panel or project load order change anything?
It does, and this is one of the more useful things editors have quietly figured out. If you disable or close secondary panels — the audio meters, the edit index, a floating scopes window — before your first tab switch, the freeze tends to run shorter, because Resolve has fewer UI elements competing for that same first-paint shader compilation. Reopen those panels after the freeze clears on your warm-up project, and they'll load instantly since the shaders are already cached.
The same logic applies to project load order on multi-project workflows. Open your smallest, simplest test project first, cycle through the tabs to trigger and clear the freeze, then open your actual full-resolution session. You've effectively made the expensive one-time cost happen on a project where a 20-second wait costs you nothing.
Does this affect Fairlight and audio work specifically, or mainly video editing?
It affects every page, including Fairlight, but audio-focused users notice it differently. If your workflow starts on Fairlight for a mixing pass, you'll hit the freeze switching into that page instead of Edit or Color. The underlying cause is identical: Fairlight's mixer console, EQ curve displays, and meter bridges all rely on GPU-accelerated rendering that needs the same first-time shader compilation. For more on this, see full coverage of how to produce psychedelic-sounding music: a guide.
For audio engineers who jump straight into Fairlight after launch and skip Cut and Edit entirely, the pre-warm trick still applies. Click through Fairlight specifically as part of your test-project warm-up, since that's the page carrying your actual freeze risk — and skip warming pages you never touch in a given session.
When will Blackmagic actually patch this?
Blackmagic Design hasn't published a fixed release date for this specific first-tab freeze as of now. The company typically bundles rendering pipeline fixes into point releases rather than rushing an out-of-cycle patch for a one-time, non-crashing delay.
Also read: related topic: the audio engineering behind trip-friendly music
Given how Resolve's update cadence has run historically, a fix addressing shader pre-caching at launch is plausible in an upcoming point release, but nothing has been confirmed publicly.
Until that lands, the workaround above costs you one warm-up cycle per session, typically under a minute, in exchange for never being surprised by a 20-second freeze mid-session. That trade is worth making now rather than waiting on a patch timeline nobody can confirm.
Isn't this just a sign my machine is underpowered?
This is the misconception worth clearing up last, because it drives people toward hardware upgrades they don't need. The freeze happens on high-end workstations with top-tier discrete GPUs just as reliably as it happens on modest laptops — the only difference is duration, not occurrence. A powerful GPU compiles the shaders faster, so the freeze might last 5 seconds instead of 30, but it doesn't disappear just because your hardware is strong.
If you're tempted to blame your GPU or consider an upgrade purely because of this freeze, hold off. Confirm first that the pre-warm workaround eliminates your disruption, because for almost everyone it does. A hardware purchase aimed solely at fixing a one-time software rendering quirk is money spent on the wrong problem.
