3 answers

★ Best answer

I've fought this exact problem while working on some footage at home, and it's usually not just about RAM or proxies - what really matters is whether you're working with variable frame rate files or heavily compressed codecs like H.264, which Resolve has to decompress constantly and absolutely murders your system.

Before you assume you need proxy files, try converting your phone footage to ProRes or DNxHD first, or at minimum check your codec in the media pool; that single change fixed it for me when 16GB felt like nothing.

4K editing on Resolve is pretty resource-hungry, and 16GB of RAM can struggle depending on your codec and timeline settings.

The most common culprit is that you're editing the full resolution files directly without creating optimized media first - Resolve works way better when you generate proxy files at a lower resolution for editing, then switches back to full quality for export. Also check your GPU cache settings and make sure your scratch disk has enough free space, since Resolve needs room to write temporary files.

Try starting a new project with proxies enabled from the get-go and see if the crashes stop.

Your first move should be generating proxy files before you even start editing. This cuts down what Resolve actually has to process in real time. The other answer nailed the codec issue, but it's not just about editing full res - it's that you're probably mixing codecs or working with footage that's heavily compressed (like phone video), which tanks performance even worse than standard 4K.

16GB of RAM isn't really enough headroom for smooth 4K work, especially with effects or color grading layered in. You're hitting a ceiling pretty fast. Beyond proxies, check your timeline resolution settings - you don't need to work at full 4K if you're just cutting and basic color. Set your timeline to half resolution or quarter resolution while editing, then switch back to full for export. Also make sure your GPU is actually being used. Go into preferences and confirm your graphics card is enabled for CUDA or OpenGL depending on what you've got. Some setups default to CPU processing, which'll choke immediately on 4K.

The freezing after a few minutes suggests your system's running out of usable memory and Resolve's cache is getting bottlenecked. Try lowering your playback quality to 1/4 resolution while you're cutting, and disable any heavy effects until you're ready to do final work. Save frequently too - Resolve can get unstable when it's struggling, and losing work sucks.

Your answer

Log into answer.