Thrum

What is bluetoothd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and code signature checked on macOS 26.3.1.

bluetoothd is the macOS daemon that runs Bluetooth: it connects keyboards, mice, trackpads, headphones and other accessories, and scans for nearby devices for features such as AirDrop and Handoff. It uses CPU when audio is streaming, when many devices are connected or nearby, or when a device keeps dropping and reconnecting. It is part of macOS and must keep running.

bluetoothd at a glance

bluetoothd
Made byApple (part of macOS, Bluetooth)
TypeSystem daemon
Location/usr/sbin/bluetoothd
Runs asroot
Started bylaunchd job com.apple.bluetoothd
Can you quit it?No. It runs the Bluetooth hardware, so keyboards, mice and headphones disconnect while it is gone.

What is bluetoothd?

bluetoothd runs as root from /usr/sbin, starts at boot, and launchd restarts it if it exits with an error. Apple does not publish a man page for it. Its launchd job registers services for classic Bluetooth, Bluetooth Low Energy, the Bluetooth audio driver and packet logging, which shows that keyboards, audio devices and low-energy features all pass through it.

Features such as AirDrop use Bluetooth Low Energy to find nearby devices, as Apple's security guide explains, so bluetoothd is active even when no accessory is connected.

Is bluetoothd safe?

Yes. bluetoothd is part of macOS, signed by Apple with the identifier com.apple.bluetoothd, and lives on the read-only system volume.

Why does bluetoothd use so much CPU and energy?

How much CPU is normal for bluetoothd?

Typical use is 0 to 2% CPU with input devices connected. A few percent while streaming audio is normal.

Sustained use above 10% with nothing streaming usually points to a misbehaving device.

How do you stop bluetoothd from using so much CPU?

  1. Check connected devices. Open System Settings > Bluetooth to see what is connected. Run system_profiler SPBluetoothDataType in Terminal for details of the controller and paired devices.
  2. Disconnect devices one at a time. Turn off accessories you are not using and watch bluetoothd in Activity Monitor.
  3. Charge or replace weak batteries. Low batteries cause dropouts and reconnects.
  4. Remove old pairings. In Bluetooth settings, click the Info button next to devices you no longer use and choose Forget This Device….
  5. Turn Bluetooth off and on. Use Control Center to switch Bluetooth off and on. If it stays high, restart the Mac.

When should you worry about bluetoothd?

Look closer if bluetoothd stays above about 10% CPU for a long time with no audio playing, or devices keep disconnecting. A copy outside /usr/sbin would not be Apple's.

How do you check bluetoothd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type bluetoothd in the search field. The CPU tab shows its % CPU. The Energy tab shows its Energy Impact. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every bluetoothd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'bluetoothd' | grep -v grep
pmset -g assertions    # shows processes keeping the Mac awake

How can Thrum help with bluetoothd?

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 bluetoothd 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 bluetoothd

Can I quit bluetoothd?

It is not useful; macOS needs it to keep Bluetooth devices connected, and launchd starts it again.

Does turning Bluetooth off stop bluetoothd?

It stops the radio work, but the daemon can stay loaded. AirDrop, Handoff and Universal Control need Bluetooth on.

Why does bluetoothd use CPU with no devices connected?

Features such as AirDrop and Handoff scan for nearby devices over Bluetooth Low Energy.

Sources