Outdoors with a clear sky, a phone is usually right to within about 5 meters. GPS.gov puts typical smartphone accuracy at a 4.9 m (16 ft) radius under open sky. Indoors, between tall buildings or under trees it gets worse, sometimes by hundreds of meters. Our GPS test shows the accuracy figure your device reports, live, so you can see which case you're in.
The 4.9 m figure comes from GPS.gov, which credits it to the Institute of Navigation. The same page adds that phone accuracy "worsens near buildings, bridges, and trees." Survey-grade gear does far better: GPS.gov cites FAA data showing high-quality single-frequency receivers at 1.82 m or better, 95% of the time. Your phone isn't one of those, and it doesn't need to be for maps.
GPS.gov lists the usual reasons a fix goes wrong:
It also makes a point that's easy to forget: often the GPS is fine and the map is wrong. A misplaced business pin or a missing road isn't a receiver fault.
When a browser hands over your location, it includes an accuracy value in meters. Picture a circle that size around the reported point. Under the current W3C Geolocation draft, that circle is a 68% confidence radius, one standard deviation. In plain terms, your real position is inside the circle about two times in three, and outside it the rest of the time. Earlier versions of the spec used 95%, so older articles may tell you otherwise.
The GPS test colors the reading so you can judge it at a glance:
| Accuracy shown | Color on the test | What it usually means |
|---|---|---|
| 10 m or less | Green | Satellite fix with a clear view of the sky |
| 11 to 50 m | Amber | Satellites partly blocked, or a fix still settling |
| 51 to 100 m | Red | Weak fix, or Wi-Fi positioning |
| Over 100 m | Red (Locate me also shows a "likely Wi-Fi/cell" hint) | Network positioning, no satellite lock yet |
The browser doesn't tell a page whether the fix came from satellites, Wi-Fi or cell towers. The size of the number is the best clue. A figure in the hundreds or thousands is almost always network positioning.
Satellite signals are weak by the time they reach the ground, and roofs and walls weaken them further. Indoors, your phone leans on nearby Wi-Fi networks and cell towers instead. That's quick, and good enough to find your city block, but it can be off by a few hundred meters.
A laptop or desktop usually has no GPS chip at all, so it relies on Wi-Fi. Don't expect a 10 m reading from a PC.
Our page asks for high accuracy on every request. The W3C spec calls that "a hint," though. The device can ignore it, for example in a battery saver mode that switches GPS off.
Two quirks to know. Heading and speed stay blank while you're standing still, because the API reports no heading when speed is zero. And the colored accuracy circle on the radar keeps the same size for any reading above 12 m, because the scale zooms out instead. Trust the number, not the circle size.
If the accuracy never drops below 50 m outdoors with a clear sky, after several minutes, something's limiting the phone. Check that battery saver or a low-accuracy location mode isn't on before you suspect the hardware.
The test shows latitude and longitude to six decimal places. That's far finer than the accuracy, so the last digits are mostly noise. Here's what each place is worth, computed with the same Earth radius the test uses (6,371 km):
| Decimal places | North-south step | East-west step at 40° latitude |
|---|---|---|
| 2 | 1.1 km | 850 m |
| 3 | 111 m | 85 m |
| 4 | 11 m | 8.5 m |
| 5 | 1.1 m | 0.85 m |
| 6 | 11 cm | 8.5 cm |
East-west steps shrink as you move away from the equator, because lines of longitude converge. For sharing a meeting spot, five decimals is plenty. Four gets you to the right building.
The spec defines three error codes. Our page turns each into a plain message, but here's what's behind them:
| Code | Name in the spec | What happened | What to do |
|---|---|---|---|
| 1 | PERMISSION_DENIED | You, or a setting, refused location access | Allow location for the site and for the browser app, then reload |
| 2 | POSITION_UNAVAILABLE | The device couldn't get any fix | Turn on system location, move to a window or outside |
| 3 | TIMEOUT | No fix arrived in time (20 seconds for Locate me) | Try again under open sky, or use Watch mode |
For code 1, there are usually two switches: one in the browser (the lock or site-settings icon by the address bar) and one in the phone's own settings. On an iPhone, the second is under Settings > Privacy & Security > Location Services. Both have to allow it.
Location uses a lot of power, so it's worth checking the battery test too if your phone runs flat fast while navigating. Our battery health guide explains what to look for. The accelerometer test covers the motion sensor that apps use alongside GPS.
Usually within about 5 meters outdoors. GPS.gov says GPS-enabled smartphones are typically accurate to within a 4.9 m (16 ft) radius under open sky, and that accuracy gets worse near buildings, bridges and trees.
It's the radius of a circle around the reported point. Under the current W3C Geolocation draft it's a 68% confidence radius, so your real position falls inside the circle about two times in three.
Indoors the phone usually can't see GPS satellites, so it estimates your position from Wi-Fi networks and cell towers. That's often off by a few hundred meters. Go outside and wait a minute or two for a satellite fix.
Most laptops and desktops don't. They locate you from nearby Wi-Fi networks, so the accuracy figure is usually tens or hundreds of meters. That's normal for a computer and doesn't mean anything is broken.
Both are empty while you're standing still, because there's no direction of travel to report. Some devices don't report them at all. Walk at a steady pace outdoors and, if your device supports them, they should appear.