HeartbeatHocusFocusFilesMacHyperTile
Guide

locationd, the daemon that knows where your Mac is

The daemon behind Location Services on a Mac: how it fixes position from Wi-Fi alone, who it shares that position with, and what its own logs say all day.

By Chethan Kumar S N · Updated

Of every lowercase name in Activity Monitor, locationd is the one people take personally. A process that knows where you are sounds like an accusation. It is not an accusation, but the instinct is not wrong either: this is the one daemon on a Mac whose entire job is a fact about you, and it runs from boot to shutdown whether or not you have ever opened Maps. On the Mac measured for this page, a 10-core MacBook Pro running macOS 27.0.1 with 26 days of uptime, it has been running since boot as process 460, under a user account called _locationd that exists for nothing else, and it has spent 98 minutes and 43 seconds of processor time finding a place that never moved.

This page is built the way the other process pages in this series are built: from the daemon’s own manual entry, its own launch configuration, its own binary, and one full hour of its own logs, captured while nothing user-facing was happening. Everything was measured read only on one Mac. Every command used is at the end if you want to repeat any of it, and the log excerpts below are the daemon describing itself in its own words.

The 279-byte manual

The manual page for locationd is 279 bytes and dated November 10, 2016:

.Nd location services daemon
.Sh DESCRIPTION
.Nm
obtains geographic location and manages the authorization
for apps, daemons and widgets that request location updates.
.Sh SEE ALSO
.Xr CoreLocationAgent 8

Two jobs in one sentence: get the location, and decide who may have it. Everything the daemon does falls under one of those two halves. The see-also line points at its only colleague, CoreLocationAgent, whose own manual from July 2017 completes the pair: it manages the authorization prompts, and “is launched by locationd”. One daemon decides, one app asks you. That is the whole interface.

A user of its own, and a binary full of words

locationd does not run as root and it does not run as you. It runs as _locationd, user id 205, a reserved account that exists so the daemon can hold location data without holding anything else. Its working data lives in /var/db/locationd, a folder owned by that user with permissions drwx--x---: you can walk through it, you cannot read it, and neither can any app you run. On the Mac measured here the folder’s modification time was the current minute, meaning the daemon was writing to it while this page was being written.

The binary itself is /usr/libexec/locationd, 28,819,136 bytes, built for three architectures: x86_64, arm64e and arm64e.x1. It is the fattest daemon measured in this series, and it has the vocabulary to match. Where cfprefsd contains six strings in total, locationd contains 41,296. Reading them is like reading the source code of a phone. There is a complete Global Positioning System vocabulary, GNSS availability predictions, a GPS odometer log format with columns for latitude, longitude, horizontal uncertainty, altitude, vertical uncertainty, speed, course and the uncertainty of each. There are BeaconFence settings, coarse GPS modes, and a string for when “GPS dropped out for 0.000 seconds while warming”. A MacBook Pro has no GPS receiver. The code carries the whole instrument panel anyway, because the same daemon ships inside every iPhone.

How a Mac with no GPS knows where it is

The Mac answers the position question with the only radio that always works: Wi-Fi. Apple’s location page for the Mac states it in one line, and it is worth reading exactly as written: “Your Mac determines its location using information from local Wi-Fi networks.” The developer documentation for Core Location describes the full toolkit, “Wi-Fi, GPS, Bluetooth, magnetometer, barometer, and cellular hardware”, and the Mac simply uses the subset it has.

The daemon’s log shows the process at work, in its own compressed shorthand:

[com.apple.locationd.Position:WifiPosition] @WifiFlow, locreq, na,
  clientupdate, current, none
[com.apple.locationd.Position:GeneralCLX] WifiLoc, processScanResult,
  aps, 7, network, 1, tiles, 1, request, Request, type, clientupdate,
  lowPriority, no, requester, registrant

That second line is a Wi-Fi position fix being assembled: 7 access points heard, 1 network, 1 map tile of candidate locations fetched. The scan results from the Wi-Fi radio are matched against a database of where those access points are, and the answer falls out. No satellite was involved. In the hour measured here the daemon also logged 13 lines from its Motion subsystem about the gyroscope, because motion is part of the position story too: it is how the system knows the laptop moved, which is how a Significant Location gets a start and an end time.

