# searchpartyd, the search party your Mac silently joins

> searchpartyd is the daemon behind Find My offline finding, the crowd of Apple devices that locates lost Macs and AirTags. Measured on a real Mac: 59 MB of code, a minute and a half a day.

Source: https://www.ribbonmac.com/guides/searchpartyd-mac · Updated 2026-11-16

Every daemon in this series gets measured by the same ruler. Processor time, memory, the doors it opens, the words in its manual. searchpartyd breaks the ruler twice before lunch. It is the fattest binary measured so far, 59,192,000 bytes, three and a half times the size of sharingd. It is also the chattiest, 177,253 log lines in a single day, eight times the previous record. And it is the only daemon in the series whose name is also a complete explanation of its job. A search party is a crowd that spreads out to look for something lost. This is the daemon that puts your Mac in one.

## The manual says almost nothing, and means it

macOS ships searchpartyd with a real manual page, dated 1/11/14, and it deserves to be quoted because it may be the most honest paragraph in the series. The name line reads "searchpartyd, searchparty daemon". Then the description, in full:

> searchpartyd is a daemon.
>
> There are no configuration options to searchpartyd. Users should not run it manually.

That is the entire entry. Most daemon manuals at least gesture at a purpose. This one, written the year Find My shipped in its modern form, says only that the thing exists. Everything else on this page comes from watching it work.

## What the name means

Apple never puts the word searchpartyd in front of a customer, but the feature it powers is one of the most famous on any Apple device. In Find My, a missing Mac, iPhone or AirTag that has no internet connection can still be located, because every other participating device is quietly looking for it. Apple's Platform Security guide describes the arrangement plainly: any device with offline finding turned on can act as a "finder device", meaning it "can detect the presence of another missing offline device using Bluetooth and then use its network connection to report an approximate location back to the owner."

That is the search party. Your Mac is in it right now. When the guide says "This entire interaction is end-to-end encrypted, anonymous, and designed to be battery and data efficient", that is a description of work this daemon does on your behalf, for strangers, continuously.

The same stack runs in both directions. Your Mac helps find other people's devices, and if it is ever the one left behind, it advertises itself and the crowd finds it. The log on the Mac measured here shows both halves: 39,607 lines in a day under the observation storing category, the listening half, and 5,141 under a category named meDevice, the half where this Mac reports its own presence.

## The keys that rotate

The clever part of offline finding, the reason it can be anonymous, is a rolling series of short lived keys. The security guide explains the construction: a private key pair and a secret generated on your device, never sent to Apple, synced only through iCloud Keychain. From that secret, a key derivation function produces a new symmetric key for each rotation window, and from that key, a new public key is computed each time. A missing device "begins periodically broadcasting the derived public key" in a Bluetooth payload, and "By using P-224, the public key representation can fit into a single Bluetooth payload." Finders relay what they hear. Only the owner, holding the original secret, can unwind the chain and recognise their own device. Nobody in the middle, Apple included, learns anything.

You do not have to take that on faith, because the machinery leaves fingerprints. The daemon's log shows it running its own SQLite database, and one of the tables has a name straight out of the paper: KeyGenerationBeaconKeys, indexed on beaconIdentifier. Its binary carries the protocol names for the accessory side of the pairing flow, AirTagPairingData among them, plus a Swift protocol for AirPods. And when accounts are removed, it logs exactly which keychain entries it deletes: an item sharing key, an observation key, a beacon store key, a standalone beacon database key. The rotation completing even has its own notification, visible in the launch configuration of the daemon's user side partner: localfindable.rotation-complete.

There is also a string in the binary, prefixed with an internal codename, that reads like an engineer's diary: "#Durian: Proceeding to unpair and remove pairing lock." Whatever Durian was inside Apple, its reset path shipped in every copy of this daemon.

## Measured on a real Mac

The numbers below were measured read only on a MacBook Pro with Apple silicon running macOS 27.0.1, 26.9 days after boot.

