What is WirelessRadioManagerd on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
WirelessRadioManagerd is the Apple daemon that manages coexistence policy for the Mac's radios: rules that let more than one radio, such as Wi-Fi and Bluetooth, work at the same time without interfering. It is usually idle and becomes briefly active when radio use changes. It is part of macOS and safe.
WirelessRadioManagerd at a glance
| WirelessRadioManagerd | |
|---|---|
| Made by | Apple (part of macOS, wireless) |
| Type | System daemon |
| Location | /usr/sbin/WirelessRadioManagerd |
| Runs as | root |
| Started by | launchd job com.apple.WirelessRadioManager |
| Can you quit it? | Not usefully. launchd starts it again when the radios need coordinating. |
What is WirelessRadioManagerd?
The man page says WirelessRadioManagerd manages multiple radio coexistence policy and should not be invoked directly. Coexistence matters because Bluetooth and 2.4 GHz Wi-Fi use the same frequency band, so the system decides how they share it.
It runs as root from an Apple launch daemon and starts on demand. Apple does not document its internal rules.
Is WirelessRadioManagerd safe?
Yes. It lives in /usr/sbin on the read-only system volume and runs from an Apple launch daemon.
Why does WirelessRadioManagerd use so much CPU?
- Bluetooth and Wi-Fi in use together. Using Bluetooth headphones, keyboards or mice while Wi-Fi is busy is the situation coexistence policy exists for.
- Radio state changes. Turning Wi-Fi or Bluetooth on or off, connecting audio devices, or starting peer-to-peer features changes which radios are active.
- Wake from sleep. On wake, radios come back and their coordination is set up again.
How much CPU is normal for WirelessRadioManagerd?
Typical use is 0% CPU. Brief activity when devices connect or radios switch is normal.
Sustained CPU use is not typical.
What can you do if WirelessRadioManagerd is busy?
- Notice what changed. Check whether a Bluetooth device keeps connecting and disconnecting, or Wi-Fi keeps rejoining. Repeated changes keep the radio manager busy.
- Use 5 GHz or 6 GHz Wi-Fi if available. If your router offers a 5 GHz or 6 GHz network, joining it takes Wi-Fi off the band Bluetooth uses.
- Restart the Mac. If it stays busy with stable connections, restart.
When should you worry about WirelessRadioManagerd?
Constant CPU use is unusual and usually comes with Bluetooth or Wi-Fi problems such as audio dropouts. A copy outside /usr/sbin would not be Apple's.
How do you check WirelessRadioManagerd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type WirelessRadioManagerd 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 WirelessRadioManagerd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'WirelessRadioManagerd' | grep -v grep
How can Thrum help with WirelessRadioManagerd?
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 WirelessRadioManagerd 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
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 WirelessRadioManagerd
Can I turn off WirelessRadioManagerd?
No. It is part of macOS and is started by launchd when needed.
Is it related to cellular?
Macs have no cellular radio. On the Mac its job is coordinating the radios that are present, such as Wi-Fi and Bluetooth.
Sources
- WirelessRadioManagerd(8) man page: run man WirelessRadioManagerd in Terminal