What is locationd on Mac, and why is it online?

Last updated: 2026-07-31

What it is

locationd is the built-in macOS daemon behind Location Services and the system backend for Core Location. The verified Apple binary is located at /usr/libexec/locationd and uses the code-signing identifier com.apple.locationd.

Its job is broader than finding a position for Maps. locationd obtains the Mac’s geographic location and manages location authorization for apps, other daemons, and widgets. Any authorized Core Location client can depend on it, as can several macOS system services.

Apple’s current Mac documentation says that a Mac determines its location using information about nearby Wi-Fi networks. Apple’s wider location architecture also uses a crowdsourced database containing Wi-Fi hotspot locations. That is the supported description for current Macs; statements about positioning hardware on other Apple devices should not be applied to a Mac without separate evidence.

Why it talks to the network

locationd may communicate with Apple’s location services infrastructure when an authorized app, website, or system service requests the Mac’s current location. Possible triggers include Maps, Weather, Find My, automatic time zone, Siri, Safari location suggestions, and system services such as Networking & Wireless.

These connections support location queries rather than general content downloads. Apple does not publish a fixed hostname or a complete endpoint list for locationd, so a connection should not be assigned to a particular service merely from an assumed domain. The process name alone also cannot reveal the contents of a particular request.

Apple says that devices with Location Services enabled may periodically send encrypted, non-personally identifying information about nearby Wi-Fi hotspots to its crowdsourced location database. However, it has not been verified that every category of such submission on current macOS is initiated directly by locationd. That distinction matters when interpreting process-level network records.

There is also an attribution boundary after a location has been delivered. If a third-party app obtains its position and then contacts that app’s own server, the resulting network activity belongs to the third-party app. It should not automatically be counted as traffic generated by locationd.

How much traffic is normal

There is no verified normal byte range for locationd, and Apple does not publish a traffic benchmark. No reliable public evidence supports claims that every request has a particular small size, so a specific KB or MB allowance would be misleading.

What can be said is qualitative. Connections are mainly associated with location requests or periodic system tasks, so the expected pattern is intermittent, low-throughput control and query traffic. It should normally be much smaller than traffic from video, audio, cloud synchronization, or software downloads.

That description is not a numeric threshold. A brief connection does not show how much information was exchanged, and an accumulated total cannot be judged from the process name alone. If locationd shows sustained high traffic, investigate which clients are requesting location and review the relevant system logs instead of assuming that the volume is normal.

Can you turn it off

Yes. The supported global control is:

Apple menu  > System Settings > Privacy & Security > Location Services > turn off “Location Services”

macOS also provides controls for individual apps and system services. These settings are preferable to trying to remove or repeatedly terminate the daemon.

Turning off Location Services prevents authorized apps, websites, and system services from obtaining the Mac’s position through macOS Location Services. Maps, Weather, Find My Mac, automatic time zone, and location-based suggestions may stop working or provide reduced functionality. Websites and apps may still estimate a broad region through other methods, such as the public IP address.

Apple specifically recommends leaving location access enabled for the Networking & Wireless system service. It uses location information to help the Mac follow regional Wi-Fi regulations and to improve the reliability of Wi-Fi, AirDrop, and AirPlay. Disabling Location Services is therefore possible and its general impact may be minor for some workflows, but it is not consequence-free.

What people get wrong

• “locationd is a virus or an advertising tracker.” The instance at /usr/libexec/locationd with the identifier com.apple.locationd is an Apple system component. A same-named executable found elsewhere is not established as the same component and should be checked separately.

• “It is only used by Maps.” Maps is one possible client. locationd serves authorized Core Location clients as well as multiple macOS system services, including features related to weather, Find My, time zone selection, suggestions, and networking.

• “locationd on a Mac gets its answer from built-in GPS.” Apple’s current Mac documentation specifically describes location determination through information about local Wi-Fi networks. Descriptions of GPS support on other Apple devices are not sufficient evidence for how a Mac is being located.

• “A locationd connection proves that macOS is continuously uploading my precise location.” A connection record alone does not establish what was sent, how precise it was, or whether the activity was an upload. Apple describes Location Services as responding to location requests and system-service needs, and says crowdsourced hotspot data is encrypted and non-personally identifying. The contents of an individual connection still cannot be inferred from the process name.

• “Force-quitting or deleting locationd is a good optimization.” locationd is managed by launchd and may restart when needed. The supported controls are the global Location Services switch and the per-app or per-system-service permissions in System Settings.

• “Disabling Location Services cannot affect networking.” Apple says the Networking & Wireless location service helps apply regional Wi-Fi rules and supports reliable operation of Wi-Fi, AirDrop, and AirPlay. Turning it off can therefore have effects beyond location-aware apps.

Seeing what it actually used

When the question is about volume rather than purpose, measure locationd over the period you care about instead of relying on a guessed normal range. Bytetally’s per-process statistics can show its recorded upload, download, and timing alongside other processes. If the traffic stays unusually high, use that timeline to identify when it began, then investigate the requesting clients and system logs.

Related processes

Common questions