What is findmydeviced on macOS?

Last updated: 2026-07-31

What it is

findmydeviced is the built-in macOS system daemon for Find My Mac. Its verified code-signing identifier and launchd label are com.apple.icloud.findmydeviced, and its executable is located at /usr/libexec/findmydeviced. It is supplied and signed by Apple rather than installed by a third-party application.

The daemon is started on demand by launchd. It maintains this Mac’s Find My registration and state and participates in the features used to locate the Mac, play a sound, remotely lock or erase it, and provide Activation Lock. It is not necessarily the only process involved. Apple has not published a complete boundary for this private daemon, and some parts of the offline Find My network may also be handled by system processes such as searchpartyd and locationd. A connection attributed to another process therefore does not prove that Find My is inactive, just as activity from findmydeviced does not describe the entire Find My system.

Why it talks to the network

findmydeviced needs network access because Find My Mac is tied to Apple’s iCloud and Find My services. It may register the device or refresh its state when Find My Mac is enabled, when you sign in to or change the Apple Account on the Mac, after a restart, or after a related configuration change.

Remote actions create another reason for activity. If someone requests the Mac’s location, asks it to play a sound, or sends a lock or erase command, the daemon can receive control messages through Apple Push Service. It can then exchange the state, location, or execution result required for that request with Apple’s services. This is event-driven activity and should not automatically be interpreted as a continuous upload.

When the Find My network is enabled, macOS can also exchange end-to-end encrypted offline-finding data. Discovery of nearby devices uses Bluetooth, which is not the same thing as an ordinary internet connection. Apple has not published the exact servers contacted, a standard contact frequency, or a complete account of which traffic belongs to findmydeviced rather than related processes such as searchpartyd. A domain list or fixed polling schedule would therefore go beyond the available evidence.

How much traffic is normal

Apple does not publish traffic measurements for findmydeviced, and there is no reliable general range that applies to every Mac. In particular, there is no verified number of megabytes per day or month that can be presented as a normal allowance.

When Find My Mac is enabled but idle, the usual qualitative pattern is no sustained throughput or only occasional small state and control requests. That is far less traffic than photo synchronization, iCloud Drive file transfers, or audio and video streaming. Initialization, a location request, or a remote action may cause a short-lived increase. The exact amount remains unverified and can vary with account events, restarts, configuration changes, and actual Find My use. A single brief burst is therefore more informative when viewed alongside its timing than when compared with an invented universal threshold.

Can you turn it off

The appropriate setting depends on which capabilities you want to retain. If you want locating, sound playback, remote locking or erasing, and Activation Lock for this Mac, Find My Mac needs to remain enabled. If you do not need those protections, Apple provides a System Settings switch rather than requiring you to terminate or modify the daemon.

In the newer System Settings layout, go to:

Apple menu > System Settings > [your name] > iCloud > Saved to iCloud: See All > Find My Mac > Turn Off

In the older layout, use:

Apple menu > System Settings > [your name] > iCloud > Find My Mac > Turn Off

Turning off Find My Mac means the Mac can no longer be located through Find My, instructed to play a sound, remotely locked, or remotely erased. It also removes Activation Lock.

The separate Find My network switch has a narrower effect. Turning off only that option stops offline finding and the Mac’s anonymous participation in helping locate nearby devices, while online finding can remain available. Turning off Location Services is also not equivalent to turning off Find My Mac: the Location Services setting and the Find My Mac enabled state are separate. To disable the service and remove Activation Lock, use the Find My Mac switch itself.

What people get wrong

• “findmydeviced is malware or a third-party monitoring tool.” It is neither. The executable is part of macOS, is signed by Apple, and is managed as an Apple system daemon.

• “It continuously uploads all of my activity and uses large amounts of data.” There is no evidence for that claim. Apple’s documentation describes the device, account, location, and service-use information needed to provide Find My. Apple does not publish a continuous transfer frequency or per-process traffic totals, so neither constant uploading nor a specific large volume can be inferred from the process name alone.

• “Force-quitting it in Activity Monitor, or deleting the executable, will disable it permanently.” launchd starts findmydeviced on demand, so the process may return after being terminated. The supported control is the Find My Mac setting in System Settings, not repeatedly killing the process or altering the system executable.

• “Turning off Find My network is the same as turning off Find My Mac.” These switches do different things. Find My network primarily controls offline, crowdsourced finding. Find My Mac controls the overall service for this Mac and is also the setting whose removal disables the remote features and removes Activation Lock.

• “Disabling Location Services completely disables Find My and Activation Lock.” Location Services and Find My Mac have separate enabled states. Turning off Location Services does not by itself establish that Find My Mac and Activation Lock have been turned off.

• “Apple can read the locations of both the lost device and the reporting device in offline finding.” Apple states that the offline Find My network uses end-to-end encryption. According to that design, Apple cannot see the location of the offline device or the device that reports it.

Seeing what it actually used

For a concrete answer on your own Mac, check findmydeviced in Bytetally’s per-process traffic view and compare its timestamps with restarts, account changes, location requests, or remote actions. Observe a longer idle period before deciding whether a short burst is unusual. Because Apple does not publish a universal traffic range, the Mac’s own process history is the useful next piece of evidence.

Related processes

Common questions