Thrum

Why is Blender using so much CPU and memory on my Mac?

Last reviewed: 19 November 2026.

Rendering with Cycles uses every CPU core unless Blender is set to render on the GPU; on Apple silicon Macs, choosing Metal in Preferences > System > Cycles Render Devices moves that work to the GPU. Memory goes to the scene itself, textures, undo history and the Video Sequencer cache, each of which has a limit in Preferences > System. Blender's manual states that GPU-accelerated ray tracing and denoising are available on Apple silicon with Metal.

Why does Blender use 100% CPU when rendering?

When Cycles Render Devices is set to None, or None is the only option, Cycles renders on the CPU and uses all available cores until the frame is finished. That is expected and is why the Mac's fans spin up during renders.

Blender's manual states that Metal GPU acceleration is supported on Apple silicon Macs, with macOS 13 or later required for all features, and that GPU-accelerated ray tracing and denoising are available there. If the GPU runs out of memory, Blender automatically uses system memory, which is slower but usually still faster than rendering on the CPU.

How do you set Blender to render on the GPU?

  1. Choose Metal. Open Edit > Preferences, click System, and under Cycles Render Devices choose Metal.
  2. Enable the device. Tick the GPU listed under Metal.
  3. Set the scene to GPU Compute. In the Render properties of each scene that uses Cycles, set Device to GPU Compute.
  4. Render and compare. Render a test frame and watch Activity Monitor: CPU use should drop while GPU use rises.

What uses Blender's memory, and what limits it?

Setting in Preferences > SystemWhat it controls
Undo StepsHow many undo steps Blender keeps.
Undo Memory LimitMaximum memory for undo, in MB (0 is unlimited).
Global UndoSaves actions outside Edit Mode. Turning it off saves memory but stops the Adjust Last Operation panel from working, so Blender recommends keeping it on.
Texture Time OutSeconds after which an unused GPU texture is freed (0 keeps textures allocated).
Memory Cache LimitUpper limit of the Video Sequencer and Movie Clip Editor cache, in MB.

High-resolution textures, subdivision modifiers and simulation caches add to the scene's own memory. Lowering viewport subdivision levels while modeling keeps the scene lighter.

When is Blender's resource use a problem?

Full CPU or GPU use during a render, bake or simulation is normal. Blender becoming unresponsive during GPU rendering can happen when the same GPU drives the display; Blender's manual discusses this. Memory pressure turning red during a render means the scene needs more memory than the Mac has: reduce texture sizes, lower the Undo Memory Limit, or render on the GPU with system memory fallback.

How can Thrum help with Blender?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Blender is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Blender in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions

Does Blender use the GPU on Apple silicon?

Yes. Choose Metal in Preferences > System > Cycles Render Devices and set the scene's Device to GPU Compute.

Why does Blender keep using memory after I delete objects?

Undo history keeps earlier states of the scene. Undo Steps and Undo Memory Limit in Preferences > System cap how much it keeps.

Sources