| Measurement | Value |
| --- | --- |
| Process ID, parent | 602, parent 1 (launchd) |
| User | root |
| Uptime | since boot, 26d 22h, never exited |
| Processor time | 39:55.64 total, about a minute and a half a day |
| Memory | 20,528 KB, falling to 16,000 KB between samples |
| Binary | /usr/libexec/searchpartyd, 59,192,000 bytes |
| Architectures | arm64e and arm64e.x1 only, no Intel slice |
| Code signature | com.apple.icloud.searchpartyd, platform identifier 26 |
| Strings in binary | 26,607 |
| Doors (Mach services) | 20 |

Three of those rows deserve a sentence each. The binary is the largest in this series by a wide margin, 59 MB of code for a daemon whose manual is 302 bytes, and the gap between those two numbers is roughly the size of the Find My feature. The memory figure falling between samples is the healthy pattern, not a leak: the launch job sets EnablePressuredExit, so the system reclaims memory whenever the daemon goes quiet. And 20 Mach services is a lot of doors, but they tell you what the daemon is: a beacon key service, an observation store, a pairing manager, a scanner monitor, a scheduler, and the rest of the vocabulary of a finding network.

## A quarter of a million log lines

One day of searchpartyd's log, counted and sorted:

| What it was doing | Lines in 24 hours |
| --- | --- |
| Storing observations | 39,607 |
| Its own SQLite database | 29,961 |
| XPC traffic to clients | 24,177 |
| Reporting this Mac as a device | 5,141 |
| Find My subsystem chatter | 5,572 |
| Network bookkeeping | 5,506 |
| CoreBluetooth management | 1,374 |
| Everything else | thousands more |

The single most common line, logged 26,826 times, is a reconciliation tick: ObservationStoring.Reconcile, every few seconds around the clock, folding what the radio heard into the database. The runner up is funnier. An error reading "No BeaconStoreActor available!" appears 12,741 times a day on a Mac that owns no Find My accessories, has none paired, and is working perfectly. Nothing is wrong. The daemon asks a component for a store, is told there is nothing to store, and writes it down anyway, several times an hour, forever.

The shape of the day matters more than the total. One hour produced 26,507 lines. Another produced 191, and one hour, 7 in the evening, produced zero, complete silence. That is what a scan window looks like from the inside: long quiet stretches punctuated by bursts of relayed observations, which is also why a glance at Activity Monitor at the wrong moment can make this daemon look busier than its monthly average suggests.

## Six processes, one feature

Find My is not one process, and the family resemblance causes real confusion in Activity Monitor. All six of these were running on the Mac measured here:

| Process | Runs as | Job |
| --- | --- | --- |
| searchpartyd | root | the beacon machinery, this page |
| searchpartyuseragent | you | your side of the conversation |
| findmydeviced | root | locating this Mac when asked |
| findmybeaconingd | root | advertising this Mac as findable |
| findmylocateagent | you | relaying locations for people and items |
| findmydevice-user-agent | you | the user half of findmydeviced |

The user side agent has run twice since boot, and its previous exit reason is the friendly one: idle memory reclaim. The root daemon has never exited. If you are trying to match a process you saw to a feature, the path column settles it, and remember that four of the six run as your user, not root.

## Why it shows up next to Bluetooth and battery

Because the radio is its workplace. The log categories above read like a CoreBluetooth client's to-do list, and the Bluetooth daemon itself carries a timer named after this process: com.apple.icloud.searchpartyd.SPBeaconManager.bluetoothd, an hourly Find My window, with a 30 minute grace period, allowed to run on battery and during Power Nap, at Utility priority. [The bluetoothd page](https://www.ribbonmac.com/guides/bluetoothd-mac) in this series documents that timer, and it is the honest answer to anyone who has watched a sleeping Mac's Bluetooth tick over in the middle of the night: your Mac periodically advertises itself as a findable beacon and listens for others, asleep or awake, plugged in or not.

