--- title: "locationd: what it is, why it uses the network, and whether to block it · Kilobat" url: "https://kilobat.app/processes/locationd" description: "locationd runs Location Services on a Mac for the apps you allow. What its traffic is, how to limit it in Privacy & Security, and what breaks if you block it." --- Security and accounts # What is locationd? `locationd` runs Location Services. It finds where the Mac is for apps and features that you allowed, and it manages those permissions. Process: `locationd` · Made by Apple · Applies to: macOS 14 Sonoma and later. Checked on macOS 27.2. · Checked: 1 November 2026 ## Short answer Part of macOS. It runs Location Services, finding where the Mac is for the apps you allowed. Block with care Blocking it can stop apps and features from getting your location. To control it, use Location Services in Privacy & Security. Path `/usr/libexec/locationd` launchd label `com.apple.locationd` Signing identifier `com.apple.locationd` ## What it is The man page says that `locationd` “obtains geographic location and manages the authorization” for apps, daemons and widgets. The program is `/usr/libexec/locationd`. launchd starts it for the system as `com.apple.locationd`. Apple's guide says that turning off Location Services stops apps and websites from using your location through it. ## Why it uses the network - **Location requests.** When an app with permission asks where the Mac is, `locationd` helps determine its location. Apple says the Mac uses information from local Wi-Fi networks. - **System services.** Apple's guide lists system services that use your location under Location Services › System Services › Details. ## How much is normal When apps with permission ask for your location, small traffic is usual. With Location Services off, it shouldn't need the network for location. Kilobat needs Location permission to read Wi-Fi names, because macOS treats Wi-Fi names as location data. ## When it uses a lot, and why - **Not documented as heavy.** Apple doesn't document how `locationd` finds the location, so this page doesn't describe its traffic in detail. Large traffic isn't expected. ## Is it safe to block? Block with care Blocking it can stop apps and features from getting your location. To control it, use Location Services in Privacy & Security. What breaks if you block it - Apps that you allowed may not get your location, or get it less accurately. - Find My Mac may not show where the Mac is. - System services listed under Location Services › System Services may lose your location. Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it. ## Reduce its use 1. Choose Apple menu › System Settings › Privacy & Security › Location Services. 2. Turn off the apps that don't need your location. Or turn Location Services off. 3. Scroll to the bottom of the list, then click Details next to System Services. Turn off the services that you don't want to use your location. 4. Find My Mac needs Location Services. Keep it on if you use Find My. 5. Don't quit `locationd` in Activity Monitor. macOS starts it again. ## See how much it uses 1. Open Activity Monitor from Applications › Utilities. Click Network. 2. Type `locationd` in the search field. The Sent Bytes and Rcvd Bytes columns show what it moved since it started. 3. In Terminal, watch only this process. Press d to show the change per second, and q to quit. ``` nettop -p 'locationd' -P ``` ## With Kilobat 1. In the Kilobat app list, search for `locationd`. Its row shows the live rate and what it moved today. 2. In Connections, click the ⓘ button on one of its rows. The popover shows this page’s short answer, without going online. 3. In Terminal, ask the same question. Add `--json` for scripts and agents. ``` kilobat explain 'locationd' ``` 4. Show its traffic over one day. ``` kilobat bandwidth 'locationd' day ``` 5. Through MCP, an AI agent asks `explain_connection` with the process name. It gets the same facts. The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data). ## What isn’t documented Apple doesn't document how a Mac determines its location, or which servers `locationd` contacts. ## Questions **Does Apple get my location?** Apple's guide says that with Location Services off, your precise location isn't sent to Apple. Apple may still use your IP address to approximate a region for search suggestions. **Why does Kilobat ask for Location permission?** macOS shows Wi-Fi network names only to apps with Location permission. Kilobat uses it for Wi-Fi names and scans, and your location stays on the Mac. ## Sources - locationd(8), man page installed with macOS 27.2 - launchd property list com.apple.locationd, macOS 27.2 - [Apple Support: Control access to the location of your Mac](https://support.apple.com/guide/mac-help/allow-apps-to-see-the-location-of-your-mac-mh35873/mac) Checked on 1 November 2026. ## Related - [findmydeviced](https://kilobat.app/processes/findmydeviced): Part of macOS. findmydeviced runs Find My Mac. searchpartyd is another Find My daemon that Apple doesn't describe in its man page. - [airportd](https://kilobat.app/processes/airportd): Part of macOS. airportd manages the Wi-Fi interface, and WiFiAgent does Wi-Fi tasks for it in your session. They run Wi-Fi itself, not internet traffic.