What is BTLEServer, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
BTLEServer is a macOS daemon that handles Bluetooth LE (Low Energy) features, the low-power form of Bluetooth used by many accessories and sensors. launchd starts it on demand, and it is idle most of the time. Activity usually follows a Bluetooth LE accessory connecting or a health sensor such as a heart-rate monitor.
BTLEServer at a glance
| BTLEServer | |
|---|---|
| Made by | Apple (part of macOS, Bluetooth) |
| Type | System daemon |
| Location | /usr/sbin/BTLEServer |
| Runs as | root |
| Started by | launchd job com.apple.BTServer.le |
| Can you quit it? | Not usefully. launchd starts it again when a Bluetooth LE feature needs it. |
What is BTLEServer?
The BTLEServer man page says it is a process that handles Bluetooth LE features. The main Bluetooth daemon is bluetoothd; BTLEServer is a separate root daemon started through the launchd job com.apple.BTServer.le.
Its launchd job provides services for Bluetooth LE audio control and logging, and lists notifications about a connected heart-rate monitor and health peripherals as launch triggers, so pairing a Bluetooth heart-rate strap is one thing that starts it. On the Mac checked here it had not run since startup.
Is BTLEServer safe?
Yes. BTLEServer is part of macOS at /usr/sbin/BTLEServer, runs as root and is signed by Apple.
Why does BTLEServer use so much CPU and energy?
- Bluetooth LE accessories. Accessories that use Bluetooth LE can involve BTLEServer when they connect and while they exchange data.
- Health sensors. Heart-rate monitors and other health peripherals are named in its launch triggers.
- A device that keeps reconnecting. An accessory at the edge of range, or with a low battery, can drop and reconnect over and over, which keeps Bluetooth processes working.
How much CPU is normal for BTLEServer?
Typical: often not running. When it runs, near 0% CPU with short bursts when accessories connect.
Continuous CPU use with no Bluetooth LE accessories in use is unusual.
How do you calm down BTLEServer?
- Check connected Bluetooth devices. Open System Settings > Bluetooth and look at which devices are connected. Disconnect ones you are not using.
- Remove old pairings. Remove devices you no longer own from the Bluetooth list so the Mac stops looking for them.
- Charge or move the accessory. Low batteries and distance cause repeated reconnects. Charge the accessory and keep it close to the Mac.
- Turn Bluetooth off briefly. Turning Bluetooth off and on in Control Center resets connections. If BTLEServer settles, one device was the cause.
When should you worry about BTLEServer?
Look closer if BTLEServer stays busy with every accessory disconnected. A copy outside /usr/sbin would not be Apple's.
How do you check BTLEServer in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type BTLEServer 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 BTLEServer process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'BTLEServer' | grep -v grep
pmset -g assertions # shows processes keeping the Mac awake
How can Thrum help with BTLEServer?
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 BTLEServer 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 BTLEServer
What is the difference between BTLEServer and bluetoothd?
bluetoothd is the main Bluetooth daemon for all connections. BTLEServer handles features specific to Bluetooth LE.
Does BTLEServer drain the battery?
Not on its own. Bluetooth activity costs a little energy, mostly when an accessory keeps reconnecting.
Sources
- BTLEServer(1) man page: run man BTLEServer in Terminal
- launchd job: run plutil -p /System/Library/LaunchDaemons/com.apple.BTServer.le.plist in Terminal