How Much Data Does Google Maps Use?

Google Maps navigation uses roughly 5–15 MB per hour. A full day of driving with the route running the whole time is somewhere around 50–150 MB, so a week of finding your way around a foreign city sits comfortably inside a quarter of a gigabyte.

That is small enough that navigation is almost never the reason an allowance runs out. What people are actually remembering when they blame Maps is usually satellite view, Street View, or an afternoon spent scrolling restaurant photos — those cost several times more, and they are the parts worth knowing about.

Once a route is calculated, the phone has most of what it needs. The map tiles along the route are fetched in a block and then cached, and your position comes from GPS rather than from the network: GPS satellites transmit one-way signals and the phone only listens, which is why a downloaded map still tracks you in airplane mode. The ongoing traffic in both directions is small: periodic traffic updates going one way and position reports going the other.

The expensive moments are the ones where Maps has to fetch something new rather than reuse what it already has:

• Starting a new route, which pulls the corridor of tiles around it in one go.
• Re-routing after a wrong turn or a road closure, which does the same thing again for the new corridor.
• Panning and zooming around an area you have not looked at yet — every new view is fresh tiles, and idly exploring a city map runs a little higher than following a route through it.

Everything above assumes the standard vector map. The other layers are photographs, and photographs are a different order of cost:

• Satellite view: roughly three to five times the standard map for the same amount of panning, because each tile is an image rather than a set of lines and labels.
• Street View: the heaviest thing in the app. Each panorama you load is a few megabytes, so ten minutes of walking a street virtually can cost more than an hour of actually navigating it.
• The Explore and place tabs: photo grids of restaurants and hotels, which behave like any other image feed. This is where a "quick look for somewhere to eat" turns into tens of megabytes.
• Live traffic on a long drive: continuous but modest, and worth every megabyte it costs.

If you want one habit to change, it is leaving satellite view on as your default. Switching back to the standard map removes most of the difference and loses you nothing while navigating.

Offline maps are worth setting up, though not for the reason they are usually recommended. Over wifi, before you leave:

1. 1Open Google Maps and tap your profile picture.
2. 2Choose Offline maps, then Select your own map — Google’s steps are the same on both platforms.
3. 3Frame the area you want — a city and its airport is a sensible box — and tap Download.

A city-sized area is typically 50–150 MB, and a whole metropolitan region can pass 300 MB. Google says an area nearing expiry updates itself automatically when you are on wifi, so download what you need before you leave and the refresh has usually already happened by the time you land.

They are a real map with real driving directions, not a full copy of the app. Offline, you lose:

• Transit, cycling and walking directions. Driving directions are the only mode that works offline.
• Live traffic, and therefore any re-routing around a jam.
• Place photos, reviews and busy-times information, which are all fetched on demand.

For a city trip where you mostly walk and take the metro, that is a significant gap — which is another way of saying the offline map is a backstop rather than a plan. Keep some data available and let the app use it.

Navigation is not the thing to optimise. Video, social feeds and background photo backup decide how big a plan you need — and backup will happily run on mobile data when there is no wifi, which the backup settings in Google Photos control. A realistic estimate takes about a minute to do properly. Then compare plans by destination on price per GB, rather than buying an extra few gigabytes to cover a map that was never going to need them.