bluetoothd, the daemon that runs your Mac's Bluetooth
The root daemon behind every Bluetooth connection on a Mac: the fifteen doors it opens, the hour of log it writes while idle, and the chip it drives.
By Chethan Kumar S N · Updated
Of all the processes people find in Activity Monitor and then search for, bluetoothd has the most human search results. Alongside the usual what is this process questions sit two that tell a story: bluetoothd high cpu, typed by someone whose fan is spinning, and sudo pkill bluetoothd mac, typed by someone who has already decided to kill it and wants to know the consequences. This page is for both of those people, and it is built the way the other process pages in this series are built: from the daemon’s own property lists, its own launchd state, its own log, and its own binary, all measured read only on one Mac running macOS 27.0.1 on an M1 Pro. Nothing was quit, killed, deleted or changed while measuring, and the commands to repeat every measurement are at the end.
The one sentence version: bluetoothd is the daemon that runs Bluetooth on your Mac. Every pairing, every connection, every AirDrop handshake and every Find My beep your Mac relays for a stranger’s lost keys goes through this one root-owned process. When you flip the Bluetooth switch in Control Centre, this is the thing you are flipping.
What the process is, in one command
ps -Ao pid,ppid,user,%cpu,rss,time,etime,comm | grep [b]luetoothd
77388 1 root 0.0 18976 58:49.32 05-23:55:48 /usr/sbin/bluetoothd
Everything important is in that row. Parent process 1 means launchd started it, the standard signature of a system daemon rather than something you opened. The user is root, one of a small number of processes on a healthy Mac that legitimately run as root at all times, because a Bluetooth controller is a system resource that every logged in user shares. The path is /usr/sbin/bluetoothd, on the sealed system volume that macOS itself cannot modify at runtime. It had been alive for just under six days, using 18,976 KB of resident memory, about 18.5 MB, and 58 minutes and 49 seconds of processor time across that whole stretch, which works out to roughly nine and a half minutes a day on a ten core machine. That is the entire cost of Bluetooth on a Mac that had six paired devices and an Apple Watch nearby.
The binary itself is worth a look, because it is much bigger than people expect:
ls -l /usr/sbin/bluetoothd
-rwxr-xr-x 1 root wheel 37625024 Sep 24 12:40 /usr/sbin/bluetoothd
Thirty six megabytes, three architectures (x86_64, arm64e and arm64e.x1), signed by Apple on 19 September 2026 with a Platform identifier of 26, which is the macOS 27 platform. For comparison, trustd, the daemon that checks every certificate your Mac sees, is a fraction of this size, and airportd, which runs the machine’s other radio and all of its Wi-Fi, does the whole job from a binary a twelfth of this one. Bluetooth is a big job: two radio standards, a dozen profiles, audio timing, and a certification test suite, all in one process.
The manual entry that does not exist
Other daemons in this series have man pages, even bad ones. trustd’s is two sentences from 2017. rapportd’s is two sentences from 2016. bluetoothd has none at all: man bluetoothd on macOS 27 returns No manual entry for bluetoothd, and there is no bluetoothd file in any of the man directories. A root-owned, always-running, 36 MB system process with complete control of a radio has literally no user-facing documentation by name anywhere on the disk.
That is the pattern for this whole stack. Apple’s Activity Monitor guide and its Continuity page, both fetched while writing this, mention Bluetooth the feature in passing but contain zero occurrences of the string bluetoothd. The developer side documents the framework instead: Core Bluetooth is described as providing the classes needed for apps to communicate with Bluetooth equipped low energy and BR/EDR, meaning Classic, devices. The framework is the client. The daemon is the server. Only one of them has a documentation page.
Fifteen doors and what knocks on them
A daemon’s Mach services list is the set of doors it opens for other processes, and bluetoothd’s property list opens fifteen of them. Reading the names is the fastest way to understand what the daemon actually is:
com.apple.bluetooth.xpcandcom.apple.server.bluetooth.general.xpc, the main doors for Bluetooth state and settingscom.apple.server.bluetooth.classic.xpc,le.att.xpcandle.pipe.xpc, Classic Bluetooth and the Low Energy attribute protocolcom.apple.BTAudioHALPlugin.xpc, the audio path, which is how Bluetooth headphones get a hardware audio device; the daemon holding the other side of that door is coreaudiodcom.apple.bluetooth.cloudkit.xpc, the iCloud side, syncing your paired device list through your accountcom.apple.bluetooth.BTPacketLoggerand a second.ioscopy, the packet capture interface developers usecom.apple.wirelessproxd, the proximity door, which is how AirDrop and Handoff feel for nearby devicescom.apple.ExposureNotification, plus a user notification delegate for it, the contact tracing machinery registered inside the Bluetooth daemon, inactive on this Mac but present in every copy of macOScom.apple.ULLAConcierge.xpc.diagnostics, a diagnostics door, andcom.apple.server.bluetooth.bbprovider.xpc, the baseband provider
At the moment of measurement, launchd’s live state showed eleven of those ports registered, with eight actively held by clients. The property list also declares two events the daemon publishes, com.apple.bluetooth.connections and com.apple.bluetooth.discovery, which is the rest of the system subscribing to connection news, and one event it wakes on, the carrier activation state notification, because a Bluetooth controller is inert until the system says it is activated.
The door count is the answer to a question people ask in a more confused way: bluetoothd is not just your headphones. It is the radio’s reception desk for audio, input devices, file transfer, proximity, iCloud, and a public health API, in one process, all the time.
The job launchd gives it
launchctl print system/com.apple.bluetoothd
The interesting lines: runs = 7, immediate reason = ipc (mach), last exit code = 0, exit timeout = 5, minimum runtime = 10. Runs at seven with the Mac 26 days up means the daemon has been recycled six times since boot, each time cleanly, and the immediate reason line means what woke it this time was another process knocking on one of those fifteen doors, not a timer. Contrast that with cloudd, the iCloud daemon, which carries EnablePressuredExit true and gets reclaimed by the memory system whenever it is idle. bluetoothd carries EnablePressuredExit false, deliberately, because a radio stack that vanishes under memory pressure stops being able to receive connections. The system would rather keep 18 MB permanently resident than miss your keyboard reconnecting.
There is also a KeepAlive rule, keep alive unless the exit was successful, which sounds backwards until you read it as: a daemon that exits with a clean status finished its job, a daemon that was killed did not, so always come back. That rule is why the pkill suggestion that circulates in forum threads does nothing lasting, covered properly in the questions above.
One quiet hour, counted
The most useful thing anyone can do with a daemon they are suspicious of is count what it does. So, for one hour, on a Mac with Bluetooth on, no audio playing, no file transferring, and no device connecting:
log show --last 60m --predicate 'process == "bluetoothd"' | wc -l
18989
17,765 of those lines were the daemon itself talking, about 4.9 messages a second, on a quiet Mac. Sorted by subsystem, the hour breaks down like this:
| Subsystem | Lines | What it is doing |
|---|---|---|
| Server.LE.Scan | 12,567 | scanning for Low Energy advertisements, two thirds of everything |
| WirelessProximity | 1,118 | handling sharingd’s nearby device scans |
| Server.MacCoex | 720 | posting Wi-Fi/Bluetooth coexistence status, exactly every 5 seconds |
| Server.XPC | 655 | answering clients at those fifteen doors |
| Server.LE.Advertise | 287 | making this Mac visible to other devices |
The top row is the story. Your Mac is not waiting for Bluetooth to happen. It is continuously, actively listening for Low Energy advertisements, other people’s Find My tags, TVs, watches, beacons, anything broadcasting, because features like Find My, AirDrop and Continuity cannot work if the Mac only listens after you ask. Deeper in the scan lines, the internal buffer names are Wild and NearOwner, Find My vocabulary: one buffer for advertisements from anyone’s devices, one for your own.
The second row has a face on it. Every ten seconds, exactly, the daemon logs a scan request from sharingd, with a note of the current screen state, whether the screen being off means no scan, and a received signal strength of -90 dBm, which is the edge of hearing. That is Handoff and AirDrop asking, ten times a minute, all day, whether anything interesting has come near.
And it finds things. In that one hour, the daemon resolved thirteen distinct nearby devices, and one log line shows the anatomy of a single discovery: an advertisement heard on channel 39 at -88 dBm, carrying NearbyInfo data, flagged Ranging, with a Duet, meaning on-device machine learning, attribution. A device walked past this Mac, and the Bluetooth daemon, the Find My buffers and an ML model all woke up to decide, in this case correctly, that it was nobody’s.
The third row is the drumbeat: 720 lines in 3,600 seconds is one line every five seconds, on the nose, all hour. MacCoex is Wi-Fi and Bluetooth coexistence, the negotiation that stops your 2.4 GHz Wi-Fi and your Bluetooth radio, which share the same air, from talking over each other. Both radios live on the same chip in a modern Mac, so the daemon posts a status notification every five seconds forever, whether anything is connected or not. If you ever wondered what a truly idle Bluetooth daemon does with 9.8 minutes of processor time a day, it is mostly this: scan, listen for sharingd, announce coexistence, repeat.
The night shift: Find My, on battery, while you sleep
launchd’s state for the daemon also lists its timers, and they explain work nobody asked about. One repeating trigger is named com.apple.icloud.searchpartyd.SPBeaconManager.bluetoothd, which is the Find My beacon manager: hourly, with a 30 minute grace period, allowed to run on battery, allowed to run during Power Nap, at Utility priority. Your Mac periodically advertises itself as a findable beacon and listens for others, asleep or awake, plugged in or not. That is the feature Apple describes as helping you locate a lost device, and this trigger is the part of it that lives inside the Bluetooth daemon rather than the Find My app. The daemon the trigger is named after has its own page: searchpartyd, the root process that runs the beacon machinery on the other end of this timer.
A second trigger runs every fifteen minutes at Maintenance priority, named CBMetrics, which is the daemon grading its own radio performance. Two more run daily: an analytics report, and one whose name contains a small piece of evidence that Apple’s engineers are human, com.apple.Bluetoooom.WPDAdvertisingManager, with three o’s in Bluetooth, a typo that has presumably shipped in every macOS build since the trigger was created. None of these are configurable. All of them are cheap. But if you have ever watched a sleeping Mac’s Bluetooth process tick over, those four timers are the agenda.
The chip it drives
Every couple of minutes, some client asks the daemon for a controller report, and the answer it gets back is a complete inventory of the radio hardware, which on this Mac reads:
Chip BCM_4387, FrmV 24.1.640.5756, HCIT PCIe, LMPv 12 (5.3)
SSrv: HFP AVRCP A2DP HID LEA AACP GATT SerialPort SCO
That is a Broadcom BCM4387, the same family of combo chip that carries both Wi-Fi and Bluetooth, attached over PCIe, speaking Bluetooth 5.3, and supporting nine services: the headset and call profiles (HFP, SCO), the audio streaming profile (A2DP) with its remote control (AVRCP), keyboards and mice (HID), the LE Audio path (LEA, AACP), the Low Energy attribute layer everyone calls GATT, and serial ports. The firmware filename in the same log line is longer than the report, and includes the internal codename MadagascarES2, a three antenna configuration, and a build date of 4 February 2026. Firmware updates for this chip arrive quietly inside macOS updates, which is why a macOS update sometimes fixes a headphone glitch: the thing being updated is this firmware, delivered by this daemon.
The same inventory lists this Mac’s six paired devices, none currently connected: two keyboards, a mouse, an iPhone, AirPods Pro, and an Apple Watch sitting three metres away at -49 dBm, close enough to be heard constantly but not connected. The pairing database itself lives in the daemon’s own preferences domain, and the only readable entries in it, besides the cryptographic pairing keys, are two harmless keys recording the last time audio played and the hardware address of the last pair of headphones it played to. The daemon remembers your last headset by address, which is exactly as mundane as it sounds.
The headset secrets hiding in the binary
Thirty six megabytes of binary has to contain something, and reading the strings inside bluetoothd is a tour of twenty years of Bluetooth engineering. There are more than 2,200 log format strings mentioning GATT, L2CAP, A2DP or HCI, the protocol stack from top to bottom. And buried among the audio strings is evidence of a genuinely charming practice: per vendor audio tuning. One string reads A2DP Dynamic Latency JBL %i, and others track the current dynamic latency for that same vendor. The daemon adjusts the audio buffer delay, the thing that decides whether your video lipsync survives, based on which manufacturer’s headphones are connected, with special cases compiled in. Every JBL owner’s Mac is running a private JBL code path. That is the level of accommodation this daemon is built to.
Why Activity Monitor shows several Bluetooth rows
bluetoothd is the only always-on process of the set, but macOS ships five more Bluetooth launch jobs alongside it, and they start on demand: bluetoothuserd and bluetoothUIServer for user session services, bluetoothaudiod for audio routing, bluetoothuiservice for interface glue, and BlueTool, the older firmware loader. During the hour measured here, none of them were running, because nothing needed them. Two other rows you might see are a DriverKit process, IOUserBluetoothSerialDriver, running as the reserved user _driverkit on this Mac, and, if you have the Bluetooth widget in your menu bar’s settings, a small app intents extension. Six blue-ish rows in Activity Monitor on a Mac with Bluetooth problems is normal, not an infestation.
How to look at your own
Everything on this page came from read only commands that any Mac can run:
ps -Ao pid,ppid,user,%cpu,rss,time,etime,comm | grep [b]luetoothd
launchctl print system/com.apple.bluetoothd
plutil -p /System/Library/LaunchDaemons/com.apple.bluetoothd.plist
log show --last 60m --predicate 'process == "bluetoothd"' | wc -l
system_profiler SPBluetoothDataType
The log count is the honest health check. A quiet Mac produces thousands of lines an hour, dominated by the LE scan, and the counts are steady. A Mac with a Bluetooth problem produces the same scan traffic plus a reconnection loop, and the loop is visible if you sort by subsystem and watch one device’s address appear every few seconds in connect and disconnect pairs. If the number of lines per minute is climbing hour over hour with no device activity, that is the log of something wrong, and the gentle fixes above are the order to try them in.
Where window managers fit
This page is about a radio; the complaint that brings people to a window manager is about screen space. They share one thing: both are full of invisible machinery that either earns its keep or gets in the way. A daemon writing five log lines a second so your AirPods can reconnect instantly is machinery earning its keep.
Ribbon is a window manager built on the same instinct, keep things visible instead of stacked. Windows stay at full size on a single scrolling strip, so the window you want is one swipe away and nothing hides behind anything. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. There is a browser demo of the strip if you want to feel it before installing anything.
The short version
bluetoothd is the root daemon that runs Bluetooth: the pairings, the connections, the audio, the Find My participation, the advertisement scanning that never stops, and the five second coexistence heartbeat between your Wi-Fi and Bluetooth radios. It has no man page, no Settings pane of its own, and no mention by name anywhere in Apple’s user facing help, which is why a root process with a lowercase name ends up in so many searches.
Measured honestly, it is cheap: 18 MB resident, about ten minutes of processor time a day on a ten core Mac, six clean restarts in 26 days, and 17,765 log lines in a quiet hour that decompose into a scan, a proximity request from sharingd, and a status post, repeated all day. High CPU that persists means a device is misbehaving, not that the daemon is, and the Control Centre toggle restarts the whole stack without touching any files.
The pkill command buys seconds of quiet before launchd brings it straight back, exactly as its KeepAlive rule says. The switches that actually exist are named after features, not machinery: the Bluetooth toggle, the device list, and the Find My setting. Everything else on this page, the thirteen strangers’ devices resolved in an hour, the JBL latency table, the nightly analytics, the three o’s in Bluetoooom, is just what a quarter century of Bluetooth looks like from inside one very busy daemon.
Questions
What is bluetoothd on Mac?
It is the daemon that runs Bluetooth. Every pairing, every AirDrop and Handoff handshake, every Bluetooth mouse, keyboard and headphone, and the Find My network participation that lets your Mac help strangers find their lost keys, all go through this one process. It runs as root, started by launchd at boot, from the binary at /usr/sbin/bluetoothd on the sealed system volume. On the Mac measured here it had been running for six days straight, using about 18 MB of memory and under one per cent of one processor core, while writing a log entry roughly five times a second. It is not something you installed and not something you configure directly. The Bluetooth switch in Control Centre is its front door.
Is bluetoothd a virus or malware?
No. It is Apple's own code. The binary is signed by Apple's system authority, sits on the read-only system volume, and launchd starts it from a property list in the system LaunchDaemons folder, none of which malware can do without already having your administrator password. People search the name because it runs as root, shows no icon in Activity Monitor, and never appears by name in any Settings pane or support page, which is exactly the shape a suspicious-looking-but-boring system process has. If you want to check yours, compare the path: the real one is /usr/sbin/bluetoothd. A process with that name running from your home folder, Downloads, or a browser profile folder would be worth a closer look.
Why is bluetoothd using high CPU?
Normally it barely registers: nine and a half minutes of processor time per day on the Mac measured here, about 0.7 per cent of one core, and that includes running a continuous Low Energy scan for other devices. A real spike usually has one of four causes: a device that keeps dropping and reconnecting, a pairing that never completes, a misbehaving Bluetooth audio device being re-negotiated, or a flood of nearby devices during discovery. The signature of a problem is not the percentage alone but the percentage that persists for an hour while no device is connecting. The fixes, in order of gentleness: toggle Bluetooth off and on from Control Centre, unpair and re-pair the suspect device, then reboot. Toggling restarts the stack, which is the same reset a support article used to get from deleting a preferences file, without touching any files.
Why is bluetoothd using so much memory?
About 18 to 19 MB is its normal size on an Apple silicon Mac, and it is not a leak. The daemon holds the tables for every paired device, every active connection, the advertisement filters used to notice nearby devices without waking the whole system, and the buffers for the packet logger that developers use to debug Bluetooth. Its job configuration explicitly turns off EnablePressuredExit, the flag that lets the system reclaim idle daemons, because the radio needs a process that is always resident to catch incoming connections. Memory that climbs into hundreds of megabytes after days of uptime, or grows steadily while nothing pairs, would be unusual, and a reboot resets it. A steady 19 MB is the daemon doing its job.
What happens if I run sudo pkill bluetoothd?
It dies, and launchd brings it back within seconds. The job's KeepAlive rule says keep it alive unless it exited successfully, which in practice means always, and on the Mac measured here the system itself had already restarted it six times since the last boot with a clean exit code each time. You will lose any active Bluetooth connections, and audio will cut out, and if an accessory firmware update is mid-flight, which is the one genuinely bad moment, the update can be left half applied. So the honest ranking: toggling Bluetooth in Control Centre achieves the same restart through the front door, unpairing and re-pairing fixes the device that was probably the reason you reached for pkill, and the command itself buys you nothing those two do not.
Ready? Buy Ribbon for $15, or read all the guides.