What is AudioComponentRegistrar, and why is it using CPU?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and plug-in folders checked on macOS 26.3.1.
AudioComponentRegistrar is the AudioToolbox helper that keeps track of the audio components installed on your Mac, which includes Audio Unit plug-ins (effects and instruments) used by music and audio apps. It works when plug-ins are installed or updated and when an audio app asks for the list, then goes idle. Large plug-in collections make each scan longer.
AudioComponentRegistrar at a glance
| AudioComponentRegistrar | |
|---|---|
| Made by | Apple (part of macOS, AudioToolbox) |
| Type | Launch agent and system daemon |
| Location | /System/Library/Frameworks/AudioToolbox.framework/AudioComponentRegistrar |
| Runs as | your user |
| Started by | launchd job com.apple.audio.AudioComponentRegistrar |
| Can you quit it? | Yes. launchd starts it again when an app needs the list of audio components. |
What is AudioComponentRegistrar?
Audio Units are macOS's audio plug-in format: effects, instruments and other processors that apps like GarageBand, Logic Pro and other audio apps load. They come as component bundles in /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components, and as Audio Unit v3 app extensions inside apps. AudioComponentRegistrar is the AudioToolbox process whose job, as its name says, is registering these audio components so apps can find them; it keeps a cache for that.
It has two launchd jobs with the label com.apple.audio.AudioComponentRegistrar: a launch agent that runs as your user and a system daemon that runs as root. Both start on demand.
Is AudioComponentRegistrar safe?
Yes. AudioComponentRegistrar is part of macOS, signed by Apple, and lives inside /System/Library/Frameworks/AudioToolbox.framework on the read-only system volume.
Why does AudioComponentRegistrar use so much CPU?
- Installing or updating plug-ins. New or updated Audio Unit bundles and apps that contain Audio Unit extensions change the list of components, so it has to be registered again.
- Opening an audio app. Music and audio apps ask for the list of available Audio Units when they start, which can wake it.
- Large plug-in collections. Hundreds of plug-ins from several vendors mean more bundles and extensions to look at on each scan.
- A plug-in that keeps changing. A plug-in installer or license manager that rewrites its bundle repeatedly can trigger repeated registration.
How much CPU is normal for AudioComponentRegistrar?
Absent or near 0% CPU most of the time. A burst of seconds to a few minutes after installing plug-ins or when an audio app starts is typical, longer with very large plug-in collections.
How do you stop AudioComponentRegistrar from using so much CPU?
- Let the scan finish. After installing or updating plug-ins, give it time to finish before opening your audio app, or leave the app on its startup screen until AudioComponentRegistrar drops back.
- Remove plug-ins you no longer use. Delete unused Audio Unit bundles from
/Library/Audio/Plug-Ins/Componentsand~/Library/Audio/Plug-Ins/Components, preferably with the vendor's uninstaller, and remove apps whose Audio Unit extensions you do not need. - Update or remove a misbehaving plug-in. If it is busy every time you start your audio app, a plug-in may be failing to load. Your audio app's plug-in manager usually names it.
When should you worry about AudioComponentRegistrar?
Look closer if AudioComponentRegistrar keeps returning to high CPU with no installs and no audio app opening. A plug-in or helper that keeps rewriting files is the likely cause.
It should run only from inside AudioToolbox.framework.
How do you check AudioComponentRegistrar in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type AudioComponentRegistrar 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 AudioComponentRegistrar process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'AudioComponentRegistrar' | grep -v grep
How can Thrum help with AudioComponentRegistrar?
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 AudioComponentRegistrar 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. Click AudioComponentRegistrar in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 AudioComponentRegistrar
Why does it run when I have no music software?
macOS ships its own Audio Units, and any app that uses audio processing can ask for the list of components.
Why are there two AudioComponentRegistrar jobs?
One runs as your user and one as root, both under the same launchd label, and each starts only when needed.