coreaudiod high CPU on Mac? Here's the usual cause
coreaudiod using high CPU on your Mac is Core Audio, and it's usually a symptom of another app monitoring the mic or a buggy audio driver. Here's how to find the real cause and reset it safely.
coreaudiod is the Core Audio daemon that manages all sound on your Mac and normally sits near zero CPU. When it spikes, it's almost always a symptom: another app or driver is hammering the audio system. Here's how to find the real culprit and reset it.
What coreaudiod does
It's the root audio process on macOS: it handles audio devices, formats and sample rates, the driver (HAL) layer, and routing for everything that plays or records sound: music, FaceTime, Zoom, Discord, and so on. A healthy coreaudiod is invisible.
Why it's using high CPU
The usual triggers:
- An app continuously monitoring the microphone: conferencing and remote-desktop apps are common offenders (Microsoft Remote Desktop, Zoom, Discord).
- A buggy or incompatible third-party audio driver or virtual device: audio-routing tools and sound-card drivers.
- A missing
~/Library/Preferences/Audiofolder on some old or migrated accounts. - A wedged Bluetooth or audio session.
Is coreaudiod a virus?
No. It's a core Apple daemon. High CPU means something is working the audio system hard, not that you're infected.
What to do about it
- Reset it:
sudo killall coreaudiod. It relaunches automatically, with about a one-second audio blip. This clears a transient wedge. - Find the app driving it. Because
coreaudiodis usually the symptom, the reset is temporary if an app keeps monitoring the mic. Quit or update the likely app (conferencing/remote-desktop tools first), or revoke its microphone access in System Settings → Privacy & Security → Microphone. - Remove third-party audio drivers you don't need, or update them.
- For the missing-folder bug on older accounts, recreating
~/Library/Preferences/Audiowith the correct ownership and rebooting has resolved it, an advanced step worth researching for your exact case. - Keep macOS updated.
The key insight
coreaudiod is rarely the real problem; it's reacting to another app or driver. A killall buys quiet, but the spike comes back until you deal with whatever is holding the audio system open.
See the process, not just the symptom
When a system daemon spikes because of another app, the trick is connecting the two. Plumby shows live CPU in the menu bar with each process named in plain language and the fix beside it, so "coreaudiod is high because a conferencing app is holding your mic" becomes something you can actually see and act on. Every number is measured, never estimated. If it's noise and heat you're chasing, pair this with why your Mac's fans are loud.
