Thrum

What is coreaudiod, and why is it using so much CPU?

Last reviewed: 19 November 2026. Path, account, launchd job, man page and audio driver helper processes checked on macOS 26.3.1.

coreaudiod is the macOS Core Audio daemon that manages audio hardware, so every sound an app plays or records passes through it. It uses some CPU whenever any app has audio running, and more with many apps, virtual audio devices or audio drivers involved. It should drop near 0% when nothing is playing or recording.

coreaudiod at a glance

coreaudiod
Made byApple (part of macOS, Core Audio)
TypeSystem daemon
Location/usr/sbin/coreaudiod
Runs as_coreaudiod (a system account)
Started bylaunchd job com.apple.audio.coreaudiod
Can you quit it?Not from Activity Monitor without an administrator password, and all sound stops while it restarts. Restarting the Mac is the clean way.

What is coreaudiod?

Its man page describes coreaudiod as the daemon used for Core Audio, Apple's system for audio hardware. It owns the Mac's audio devices (built-in speakers and microphones, headphones, USB and Bluetooth audio, and AirPlay), mixes the sound from every app, and sends it to the output you choose in System Settings > Sound.

It runs as the _coreaudiod system account from the com.apple.audio.coreaudiod job. Third-party audio drivers, such as virtual devices installed by recording, meeting and routing apps, are Audio Server plug-ins installed in /Library/Audio/Plug-Ins/HAL; on this Mac each runs in its own helper process named Core Audio Driver (name.driver) under the same account.

Is coreaudiod safe?

Yes. coreaudiod is part of macOS, signed by Apple, and stored in /usr/sbin on the read-only system volume. It runs as its own system account rather than as root or as you.

Why does coreaudiod use so much CPU?

How much CPU is normal for coreaudiod?

Near 0% CPU with no audio playing or recording. A few percent while music or a call is running is typical; more with several streams, high sample rates or audio drivers involved.

How do you stop coreaudiod from using so much CPU?

  1. Close apps that hold audio open. Quit or close browser tabs, players and meeting apps you are not using. A paused video or an idle call can still keep a stream open.
  2. Check the output and input device. Open System Settings > Sound and check Output and Input. Choose the built-in or the device you actually use rather than a virtual or aggregate device.
  3. Remove audio drivers you no longer use. Look in /Library/Audio/Plug-Ins/HAL for drivers from apps you have removed, and uninstall them with the vendor's uninstaller. A Core Audio Driver process in Activity Monitor shows which driver is loaded.
  4. Restart the Mac. If coreaudiod stays high with nothing playing, or sound stops working, restart the Mac to start Core Audio fresh.

When should you worry about coreaudiod?

Look closer if coreaudiod stays above about 10% CPU with no app playing or recording, or if sound crackles or drops. A third-party audio driver or virtual device is the usual cause; removing it, then restarting, is the test.

It should run only from /usr/sbin/coreaudiod as _coreaudiod.

How do you check coreaudiod in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type coreaudiod 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 coreaudiod process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

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

How can Thrum help with coreaudiod?

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 coreaudiod 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 coreaudiod

Why does coreaudiod use CPU when nothing is playing?

An app may still have an audio stream open, such as a paused video tab or a call app with the microphone on. Closing it lets coreaudiod go idle.

What are the Core Audio Driver processes?

They are third-party audio drivers from /Library/Audio/Plug-Ins/HAL, each running in its own helper under the _coreaudiod account.

Is it safe to restart coreaudiod?

Restarting the Mac is the safe way. Sound stops in every app while Core Audio restarts.

Sources