What coreaudiod does
The built-in man coreaudiod page gives a brief definition: a daemon for Core Audio purposes. It doesn't provide a consumer troubleshooting table or a normal CPU threshold. Core Audio is the system audio infrastructure, so several apps and devices can be involved in the work you see at once.
A process named coreaudiod appearing in Activity Monitor is therefore expected. That name doesn't establish which app is playing or recording, and a high reading doesn't by itself diagnose broken speakers, a failed chip or malware.
Distinguish three symptoms: no audio, audible distortion such as crackling, and high CPU without an audible problem. Record which one you actually have before changing a driver or the audio-device configuration.
Where it runs on this Mac
Read-only checks on our M2 Max documentation Mac, macOS 27.0.1, on 23 October 2026 found the executable at:
/usr/sbin/coreaudiodThe running service belonged to _coreaudiod, a separate system account, not the logged-in user. We checked the owner and path without restarting the service, playing test audio or measuring a CPU percentage.
In Activity Monitor, choose View › All Processes and show the User column through View › Columns if needed. That keeps a system-owned service visible. The process-name reference explains other entries you may encounter.
Find the app or device that changes the symptom
Think about what started immediately before it happened: a call, browser tab, audio workstation, USB interface, external display or wireless output. A repeatable change is more useful than a guess based on one process snapshot.
| Pattern | Useful next test |
|---|---|
| One app or project triggers it | Save, close that app normally and compare another known audio source. |
| Only one output device has the problem | Compare the built-in speakers and that external path. |
| Starts after a driver update | Check the manufacturer's current macOS support and instructions. |
| All apps and built-in output fail | Check system sound settings, restart normally and seek help if persistent. |
Pause optional audio and close unused call or media apps one at a time. If CPU falls or sound returns, repeat the same controlled action before assigning a cause. No universal percentage or duration in the sources tells you that a single snapshot is a fault.
Check the output and basic sound controls
On macOS 15 Sequoia, 26 Tahoe or 27 Golden Gate, open System Settings › Sound › Output. Select the intended device. Check output volume, mute and the app's own volume controls.
For a built-in-speaker test, disconnect headphones or external speakers first. Apple recommends trying another audio file or source to isolate whether the problem belongs to the content. Keep the volume comfortable rather than turning it up sharply to chase an intermittent sound.
If you expected audio from a display or USB interface, check that device's power, connection and selected output. A monitor showing a picture doesn't prove that the intended audio output is selected. Test a direct connection when an optional hub or dock is involved.
For a USB device missing from the output list, Apple suggests checking System Information › Hardware › USB to see whether it is detected, then reconnecting it if needed. Detection, output selection and a compatible driver are separate checks.
Review drivers and Audio MIDI Setup
Apple's Audio MIDI Setup guide says a third-party audio driver can conflict with apps using standard macOS drivers. Check the hardware manufacturer's website for a current compatible driver and follow its supported installation or removal method.
Don't delete arbitrary audio plug-ins or system folders from an old internet checklist. A professional project may depend on a specific device, plug-in or routing configuration; record it and protect the project before changing that setup.
Open Finder › Applications › Utilities › Audio MIDI Setup if your workflow uses its controls. Select the device and inspect its supported options. Apple's guide covers choosing the input/output role and device-specific format settings. Change sample rate, channel configuration or clock source only according to the hardware or app's requirements.
A temporary test with the Mac's own output can help distinguish a third-party path. It doesn't prove that the external hardware itself is defective: its cable, driver, routing and compatibility remain possible variables.
Restart the affected app, then update if needed
Save work and quit the affected app normally. Reopen it and repeat the smallest action that triggers the issue. If the app can't quit, use the force-quit guide with its unsaved-work warning.
If several apps remain affected, save and use Apple menu › Restart. Check supported updates for macOS, the app and the device software. The app-update guide covers the genuine vendor and App Store routes.
Keep the exact macOS version, app version, device and trigger for support. If the built-in speakers still fail after Apple's basic checks, contact Apple. If one audio interface or plug-in is the consistent trigger, its vendor is the more specific next contact.
Don't keep terminating the service
Force-stopping coreaudiod can interrupt audio for multiple apps, including recording or calls. Repeatedly killing it in a script obscures the original pattern and may discard useful work without fixing the driver or app.
Its binary belongs to macOS. Don't remove it, unload it permanently or weaken System Integrity Protection to edit the service. If the whole Mac also slows down, use the wider workload diagnosis rather than treating audio as the only possible cause.
What Tend shows
Tend lists processes in your account, so the system-owned coreaudiod checked here doesn't appear by name. Its cost remains in the overall macOS share. Your audio and call apps can show free CPU, memory and estimated watts, but those app estimates don't fully attribute the system service's work or identify a crackling driver.
Questions
What is coreaudiod?
It is a macOS daemon for Core Audio. Its presence is expected; the process name does not identify one app, output device or hardware fault.
Why is coreaudiod using high CPU?
Investigate the app, audio device and driver active when it happens. Note whether the reading settles after closing one app or changing to the built-in output; a snapshot alone does not establish a cause.
Should I force quit coreaudiod?
Start with saving and quitting the affected app, checking the output and restarting normally. Terminating the audio service can interrupt multiple apps, and repeatedly doing so does not repair the underlying trigger.
Why is coreaudiod missing from Tend's app list?
On the checked Mac it runs as the separate _coreaudiod system account. Tend lists your own account’s processes, so that service’s work remains in the overall macOS share.
Related guides
Activity Monitor
Inspect the actual owner and workload.
Diagnose slowness
Check the wider Mac if needed.
Update apps
Keep the app and its supported components current.
System Integrity Protection
Keep protected system services intact.
Sources
- Apple, Change sound output settings
- Apple, If you cannot hear sound, macOS 26
- Apple, If you cannot hear sound, macOS 27
- Apple, Set up audio devices
- Apple, Third-party audio-driver compatibility
- Apple, Activity Monitor process views
- macOS,
man coreaudiodand read-only process owner/path checks on 23 October 2026; no audio experiment or service restart performed.
See the apps feeding the audio workload
Tend is free to download. Pro is $1.99 a month, $12.99 a year with a 7-day free trial, or $29.99 once.