The authorization gate

The second half of that 279-byte manual is the authorization half, and the log shows it as a function with an honest name: _CLDaemonGetAuthorizationStatusForAppWithAuditToken. Not for an app by name. For an app with an audit token, the kernel’s proof of exactly which signed binary is asking. When an app wants your location, locationd checks that token against its records, answers no, ask, or yes, and if the answer is ask, it launches CoreLocationAgent to put the prompt on your screen.

The system’s own clients are not exempt, and this is the part no settings screen shows you. They are listed in plain sight at /System/Library/LocationBundles, 21 entries, each one a system feature that receives location updates:

BundleWhat it is for
Routine.bundleSignificant Locations, the places you go
CountryTracker.bundleWhich country the Mac is in, for region features
TimeZone.bundleSetting the clock from location
WifiCalling.bundleWi-Fi calling region rules
IPTelephonyEmergency.bundleEmergency call location
DoNotDisturb.bundleThe until I leave this place setting
FMF.framework, FindMyDevice.frameworkFind My friends and devices
HomeKitDaemon.framework, HomeEnergyDaemon.frameworkHome automation
MapsAnnouncements.bundle, Milod.bundle, Wea.bundleMaps and weather

During the measured hour, four of these were actively asking: Routine, CountryTracker, TimeZone and WifiCalling, alongside the WirelessDiagnostics framework, which was the chattiest client of all with 46 position requests. Every one of them is visible in the log by bundle path, every one can be switched off in System Settings, and that list is under Privacy and Security, Location Services, scroll to the bottom, System Services, Details.

One quiet hour: 15,790 lines

For an hour with no location app open, no Maps, no weather widget touched, locationd wrote 15,790 log lines. That is the busiest daemon measured in this series, ahead of cfprefsd at 7,771 and twelve times distnoted. The breakdown says most of it has nothing to do with your apps:

Log subsystemLines in one hour
Position:Position5,651
Core:Geotagging5,622
icloud.SPFinder:advertisementCache1,548
Position:GeneralCLX532
Core:Client219
Utility:QA150
Position:WifiPosition113
xpc:connection15
Motion:Gyro13
Core:TZ, Position:Country, Core:Core72

The single biggest story inside those numbers is 3,724 lines mentioning Avenger advertisements. Avenger is the internal name for the Find My beacon traffic, and the loop reads like this, once every few seconds:

[com.apple.locationd.Core:Geotagging] onAvengerAdvertisementDetected:
  got avenger advertisement
[com.apple.locationd.Core:Geotagging] onAvengerAdvertisementDetected:
  advertisement is near-owner from other people and do not process it
[com.apple.icloud.SPFinder:advertisementCache] saveBeaconPayload: 1

That is the crowd-sourced Find My network from the inside: a nearby stranger’s AirTag or device broadcasting, this Mac’s bluetoothd hearing it, and locationd filing the observation for the owner to find later, after noting that this particular advertisement belonged to someone else. Your Mac is a passive node in a network that finds other people’s keys, and it logs each observation it declines to act on.

Two smaller honest details from the same hour. One of the daemon’s log strings contains a typo, “LocationSubcription”, that has presumably shipped for years. And the Routine client subscribes with a stated DesiredAccuracy of 100 metres, a number that tells you Significant Locations are not trying to pinpoint you, they are trying to know the neighbourhood. That Routine client is a daemon in its own right, routined, the student to locationd’s gatekeeper, and the routined page measured the other half of the handoff: the models that classify each visit, the schema of learned places, and the simulated phones behind every routined crash report.

The launch job

The daemon is started by launchd from /System/Library/LaunchDaemons/com.apple.locationd.plist, 1,005 bytes, and the configuration answers the questions people ask in forums directly:

SettingValueWhat it means
UserName / GroupName_locationdruns as its own reserved user, not root, not you
KeepAliveSuccessfulExit: falseif it exits successfully, do not restart it
RunAtLoadfalseloaded at boot, started on demand
StartInterval86400plus a daily nudge if nothing asked
ThrottleInterval3cannot be restarted more than once per 3 seconds
EnablePressuredExitfalsememory pressure cannot evict it
POSIXSpawnTypeAdaptivescheduler treats it as neither urgent nor batch

