How to Fix Laggy Playback in DaVinci Resolve

About this video

Tim explains why Resolve playback is choppy and works through fixes, starting with the most effective: proxy media. In Project Settings under Master Settings he sets Proxy Media Format to ProRes 422 Proxy — an intra-frame codec where every frame is encoded individually, giving faster editing at reasonably lower file sizes — and Proxy Media Resolution to half or quarter, choosing half, then generates proxies for all highlighted clips and sets proxy handling to Prefer Proxies; exports still use the original source files automatically. For effects-driven lag he covers lowering Timeline Playback Resolution, which reduces preview processing for effects; Render Cache, with Smart mode auto-detecting heavy effects or User mode for manual selection, plus managing cache files that fill a drive; caching, bouncing, or exporting audio clips in Fairlight when voice isolation, dialogue separator, AI tools, or plugins slow playback; and Render in Place to bake a clip into a new file, choosing a format with an alpha channel such as Apple Pro 4444 when the clip has transparency. For Fusion, adding a Saver node before an effect such as Magic Mask, rendering via Render All Savers, and reloading the resulting EXR sequence through a Loader node produces a pre-rendered comp. On Windows he advises using content-creation GPU drivers — NVIDIA’s Studio driver, while AMD’s Pro Edition is described as now limited to Radeon Pro workstation cards — and checking RAM speed in Task Manager: his DDR4 should run at 3200MHz but showed the default 2133 (DDR5’s default is given as 4800), fixed by enabling an XMP, DOCP, or Expo profile in the BIOS, reached by pressing Delete on restart. Inside Resolve’s Preferences > Memory and GPU, he unchecks the Auto boxes to allocate resources manually, sets NVIDIA to CUDA (Metal on Mac, otherwise OpenCL), enables hardware decode, and sets Playback Performance Mode to Manual so optimizations are not turned off automatically. Finally, he recommends working from an SSD rather than a hard disk drive, and keeping all project media on one drive — sorting the Media page by file path revealed stray files on his G drive instead of D, which he fixed by relinking them.

Key takeaways

• Generate ProRes 422 Proxy media at half or quarter resolution and set Prefer Proxies — editing speeds up while exports automatically use the original files.
• Tackle effects lag in layers: lower Timeline Playback Resolution, use Render Cache in Smart or User mode, cache or bounce heavy Fairlight audio, and Render in Place (with an alpha-capable format if needed).
• Pre-render Fusion work with a Saver node, then load the rendered EXR sequence back through a Loader node so effects like Magic Mask do not need retracking.
• Check the system: install NVIDIA Studio (creation) drivers on Windows and enable XMP/DOCP/Expo in the BIOS if RAM runs at default speed — his DDR4 showed 2133 instead of 3200MHz.
• In Resolve Preferences, allocate RAM/GPU manually, pick CUDA on NVIDIA or Metal on Mac, set Performance Mode to Manual, work from an SSD, and relink any media scattered across slower drives.

Episode details: published October 24, 2025 · 11:13 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are Kevin Stratvert’s own claims, shared for education — they are not typical or guaranteed.

← Previous: NEW: Copilot Mode in Microsoft Edge (Top 5 AI Features Explained) · Next: Automate Slide Creation with the Gamma API (Spreadsheet → Presentation) →

All Kevin Stratvert videos · Kevin Stratvert profile · Kevin Stratvert on YouTube