IP geolocation vs device geolocation: what’s the difference?

IP geolocation infers location from the network path a request took, while device geolocation measures it from the device’s own sensors, which is why a VPN changes the first and not the second.

IP geolocation

Every request reaches a server from an IP address. Commercial databases map address ranges to places, using registry records, routing data and observations. The server looks up the address and gets a guess at where the request came from.

The guess is about where the traffic entered the internet, which is not always where the person is. Mobile carriers route traffic through regional gateways. Companies route through head offices. VPNs, proxies and iCloud Private Relay route through servers elsewhere by design, and many people use them for ordinary privacy reasons.

Even without any of that, accuracy falls off below country level. GeoComply, whose business includes IP intelligence, put it this way in a position paper for the IAB’s 2025 workshop on IP address geolocation:

Granularity of IP geolocation at anything beyond country level is 70% accurate at best, quickly declining to 50% at city level and beyond

Device geolocation

Device geolocation is measured on the device: satellite positioning, nearby Wi-Fi networks, cell towers, and on phones, motion and other sensors. A VPN does not move any of these. The browser Geolocation API and the location services on iOS and Android are device geolocation.

Device geolocation has its own weakness. Software on the device reports the readings, and software can be changed. Mock-location apps, emulators and modified builds can make a device report a place it is not. See device integrity checking for how vendors try to detect that, and device-attested location for signing the result in hardware.

Side by side

Last reviewed 19 October 2026