At runtime, launchctl reports one run since boot, never exited, and an immediate start reason of “semaphore”, which is this series’ first: every other daemon measured so far was woken by a Mach message. locationd was woken by a held flag, the kind of trigger you use when the wake-up must not be missed. The job vends seven Mach services, and their names are a map of the Mac-specific design: com.apple.locationd.desktop.agent, desktop.registration, desktop.spi and desktop.synchronous, plus com.apple.locationd.routine, com.apple.locationd.simulation and a StatusKit client. The desktop family does not exist on an iPhone. It is the API surface a Mac uses to talk to the same daemon.

The job also carries two calendars. One event, a metrics heartbeat, fires every 14,400 seconds, four hours. The other is the strangest schedule measured in this series: com.apple.locationd.CLClientManager.usersrecencycheck, an activity that repeats every 16,070,400 seconds. That is 186 days. Somewhere in the daemon’s year there is one check, twice a year, asking whether the list of clients who have recently used location still matches the list it remembers.

The near-name family, including one red herring

Activity Monitor and the man pages mix several processes into this story. The family tree, measured live on one Mac:

And the red herring: locate. There is a second launch job on every Mac called com.apple.locate, which runs locate.updatedb, the database builder for the classic locate filename search. It is Disabled by default, and would run at 3:15 in the morning on Saturdays. It has nothing to do with location services and everything to do with 1980s Unix. Searching for locationd and landing on locate man pages is a documented hazard of this topic.

What you can actually control

The switch panel is real, and it is the only one locationd respects. System Settings, then Privacy and Security, then Location Services. The master switch turns it off, and Apple’s page for that setting states the trade honestly: with it off, your precise location is not sent to Apple, though your IP address still implies a region, and emergency calls may still use location regardless. Below the master switch, every app has its own toggle, and below the app list, the System Services Details button reveals the system’s own location uses, the same cast listed in the table above, each switchable.

Two of those deserve their own words. Significant Locations keeps the places that matter to you, encrypted end to end in a way Apple says it cannot read, with a Details page that lists them and a Clear History button. And whenever anything is using location, an arrow appears next to Control Centre in the menu bar; click it and it names the app. On a healthy Mac that arrow is rare, the CPU cost is a rounding error, and the three rows in Activity Monitor are one daemon and two pretend phones. If you want to check any of this yourself, the commands follow.

The launch configuration, verbatim
$ plutil -p /System/Library/LaunchDaemons/com.apple.locationd.plist
{
  "EnablePressuredExit" => false
  "EnableTransactions" => true
  "GroupName" => "_locationd"
  "KeepAlive" => { "SuccessfulExit" => false }
  "Label" => "com.apple.locationd"
  "LaunchEvents" => {
    "com.apple.xpc.activity" => {
      "com.apple.locationd.CLClientManager.usersrecencycheck" => {
        "AllowBattery" => true
        "GracePeriod" => 86400
        "Interval" => 16070400
        "Priority" => "Maintenance"
        "Repeating" => true
      }
    }
  }
  "POSIXSpawnType" => "Adaptive"
  "RunAtLoad" => false
  "StartInterval" => 86400
  "ThrottleInterval" => 3
  "UserName" => "_locationd"
}
What launchctl knows about the running job
$ launchctl print system/com.apple.locationd
	state = running
	program = /usr/libexec/locationd
	username = _locationd
	minimum runtime = 3
	exit timeout = 5
	runs = 1
	pid = 460
	immediate reason = semaphore
	forks = 0
	execs = 1
	last exit code = (never exited)
Counting the daemon's hour yourself
$ log show --last 1h --predicate 'process == "locationd"' --style compact | wc -l
   15790

$ log show --last 1h --predicate 'process == "locationd"' --style compact \
  | grep -o "\[com\.apple\.[a-zA-Z.]*:[A-Za-z]*\]" | sort | uniq -c | sort -rn