None of this is expensive. A minute and a half of processor time a day is around a tenth of a percent of one core, and the beacon payloads are deliberately tiny, a single Bluetooth payload per key by design. But if you are tracing battery drain, the chain is real and worth knowing: Find My drives searchpartyd, which drives Bluetooth windows. [The battery page](https://www.ribbonmac.com/guides/why-is-my-mac-battery-draining-so-fast) covers how to read that honestly, including the location daemon's own habit of logging Find My beacon observations for other people's devices by the thousand.

## Apple never names it

The hedge at the end of every page in this series, verified again for this one: across the entire Find My User Guide for macOS 27, its table of contents, and the Find My section of the Platform Security guide, the word searchpartyd appears zero times. Apple documents the feature beautifully and never names the machinery. The user guide will tell you that "A device's location might not be found if more than 7 days have passed since its last location was sent to Apple", which is the crowd-sourced system showing you its edge, and it will walk you through Lost Mode and alerts for devices left behind, all without once mentioning the daemon doing the work. That is a deliberate choice, and mostly a fine one. You do not need to know the name of the search party. You just need to know that when your device is the one lost, a few hundred million strangers have already agreed to look for it.

- [What Is bluetoothd on Mac?](https://www.ribbonmac.com/guides/bluetoothd-mac), the radio this daemon works through, and the page that documents the hourly Find My timer from the other side
- [What Is locationd on Mac?](https://www.ribbonmac.com/guides/locationd-mac), the other daemon whose log fills with Find My beacon observations
- [What Is sharingd on Mac?](https://www.ribbonmac.com/guides/sharingd-mac), the neighbour-facing counterpart, where AirDrop and Handoff live
- [Why is my Mac battery draining so fast?](https://www.ribbonmac.com/guides/why-is-my-mac-battery-draining-so-fast), for reading power use honestly before blaming any single daemon

## FAQ

### What is searchpartyd on Mac?

It is the daemon that runs Find My offline finding, the system where every Mac, iPhone and iPad signed in to Find My quietly listens for other people's lost devices. Its name is the explanation: the search party is the crowd of participating devices, and this root process at /usr/libexec/searchpartyd is the part of it that lives on your Mac. Apple's security documentation describes exactly what it does, detecting a missing offline device over Bluetooth and reporting an approximate location back to the owner, end to end encrypted and anonymous. On the Mac measured here it costs about a minute and a half of processor time a day.

### Why is searchpartyd using so much CPU?

On the Mac measured here, it was not: 39 minutes and 55 seconds of processor time across 26.9 days of uptime, roughly a minute and a half a day, a tenth of one percent of a single core. The work comes in bursts. Its log ranged from 191 lines in the quietest measured hour to 26,507 in the busiest, a 138 fold swing, and the peaks line up with Bluetooth scanning windows. If Activity Monitor shows searchpartyd genuinely pegged for a sustained period, treat it as a symptom: something is driving constant beacon activity, usually a flood of nearby Find My devices or a Bluetooth radio in a bad state, and the daemon's own log names which category is busy.

### Is searchpartyd tracking me, or is it a virus?

Neither, and the direction of the privacy story is the opposite of what the name suggests. It is platform signed Apple code, the class of signature reserved for the operating system's own files, running from the read only system volume. The beacon traffic it handles cannot be read by Apple or by the strangers whose devices relay yours: the security guide says the whole interaction is end to end encrypted and anonymous, and the rotating keys are generated on your devices and synced through iCloud Keychain, never sent to Apple as plaintext. This same stack is also what powers the alert that tells you an unknown accessory is travelling with you.

### Why is searchpartyd connected to Bluetooth?

Because Bluetooth is how offline finding works. A missing device with no internet connection broadcasts short lived public keys in a Bluetooth payload, and surrounding devices, including yours, pick them up and report an approximate location over their own network connection. That makes searchpartyd a CoreBluetooth client, and its log shows the categories you would expect: peripheral management, a central manager, an advertisement cache. The Bluetooth daemon's own timers include one named after this process, an hourly Find My beacon window that is allowed to run on battery and during Power Nap. The details are on the bluetoothd page of this series.

### Can I quit or disable searchpartyd?

There is no supported way, and no reason to want one. Its manual says there are no configuration options and users should not run it manually, there is no row for it in System Settings, and its memory is already reclaimed on demand through pressured exit, which is why its footprint fell from 20 MB to 16 MB between two measurements on an idle Mac. The one real switch is the feature, not the daemon: sign out of Find My Mac in your Apple Account settings and the beacon machinery has nothing to do. That also means nobody, including you, can locate this Mac when it goes missing, which is a genuine trade-off to weigh rather than a free win.
