sharingd high CPU on Mac? AirDrop & Handoff, explained
sharingd using high CPU on your Mac powers AirDrop, Handoff, and Continuity, and usually spikes on a stuck AirDrop or constant wireless retries. Here's how to calm it, and the privacy angle worth knowing.
sharingd powers your Mac's sharing and Continuity features: AirDrop, Handoff, and more. High CPU usually means a stuck AirDrop transfer or repeated wireless discovery retries. Here's how to settle it, plus a privacy point worth knowing.
What sharingd does
Its own description: it "enables AirDrop, Handoff, Instant Hotspot, Shared Computers, and Remote Disc in the Finder." It also underpins Universal Clipboard and the peer-to-peer discovery those features rely on. The binary is at /usr/libexec/sharingd, and it's been around since OS X Yosemite.
Why it's using high CPU
- A failed or stuck AirDrop transfer: a documented case pinned
sharingdnear 100% after an AirDrop that never completed. - Flaky Wi-Fi or Bluetooth, or a VPN/router configuration, causing repeated BLE advertising and peer-to-peer Wi-Fi negotiation retries.
- A Handoff session stuck incomplete.
- In public with AirDrop set to "Everyone," repeated inbound attempts from strangers keep it busy.
Is sharingd a virus?
No. It's a legitimate first-party daemon in /usr/libexec. One nuance worth knowing: sustained activity while you're not using any sharing feature can mean unwanted inbound AirDrop attempts: a privacy annoyance, not malware.
What to do about it
- If you don't use AirDrop, turn off discovery. In Finder's AirDrop window (or Control Center), set "Allow me to be discovered by" to No One (or Contacts Only). This stops the constant scanning, and closes the public-AirDrop annoyance above.
- Toggle Wi-Fi and Bluetooth off and on to clear a wedged discovery loop.
- Toggle Handoff off at System Settings → General → AirDrop & Handoff to clear a stuck session.
- Restart to clear a wedged transfer. Often it settles on its own once the in-flight transfer times out; waiting is legitimate.
What people get wrong
sharingd is commonly confused with rapportd, which handles other Continuity plumbing (wake-over-network and instant-hotspot presence). They're separate daemons; blaming AirDrop CPU on rapportd, or vice versa, is a frequent mistake.
See it, and the privacy side
sharingd sitting busy while you're not sharing anything is exactly the kind of thing worth noticing. Plumby shows live CPU and network in your menu bar with the process named plainly, so a stuck AirDrop or unwanted inbound attempts are visible instead of a mystery, measured from your Mac's real state, with nothing about your machine leaving it.