The system's own location clients
$ ls /System/Library/LocationBundles
AppleCameraLocalization.bundle    IPTelephonyEmergency.bundle
CarbonAnalytics.bundle            MapsAnnouncements.bundle
CoreParsec.framework              Milod.bundle
CoreTelephony.framework           NetworkServiceProxy.framework
CountryTracker.bundle             Oos.bundle
DestinationdLocationBundleiOS.bundle   Routine.bundle
DeviceManagement.framework        TimeZone.bundle
DoNotDisturb.bundle               Wea.bundle
FMF.framework                     WifiCalling.bundle
FindMyDevice.framework
HomeEnergyDaemon.framework
HomeKitDaemon.framework
The manual pair, both pages in full

locationd.8, dated November 10, 2016: “obtains geographic location and manages the authorization for apps, daemons and widgets that request location updates.” CoreLocationAgent.8, dated July 6, 2017: “manages the authorization prompts for apps, daemons and widgets that use location services. Nm is launched by locationd.” Between the two of them, 631 bytes document the entire permission system of a Mac.

The commands

ps -A -o pid,user,time,rss,comm | grep locationd
man locationd
man CoreLocationAgent
plutil -p /System/Library/LaunchDaemons/com.apple.locationd.plist
launchctl print system/com.apple.locationd
ls -ld /var/db/locationd
ls /System/Library/LocationBundles
strings -a /usr/libexec/locationd | wc -l
log show --last 1h --predicate 'process == "locationd"' --style compact

Everything above was measured read only on one Mac, and the one thing the measurements cannot tell you is what Apple’s location database does with the access points it hears. For that, the privacy page is the only source: location is collected “in a manner that doesn’t personally identify you”, and the switch that stops it is in the same place it has always been, one screen below the one listing every process you were ever suspicious of.

Questions

What is locationd on Mac?

It is the location services daemon. Its own manual, unchanged since November 2016, says it obtains geographic location and manages the authorization for apps, daemons and widgets that request location updates. Every position fix on a Mac, every authorisation check, every Significant Locations visit and every Find My beacon observation passes through this one process. It runs as its own reserved system user, named _locationd, so it holds no privileges of yours. On the Mac measured here it used about 19 MB of memory and under four minutes of processor time a day.

Why are there two or three locationd processes in Activity Monitor?

Because each booted iPhone simulator runtime ships its own copy. There is one system wide daemon, running as the reserved _locationd user since boot, and if you develop iOS apps, every simulator runtime you have launched adds another locationd loaded from its RuntimeRoot inside the simulator volume. On the Mac measured here that made three rows: one system copy and two simulator copies, one each for the iOS 27.0 and 27.2 runtimes. All of them are Apple's binary. None of them is watching the real Mac; the simulator copies serve the simulated phones.

Is locationd tracking me?

It is the gatekeeper, not the stalker. Nothing gets a position without passing its authorization check, which is keyed to the audit token of the asking process, and the list of who is allowed lives in System Settings under Privacy and Security, then Location Services, where every app and every system service can be switched off individually. Apple's own location page for the Mac never names locationd at all, but it does say that Significant Locations are encrypted and cannot be read by Apple, and that an arrow by the Control Centre icon appears whenever the location is in use. If you turn Location Services off entirely, the same page says your precise location is not sent to Apple.

Why is locationd using high CPU, and can I quit it?

Normally it barely works: about three minutes and forty six seconds of processor time per day on the Mac measured here, a quarter of one per cent of a single core. When it runs hot, the cause is almost always a client asking for fixes in a loop, and the daemon's own log names every client by bundle path, so the loop is findable with one log command. The loudest activity on a quiet Mac is not your apps at all but Find My beacon harvesting, which logged over three thousand seven hundred lines in the hour measured here. There is no supported way to disable the daemon; the real switch is Location Services in Privacy and Security.

What is the difference between locationd, CoreLocationAgent and locate?

Three names, three jobs. locationd is the system daemon that fixes position and checks permission. CoreLocationAgent is the little app that draws the permission prompt, and its manual says plainly that it is launched by locationd. And locate is not related at all: it is the classic Unix filename search tool, whose database builder job is present on every Mac but disabled by default, scheduled for Saturday mornings. People who search for locationd and find locate man pages are reading about the wrong thing entirely.

Ready? Buy Ribbon for $15, or read all the guides.