bluetoothd on Mac: what it is and why it uses CPU

What bluetoothd does

Every Bluetooth conversation on a Mac goes through one process: bluetoothd. It owns the Bluetooth radio, keeps the list of paired devices, moves audio to your AirPods and headphones, reads your mouse and keyboard, and runs the short-range side of Handoff, AirDrop discovery, Universal Control and Apple Watch unlock. Apps never talk to the radio directly. They ask bluetoothd, and bluetoothd answers.

That is why it is always running, even on a Mac with Bluetooth switched off in the menu bar. With the radio off it sits idle, waiting. With a wireless keyboard and mouse it does a little steady work, roughly the same as the Mac reading a wired keyboard. It only becomes noticeable when something makes it work far harder than that.

What normal looks like

Why bluetoothd is using CPU right now

High CPU in bluetoothd is almost never bluetoothd being broken. It is bluetoothd being asked to do something over and over. The usual askers:

1. A device stuck in a connect, drop, reconnect loop. A low battery mouse or keyboard, or a pair of headphones at the edge of range, can reconnect several times a second. Each reconnect costs bluetoothd real work.
2. AirPods switching between your Mac, iPhone and iPad. Automatic switching is handy and mostly fine, but with three devices all awake it can bounce for a while.
3. An app with Bluetooth permission that scans constantly. Printer utilities, fitness apps, browser-based device tools and some virtual-device helpers scan for devices in the background. Each scan is a burst for bluetoothd. Check System Settings, Privacy & Security, Bluetooth for the list.
4. Many devices at once. Two keyboards, a mouse, headphones, a game controller and an Apple Watch is a lot of simultaneous links. Normal, but higher.
5. A bad state after sleep or an update. Sometimes the daemon simply wedges after waking. Toggling Bluetooth clears it.

In the long Apple Community thread on this, most people were on Monterey, saw 100 to 200 percent right after login, and found that switching Bluetooth off and back on brought it down, at least until the next wake.

Is it safe to quit bluetoothd?

Do not force quit it. bluetoothd runs as root and launchd restarts it immediately, so the only thing you achieve is a second or two with no mouse, keyboard or headphones, then the same process with the same problem. Some people use Terminal to kill it; that is the same thing with extra risk. The safe equivalent is turning Bluetooth off and on from the menu bar or Control Center, which stops and restarts the radio cleanly and resets every connection.

Use the checker above for any other process you see next to bluetoothd. The wireless side of a Mac has several helpers (sharingd, rapportd, wirelessproxd) and they usually spike together.

What to do, in order

1. Turn Bluetooth off and on

   Click the Bluetooth icon in the menu bar or Control Center and switch it off. Wait ten seconds. Switch it on. Watch bluetoothd in Activity Monitor. For most people it drops to near zero and stays there.

2. Find the device that keeps reconnecting

   In System Settings, Bluetooth, look for a device that flips between Connected and Not Connected. Charge it, move it closer, or disconnect it. If one device is the cause, bluetoothd settles the moment it is gone.

3. Check which apps can use Bluetooth

   System Settings, Privacy & Security, Bluetooth. Switch off any app you do not need scanning in the background: printer helpers, browser device access, old fitness or smart-home utilities. Quit that app and watch bluetoothd.

4. Calm down AirPods switching

   With your AirPods connected, open System Settings, Bluetooth, click the info button next to them, and set Connect to This Mac to When Last Connected to This Mac. The bouncing between devices stops.

5. Forget and re-pair a stubborn device

   Same Bluetooth settings pane, info button, Forget This Device. Then pair it again. This rewrites the device record and fixes most reconnect loops that survive a toggle.

6. Restart the Mac, and update macOS

   A restart clears any wedged state in the daemon. If the problem started after an update, check Software Update: Apple has shipped several Bluetooth fixes over the years, and in the Apple Community thread below most of the 2021 reports tailed off after later Monterey updates.

bluetoothd and a Mac that wakes at night

If your laptop loses battery overnight, the Bluetooth side is worth a look before anything else. A wireless mouse on a shared desk, a keyboard in a bag that gets bumped, or an Apple Watch unlock request can each wake the Mac. None of this is bluetoothd misbehaving; it is doing exactly what the wake setting allows. Our battery drain guide walks through the other wake sources.

When to worry

Worry a little if bluetoothd stays above 50 percent after a Bluetooth toggle, a restart, and a check of every paired device. That usually means an app is scanning hard; the Privacy settings list is where to find it. Worry more if bluetoothd's memory grows steadily over days without coming back after a toggle. That is a leak, and a restart followed by a Software Update is the fix. Worry about the hardware only if Bluetooth drops out for every device, including a brand new one, and the daemon stays wedged after a restart. Everything else is routine.

Safe to Quit, the Mac app this site comes from, shows the plain-English verdict for bluetoothd and every other process right in Activity Monitor terms, so you do not need to look each one up.