coreaudiod, the daemon that runs every sound your Mac makes
The busiest daemon measured on a quiet Mac: coreaudiod runs every sound in and out of your Mac, from speaker power to the microphone permission prompt.
By Chethan Kumar S N · Updated
Every sound your Mac has made since it booted went through one process. The startup chime on an Intel machine, the alert ping, the voice on the other end of a call, the fan noise a friend’s kid insists is a robot: all of it, in and out, is coreaudiod.
This series has been measuring the lowercase daemons in Activity Monitor one at a time, and coreaudiod breaks the pattern the others set. trustd, the certificate checker, spends about thirteen minutes of processor time a day. bluetoothd, running a continuous radio scan, about ten. coreaudiod, on a Mac where nobody was listening to anything and nothing was recording, had spent twenty nine hours of processor time in twenty six days. It is the busiest daemon measured so far, by four times, and its entire official documentation is two sentences written in 2004.
What the manual actually says
Here is the whole description, verbatim:
coreaudiod is a daemon used for Core Audio related purposes.
The file is /usr/share/man/man8/coreaudiod.8, 673 bytes, dated July 19 2004. A second sentence adds that it “was introduced with OSX version 10.4”. That is the complete state of Apple’s written description of this daemon, twenty two years and something like twenty major macOS versions later. There are shell scripts on this machine with longer manuals.
The vagueness is almost honest. The reason a one line description survives is that the daemon’s job is not describable in a line without the word “everything”. It is the sound server, the device negotiator, the format converter factory, the power manager for your speakers, and the enforcement point for the microphone permission prompt. “Core Audio related purposes” is doing more work than it looks like.
You can read it yourself:
man coreaudiod
ls -l /usr/share/man/man8/coreaudiod.8
The measurements
Everything below was measured read only, on one Mac: macOS 27.0.1, an M1 Pro with ten cores, twenty six days and ten hours past its last boot.
ps -Awwo pid,ppid,user,rss,time,etime,args | grep [c]oreaudiod
659 1 _coreaudiod 19904 1752:48.69 26-10:10:33 /usr/sbin/coreaudiod
Read it the way this series has learned to. Process 659, parent 1, so launchd started it at boot. The user is not root and not you. It is a reserved account, _coreaudiod, uid 202, with the real name “Core Audio Daemon” in the local directory, a home of /var/empty and a shell of /usr/bin/false. You cannot log in as it. Nothing can. It exists so the sound system can own files and hold capabilities without being root, the same pattern as _locationd and _trustd covered earlier in this series.
The processor number is the headline. 1,752 minutes and 48 seconds across 26.4 days is about 66 minutes a day, or 4.6 per cent of a single core, continuously averaged. For a daemon whose user was doing nothing audio related at the time, that is a striking amount of work, and the log section below shows exactly where it goes.
Memory sits between 20 and 33 MB. Two samples taken minutes apart read 19,904 KB and then 33,600 KB, because the audio engine allocates buffers when a stream starts and lets them go when it stops. launchd has given the job EnablePressuredExit, so under real memory pressure the system can reclaim it and bring it back. A different number in Activity Monitor, the virtual memory figure near 488 GB, is an address space reservation, not a cost. It looks alarming and means nothing.
The binary itself is small for what it does: /usr/sbin/coreaudiod is 791,168 bytes, in three slices, x86_64, arm64e and arm64e.x1. Unlike sandboxd and sharingd from earlier in this series, Apple still ships an Intel slice. The code signature reports Identifier=com.apple.audio.coreaudiod and Platform identifier=26, the platform flag reserved for the operating system’s own files. And its string table runs to just 324 entries, barely more than the six string daemon cfprefsd and a rounding error next to sharingd’s 26,560.
The identity commands, verbatim
ps -Awwo pid,ppid,user,rss,time,etime,args | grep [c]oreaudiod
ls -l /usr/sbin/coreaudiod
lipo -archs /usr/sbin/coreaudiod
codesign -dv /usr/sbin/coreaudiod
strings -a /usr/sbin/coreaudiod | wc -l
dscl . -read /Users/_coreaudiod
A small dispatcher in front of an enormous stack
Three hundred and twenty four strings is the tell. This daemon is not the audio engine. It is the dispatcher in front of one.
The engine is distributed across the system. The kernel extensions directory carries 47 audio related kexts, with names like IOAudio2Family.kext, AppleIPCAudioController.kext, AOPAudioDriver.kext and ExclavesAudioKext.kext, the pieces that move samples to and from the silicon. The private frameworks directory holds more than twenty frameworks whose names start with Audio, from AudioDSPGraph to AudioSession to CoreAudioOrchestration, the code that mixes, converts and routes. coreaudiod sits in front of all of it, decides who talks to what, and holds the door.
That is why the 2004 manual says “purposes” and nothing else. The purpose is genuinely distributed. When you change the output device in System Settings, the click travels from the Settings app to coreaudiod, which tells the HAL to re build the device graph, which wakes the right driver, kernel side. No single file contains the job, so no single man page describes it.
Three processes in the reserved account
Look for everything running as _coreaudiod and you find the daemon plus two roommates:
ps -axo pid,user,time,rss,args | grep [_]coreaudiod
659 _coreaudiod 1752:48.69 19904 /usr/sbin/coreaudiod
661 _coreaudiod 1:13.87 864 /usr/sbin/distnoted agent
664 _coreaudiod 1:23.42 4336 Core Audio Driver (MSTeamsAudioDevice.driver)
The distnoted copy is the per session agent pattern from the distnoted page: every account with a background session gets one, including reserved accounts, and this one serves the audio daemon’s session.
The third process is the interesting one. MSTeamsAudioDevice.driver is Microsoft’s Teams virtual audio device, installed in /Library/Audio/Plug-Ins/HAL/, and it runs as its own process under the reserved account. This is the architecture for third party audio drivers: anything that adds a virtual device to the system gets hosted out of process, next to the daemon rather than inside it. A crashing driver cannot take the sound server down with it, and a crashing server does not take third party drivers with it. On this Mac the folder holds two drivers, the Teams one and a ParrotAudioPlugin.driver, and the device list shows the result: alongside the built in speakers and microphone, system_profiler reports a “Microsoft Teams Audio” device, manufacturer Microsoft Corp., transport Virtual, alongside an iPhone that happened to be on the desk, listed as a 48 kHz microphone input.
So if you ever see a process named “Core Audio Driver (something.driver)” and do not remember installing it, the something is the app that installed it. Teams, Zoom, BlackHole, virtual cassette decks for audio routing: they all live there.
The reserved account idea repeats one level up. The daemon that decides where audio goes in the first place, audiomxd, runs under its own account named _audiomxd, the referee for which nearby Apple device your AirPods belong to. One account for the hardware, one for the decision, and neither of them you.
Six doors
The launch job is /System/Library/LaunchDaemons/com.apple.audio.coreaudiod.plist, and like sharingd’s it is mostly a cast list. Six Mach services:
| Mach service | What it is |
|---|---|
| com.apple.audio.audiohald | The HAL itself, the API every audio app talks to |
| com.apple.audio.coreaudiod | The daemon’s own control channel |
| com.apple.audio.driver-registrar | Where drivers check in, and both HAL plugins on this Mac did |
| com.apple.BTAudioHALPluginAccessories | The Bluetooth audio bridge, the door bluetoothd knocks on for headsets |
| com.apple.coremedia.systemcontroller.xpc | System media policy, volume limits and route changes |
| com.apple.virtualaudio.cider | Virtual audio devices; registered but idle on this Mac |
The bluetoothd door deserves the click of a link. When Bluetooth headphones connect, the radio daemon negotiates the link and then hands the audio across through this service, which is why a headset pairing wakes both daemons at once, and why a headset that keeps dropping can leave both of them with elevated numbers in Activity Monitor.
launchctl’s view of the job is as quiet as the series gets:
launchctl print system/com.apple.audio.coreaudiod
state = running
runs = 1
last exit code = (never exited)
minimum runtime = 10
exit timeout = 5
One run, no exits, since boot, started over a Mach message like nearly everything else in this series. The environment block carries three settings worth knowing exist: OSLogRateLimit of 64, so a chatty audio device cannot flood the unified log, and two allocator settings, MallocNanoZone and MallocSpaceEfficient, which trade a little speed for a smaller footprint. A daemon that allocates in bursts wants exactly that.
What it actually does all day
A quiet half hour of coreaudiod’s log, on a Mac where nothing was being played or recorded by anybody, runs to 327 lines. The single biggest story in them is the speakers being switched on and off.
Six times in thirty minutes, the log walks the output device through the same five states and back: inactive, idle, prepare, power, running, then down again. Each step is logged with the time it took, to the nanosecond:
Speaker: Order: 1000, State change 'iact' to 'idle' (transition 'utid'): took 307125ns
Speaker: Order: 1000, State change 'idle' to 'ppar' (transition 'uppr'): took 5500ns
Speaker: Order: 1000, State change 'ppar' to 'pwrm' (transition 'upwm'): took 2941458ns
Speaker: Order: 1000, State change 'pwrm' to 'runn' (transition 'urun'): took 16375ns
Two hundred and ninety four microseconds to bring the speaker amplifier up, every time. Six full cycles in a quiet half hour is roughly two hundred and eighty a day, and that is the honest answer to where sixty six minutes of daily processor time goes: powering the speakers up, moving the samples, powering them back down. Every notification chime is a full cycle. Every alert sound an app insists on playing is a full cycle. The Mac was not playing music. It was being pinged.
Each cycle also builds converters. The log records them being created, with the formats spelled out:
Created a new in process converter, from 6 ch, 48000 Hz, Float32, interleaved
to 6 ch, 48000 Hz, Float32, interleaved
Created a new in process converter, from 12 ch, 48000 Hz, Int16, interleaved
to 12 ch, 48000 Hz, Float32, interleaved
Six and twelve channel buffers, at 48 kHz, because the internal graph carries more channels than the speakers have, for mixing and routing headroom. The input side of the same window shows the engine starting and stopping: HALS_IOEngine2::_StartIO(96) succeeded ... new state: Prewarm: 0 Play: 1 State: Running.
Around the edges of the same log sit the daemon’s other jobs. Ten times in the half hour it called TCCAccessRequest, the privacy permission check, against the system privacy daemon, because anything touching an input device has to prove it may. There are lines from AXHearingHalPlugin, the accessibility layer’s hearing device support, reporting itself hidden on a Mac with no hearing devices paired. And there is exactly one error level line, HALS_PlugIn::HostInterface_PropertiesChanged: the object is not valid, the sound of a plugin object disappearing mid callback. Half an hour, three hundred lines, one complaint. That is a healthy daemon.
The privacy boundary, in its own words
The CoreAudio framework ships its user facing English vocabulary in one localisation file. It contains exactly three strings, and together they are the microphone and system audio permission prompt:
"%@" would like to access, modify and record your system audio.
OK
Don't Allow
That is the whole interface between the sound system and your consent. The prompt you see when an app asks to record system audio is one of those formats filled in, and the daemon is the machinery underneath it, checking with the privacy daemon on the cadence the log shows.
One more file is worth quoting because it is funny in a dry way. The framework’s VoiceIsolationSettings.plist carries a client deny list for the voice isolation feature, three entries: FaceTime, the Sound settings extension, and com.apple.audio.coreaudiod. The daemon denies itself a feature, almost certainly so its own audio path can never recursively ask for processing. Even in a settings file, the sound server is careful about who gets to touch the audio.
Apple never says its name
The pattern that closes every page in this series holds here too. Across Apple’s macOS audio documentation, the sound settings help, the AirPlay guides, the Background Sounds page that explains you can play ambient sound “to help you focus or rest” from Accessibility settings: zero mentions of coreaudiod. Apple documents the features and leaves the machinery unnamed, which is how a daemon can run an hour of processor time a day on every Mac sold and keep a two sentence manual from 2004.
If your sound works, this daemon is why, and it needs nothing from you. If your sound is broken, the order of operations is: check the output device in Sound settings, toggle Bluetooth if a headset is involved, close the app holding the stream, and only then restart the daemon. It will come back in seconds. It always has.
Related guides
- What Is distnoted on Mac?, the notification daemon that runs an agent inside this account
- What Is bluetoothd on Mac?, the radio daemon on the other side of the headset bridge
- Why is my Mac battery draining so fast?, where this daemon’s daily work belongs on the list
- Why is my Mac running slow?, for reading a busy daemon the honest way
Questions
What is coreaudiod on Mac?
It is the daemon at the centre of Core Audio, the layer every app's sound goes through. When anything plays a sound, records the microphone, changes the volume, pairs a Bluetooth headset or opens a virtual audio device, coreaudiod is the process doing the work, and the apps talk to it through the HAL, the hardware abstraction layer it serves. It is not a small utility. On the Mac measured here it had spent twenty nine hours of processor time across twenty six days of uptime, about sixty six minutes a day, which makes it the busiest daemon measured in this series, ahead of the certificate checker trustd and the Bluetooth stack. Its manual, unchanged since July 2004, describes the whole job as Core Audio related purposes.
Why is coreaudiod not showing in Activity Monitor?
Because Activity Monitor opens with its View popup set to My Processes, and coreaudiod does not run as you. It runs as its own reserved account, named _coreaudiod, so it is filtered out until you change the popup in the toolbar to All Processes. It has always been running; the default view just hides other users' processes. The same filter explains a related confusion: after a restart of the daemon its process id changes, so the pid you noted earlier no longer exists, and the daemon looks missing when it has simply been relaunched by launchd.
How do I restart coreaudiod on a Mac?
With an admin password, because the daemon does not run as you. The clean way is sudo launchctl kickstart -k system/com.apple.audio.coreaudiod, which asks launchd itself to stop and start the job. The blunter way is sudo killall coreaudiod, which kills the process and lets launchd bring it back within seconds, since the job has been running once, continuously, since boot. Either way, sound cuts out for a moment, then returns. You lose nothing durable: the device list is rebuilt from the hardware and the installed drivers. If sound is broken and this fixes it, the honest reading is that some client or driver wedged the audio engine, and the interesting question is which one.
Why is coreaudiod using so much CPU or memory?
A healthy coreaudiod is busy by design. On the Mac measured here it spent about sixty six minutes of processor time a day with nobody using the machine for audio, because every notification chime and every short sound powers the speakers up through four states and back down, and each burst also builds format converters for the sample rates in play. Memory between 20 and 33 MB is the normal range; the number moves because the engine allocates per burst and launchd has permission to reclaim it under pressure. A real problem looks different: a percentage that holds high for an hour while nothing is playing. The usual culprits are an app holding a stream open silently, a Bluetooth headset negotiating repeatedly, or a third-party virtual audio driver. Closing apps one by one, or toggling Bluetooth, will find it faster than killing the daemon, which restarts into the same clients.
What is /usr/sbin/coreaudiod, and is it a virus?
It is the Core Audio daemon's own program file, and it is Apple's. You can check in five seconds: codesign -dv /usr/sbin/coreaudiod reports Identifier=com.apple.audio.coreaudiod with a platform signature, the class of signing Apple reserves for the operating system's own files. Malware does occasionally imitate system process names, so the path column in Activity Monitor is the honest test. A real coreaudiod always lives at /usr/sbin/coreaudiod. The searches that pair the path with sudo killall are usually people dealing with a stuck audio state, and the restart question above covers that without deleting anything.
Ready? Buy Ribbon for $15, or read all the guides.