Thrum

What is UVCAssistant, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account and launchd job checked on macOS 26.3.1.

UVCAssistant is Apple's built-in camera extension for USB Video Class (UVC) cameras, the standard most USB webcams and many capture devices follow. It uses CPU while an app is receiving video from such a camera and is idle otherwise. Closing the apps that use the camera, or lowering their video resolution, brings it down.

UVCAssistant at a glance

UVCAssistant
Made byApple (part of macOS, CoreMediaIO)
TypeCamera extension (system extension)
Location/System/Library/Frameworks/CoreMediaIO.framework/Versions/A/Resources/UVCAssistant.systemextension/Contents/MacOS/UVCAssistant
Runs as_cmiodalassistants (a system account)
Started bylaunchd job com.apple.cmio.uvcassistantextension
Can you quit it?Not usefully. USB cameras stop working in every app until launchd starts it again.

What is UVCAssistant?

USB Video Class is the USB standard that lets webcams work without a vendor driver. On macOS 26, Apple's support for those cameras is UVCAssistant, a camera extension: the kind of system extension Apple introduced in macOS 12.3 for camera drivers that run outside the kernel. It is stored as UVCAssistant.systemextension inside CoreMediaIO.framework.

It runs as the _cmiodalassistants system account from the com.apple.cmio.uvcassistantextension launchd job, which the camera system starts when it is needed.

Is UVCAssistant safe?

Yes. UVCAssistant is part of macOS, signed by Apple, and lives on the read-only system volume. It runs as a dedicated system account rather than as root or as you.

Why does UVCAssistant use so much CPU?

How much CPU is normal for UVCAssistant?

Near 0% CPU when no app uses a USB camera. Steady CPU while video from a USB camera is shown is expected, rising with resolution and frame rate.

How do you stop UVCAssistant from using so much CPU?

  1. Close apps that use the camera. Quit video calls, recording tools and browser tabs that use the USB camera when you are not using it.
  2. Lower the resolution or frame rate. In your call or recording app, choose a lower video resolution or 30 frames per second instead of 60.
  3. Reconnect the camera. Unplug the USB camera and plug it in again, ideally directly into the Mac rather than through a hub.
  4. Review camera access. Open System Settings > Privacy & Security > Camera and turn off access for apps that should not use it.

When should you worry about UVCAssistant?

Look closer if UVCAssistant uses CPU with no app using a camera. Unplug USB cameras and capture devices one at a time; if it continues, restart the Mac.

It should run only from the CoreMediaIO framework path above, as _cmiodalassistants.

How do you check UVCAssistant in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type UVCAssistant in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every UVCAssistant process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'UVCAssistant' | grep -v grep

How can Thrum help with UVCAssistant?

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 UVCAssistant 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

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 about UVCAssistant

Do I need a driver for my USB webcam?

Most USB webcams follow the USB Video Class standard and work through UVCAssistant without a separate driver. Some cameras ship extra software for their own features.

Is UVCAssistant running even without a webcam?

It can be started by the camera system and then sit idle; its CPU use matters only while a camera is delivering video.

Sources