bluetoothd high CPU on Mac? Usually a device or a bug
bluetoothd using high CPU on your Mac isn't normal. It's almost always a specific flaky Bluetooth device or an OS bug. Here's how to isolate the device and the fixes that actually work.
bluetoothd manages all of your Mac's Bluetooth. Unlike most background daemons, high CPU here usually isn't routine work. It's a sign that one specific device or connection is misbehaving, or that you've hit a known macOS bug. The fix is to isolate the culprit, not to fight the daemon.
What bluetoothd does
It's the root-privileged process that runs the entire Bluetooth stack: radio control, device pairing, connection management, and low-energy (BLE) communication, including the BLE advertisements used by Find My. Normally it barely registers on the CPU. (On older OS X, up through El Capitan, this daemon was called blued.)
Why it's using high CPU
It's almost always a specific misbehaving device or an OS bug, not normal operation. Documented triggers include:
- Waking from a long sleep with Bluetooth on.
- A particular flaky peripheral: some mice and other devices have been reported to put it in a loop.
- A known macOS bug that was fixed in Monterey 12.3 and later.
- Corrupted Bluetooth preference files.
Is bluetoothd a virus?
No. It's an essential, legitimate Apple process running from a protected system path.
What to do about it
- Toggle Bluetooth off and back on, or restart the daemon with
sudo pkill bluetoothd(it relaunches automatically), the least disruptive first step. - Isolate the device. Disconnect or "Forget" a suspect device, then reconnect. If the spike stops, you've found it.
- Update macOS: a known Bluetooth bug was fixed in 12.3, and later fixes have followed.
- Reset the Bluetooth preferences if it persists: delete the
com.apple.Bluetooth.*.plistfiles in~/Library/Preferences/ByHost/and reboot so macOS regenerates them.
What people get wrong
It's easy to blame the daemon, but the cause is almost always an external device or a version-specific OS bug, not bluetoothd itself. So isolate the device or update macOS; don't try to kill it permanently. You can't (the system restarts it), and Bluetooth stops working while it's down.
Find the device behind the spike
The hard part of a Bluetooth CPU problem is connecting the daemon to the one device causing it. Plumby keeps live CPU and your paired Bluetooth devices visible in the menu bar, with the process named plainly, so you can spot the pattern and isolate the culprit faster. Measured from your Mac's real state, never estimated.
