← All processes

macOS process library

What is coreaudiod on Mac?

coreaudiod is the macOS daemon behind Core Audio. Every app that plays or records sound, from Music to Zoom to your browser, goes through it to reach your speakers, headphones, and microphones.

Part of
macOS’s Core Audio daemon, part of the system’s audio stack.
Safe?
Yes. It is part of macOS and runs on every Mac.
Can I quit it?
Only to reset audio: macOS restarts it within seconds, and sound cuts out briefly while it does.

The short answer

coreaudiod using some CPU while audio is playing or a call is running is normal. Sustained high use with nothing playing usually points to an app holding the audio device open, or a third-party audio driver misbehaving. Resetting coreaudiod is a common fix and is safe.

Normal use

What coreaudiod usually looks like.

With no sound playing, coreaudiod usually sits near 0% CPU. During music, video, or a call, a few percent is common, and more with many audio devices or effects.

Third-party audio drivers, such as virtual audio devices from call, recording, or noise-cancelling apps, load into Core Audio. On recent macOS versions they can appear as separate “Core Audio Driver” processes next to coreaudiod.

Why coreaudiod uses so much CPU or memory

How to calm coreaudiod down

Start at the top. Each step is more disruptive than the one before.

  1. Find the app using audio

    Check which apps are on a call, recording, or playing media. Quitting the one that shouldn’t be often brings coreaudiod back down.

  2. Disconnect devices you aren’t using

    Unplug unused audio interfaces and disconnect Bluetooth headphones you’re not wearing.

  3. Update or remove audio drivers

    Update apps that install virtual audio devices. If you no longer use one, uninstall it with the app’s own uninstaller.

  4. Reset Core Audio

    In Terminal, run sudo killall coreaudiod. macOS restarts it immediately. Sound cuts out for a moment, and apps playing audio may need to restart playback.

  5. Restart your Mac

    If audio is still stuck, restart. Save your work first.

Seeing it in Spare

Find what it’s reacting to.

coreaudiod works for whatever app is making sound, so its number alone doesn’t tell you much. Spare groups each app with its helper processes, so you can see whether a call app, a browser, or a recording tool was active when coreaudiod climbed.

Spare treats macOS processes like coreaudiod as system tasks and never offers to stop them. Spare doesn’t monitor audio devices or sound itself.

SpareMemory pressure · Normal
♪
coreaudiodmacOS · Audio
12% CPU52 MB
◉
ZoomApp · 6 processes
28% CPU760 MB
◎
Google ChromeApp · 22 processes
14% CPU2.9 GB
Illustration with example readings

Common questions

About coreaudiod

Is coreaudiod a virus?

No. It is part of macOS at /usr/sbin/coreaudiod and handles all audio on your Mac.

Is it safe to run sudo killall coreaudiod?

Yes. macOS restarts coreaudiod right away. You lose sound for a moment, and some apps may need to restart playback.

Why is coreaudiod using CPU when nothing is playing?

An app may be holding the audio device open, or a third-party audio driver may be busy. Quit audio apps one at a time to find it.

Why do I have no sound on my Mac?

Check the output device in System Settings → Sound first. If the right device is selected and there’s still no sound, resetting coreaudiod often helps.

Related processes

Sources: Apple: Core Audio Overview, coreaudiod man page, macOS. Reviewed October 6, 2026.

Get Spare

Free to use. Yours to explore.

Download Spare for Apple silicon, or explore the MIT-licensed source on GitHub. Free to use, with no subscription or account.

macOS 14+ · Apple silicon · Signed and notarized