What is locationd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
locationd is the macOS Location Services daemon: it obtains the Mac's geographic location and manages which apps, daemons and widgets are allowed to receive location updates. It is busiest when apps or system services ask for your location. You can see and limit those requests in System Settings > Privacy & Security > Location Services.
locationd at a glance
| locationd | |
|---|---|
| Made by | Apple (part of macOS, Location Services) |
| Type | System daemon |
| Location | /usr/libexec/locationd |
| Runs as | _locationd (a system account) |
| Started by | launchd job com.apple.locationd |
| Can you quit it? | Not usefully. launchd restarts it if it exits unexpectedly, and apps lose location updates in the meantime. |
What is locationd?
The locationd(8) man page says locationd obtains geographic location and manages the authorization for apps, daemons and widgets that request location updates. Its partner CoreLocationAgent shows the permission prompts.
It runs as the _locationd system account through the launchd job com.apple.locationd. launchd keeps it alive (it is restarted if it exits with an error) and also starts it once a day. On the Mac checked here it was running.
Is locationd safe?
Yes. locationd is part of macOS at /usr/libexec/locationd, runs as its own system account and is signed by Apple.
Why does locationd use so much CPU and memory?
- Apps asking for location. Maps, Weather, Find My, websites in Safari and third-party apps can request location. Apps that ask continuously keep locationd working.
- System services. Services such as time zone setting, suggestions and significant locations use location. They are listed under System Services in the Location Services settings.
- Changing networks or moving. Moving to a new place or network is a reason for location to be worked out again.
- Many authorized clients. locationd keeps a record of each app and service that has asked for location, so its memory grows a little with the number of clients.
How much CPU is normal for locationd?
Typical: near 0% CPU, with short bursts when an app asks for your location.
A small arrow next to the Control Center icon in the menu bar means an app is using your location right now.
How do you stop locationd from using so much CPU?
- See which apps use location. Open System Settings > Privacy & Security > Location Services to see every app and widget that has asked for your location.
- Turn off location for apps that do not need it. Switch off apps in that list that have no reason to know where you are. An app asks again the next time it needs location.
- Review System Services. Click Details next to System Services at the bottom of the list to turn individual system uses of location on or off. Turn on Show location icon in Control Center when System Services request your location to see when they do.
- Turn Location Services off entirely. The main Location Services switch stops location for everything. macOS warns that this also stops you locating the Mac with Find My Mac.
When should you worry about locationd?
Look closer if locationd stays busy and the location arrow is always on. Find the app using location in the Location Services list and turn it off or update it.
A locationd outside /usr/libexec, or one not running as _locationd, would not be Apple's.
How do you check locationd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type locationd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every locationd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'locationd' | grep -v grep
How can Thrum help with locationd?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when locationd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about locationd
Can I stop locationd completely?
Turning off Location Services stops location requests, but locationd stays loaded because it also manages the authorization settings.
Does locationd send my location to Apple?
Apple's page on Location Services says that turning it off stops your Mac from sending its precise location to Apple. Details are in the Location Services settings.
Sources
- locationd(8) man page: run man locationd in Terminal
- Apple Support: Control access to the location of your Mac