Thrum

Why is OBS Studio using so much CPU on my Mac?

Last reviewed: 19 November 2026.

OBS Studio composites every scene and then encodes the result in real time, and encoding with the x264 software encoder runs entirely on the CPU. On a Mac, switching to Apple's VideoToolbox hardware encoder (Apple VT) moves encoding to dedicated hardware, and lowering the output resolution or frame rate reduces both rendering and encoding work. OBS's "encoding overloaded" message means the encoder cannot keep up.

What uses the CPU in OBS Studio?

How do you lower OBS Studio's CPU use on a Mac?

  1. Use the Apple VT hardware encoder. Open Settings, then Output. Set Output Mode to Advanced, and on the Recording (or Streaming) tab set the Encoder to Apple VT H264 Hardware Encoder. OBS describes hardware encoders as taking the workload off the CPU.
  2. Lower the output resolution. In Settings > Video, choose a smaller Output (Scaled) Resolution. OBS's guidance is that reducing output resolution reduces the load on the encoder.
  3. Drop to 30 fps if 60 does not hold. Set Common FPS Values in Settings > Video to 30. Frame rate affects both rendering and encoding load.
  4. Close GPU-heavy apps. OBS suggests checking Activity Monitor for other programs using a lot of GPU, since games or video apps compete with OBS for rendering time.
  5. Remove unused sources and filters. Hidden sources in a scene can still be captured; delete sources and filters you no longer use.

Which encoders are available on Apple silicon and Intel Macs?

According to OBS, Apple VideoToolbox hardware encoding is supported on both Apple silicon and Intel Macs. On Apple silicon, recording supports H.264, HEVC and Apple ProRes. On Intel Macs, VideoToolbox recording is limited to H.264 and streaming is not supported, so streaming from an Intel Mac uses the x264 software encoder and therefore the CPU.

For recording, OBS suggests a bitrate of about 8000 Kb/s for 1080p at 30 fps and 16000 Kb/s for 1080p at 60 fps with the Apple VT encoder.

When is OBS's CPU use a sign of a problem?

High CPU with x264 is the expected cost of software encoding. Look into it when OBS shows encoding overloaded messages, when recordings stutter, or when CPU stays high with a hardware encoder selected. Those point to too high a resolution or frame rate for the Mac, a heavy filter, or another app using the GPU at the same time.

How can Thrum help with OBS Studio?

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 OBS Studio 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 OBS Studio 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

What does encoding overloaded mean in OBS?

The encoder cannot compress frames as fast as OBS produces them, so output becomes choppy. OBS recommends freeing up resources: lower resolution or frame rate, or use a hardware encoder.

Can I stream with the hardware encoder on an Intel Mac?

OBS's documentation says VideoToolbox streaming is not supported on Intel Macs; use x264 for streaming there.

Sources