How do I geotag photos with my Google Maps Timeline export?

Updated November 21, 2026 · By GeoStamp

Short answer: export your Timeline on your phone (you get a file called Timeline.json), then match each photo’s capture time against the positions in that file and write the result into the photo’s EXIF GPS tags. You can do the matching with a script and ExifTool, with a desktop geotagger after converting the Timeline to GPX, or in the browser with GeoStamp, which reads Timeline.json as it is.

Why this works

A camera without GPS still writes the moment of each shot into the file, in the EXIF tag DateTimeOriginal. Your phone, if Google Maps Timeline was on, kept a log of where it was through the day. Put the two side by side and every photo has a place: wherever the phone was at that moment. The only hard parts are getting the Timeline out of the phone, and making sure the camera’s clock and the phone’s clock agree.

How to export your Timeline

Since 2024 Google keeps Timeline on the device rather than in your account, so the export is made on the phone itself.

  1. Android. Open Settings > Location > Location services > Timeline > Export Timeline data. Pick a folder. The phone saves Timeline.json.
  2. iPhone. In the Google Maps app open Google Maps > your profile picture > Your timeline > the “…” menu > Location and privacy settings > Export Timeline data and save the file.
  3. Move the file to the computer where your photos are: email it to yourself, save it to a cloud drive, or copy it over a cable.

Google moves these menus from time to time. If yours look different, search the phone’s settings for “Timeline”. The export only contains what the phone recorded: if Timeline was off during the trip, there is nothing to match.

What is inside Timeline.json

The file has a list called semanticSegments. Each segment has a start and an end time and one kind of content. Shortened, with made-up coordinates:

Timeline.json
{ "semanticSegments": [
  { "startTime": "2025-06-14T15:00:00.000-07:00", "endTime": "2025-06-14T17:00:00.000-07:00",
    "timelinePath": [
      { "point": "36.0579°, -112.1431°", "time": "2025-06-14T15:41:00.000-07:00" },
      { "point": "36.0584°, -112.1402°", "time": "2025-06-14T15:44:00.000-07:00" } ] },
  { "startTime": "2025-06-14T17:05:12.000-07:00", "endTime": "2025-06-14T18:20:40.000-07:00",
    "visit": { "topCandidate": { "placeLocation": { "latLng": "36.0591°, -112.1093°" } } } },
  { "startTime": "2025-06-14T18:20:40.000-07:00", "endTime": "2025-06-14T18:52:03.000-07:00",
    "activity": { "start": { "latLng": "36.0591°, -112.1093°" }, "end": { "latLng": "35.9732°, -112.1267°" } } }
] }

Coordinates are text, like "36.0579°, -112.1431°". Some files have the degree sign damaged (°) or missing, and some write geo:36.0579,-112.1431. Times carry their UTC offset (-07:00 above), which tells you the time zone the phone was in.

The time zone and clock traps

This is where most attempts go wrong. The Timeline stores exact instants. A camera stores a wall-clock time with no zone: 2025:06:14 15:42:10 and nothing else. To compare them you must know which zone the camera clock was showing.

A simple check: find a photo you can place with certainty (a landmark, your hotel door), and see whether the position it gets is right. If it is off by a whole trip segment, the zone is wrong. If it is off by a little along your route, correct the clock by a few minutes. Next time, take one photo of your phone’s clock with the camera: the difference between what the picture shows and its capture time is your correction.

Interpolation and the max time gap

The phone does not record a position for every second. For a photo taken between two recorded points, the sensible estimate is the point in between, in proportion to the time: a photo taken one minute after a point and two minutes before the next is placed a third of the way along. For a photo taken during a visit, the place of the visit is the better answer.

What if the nearest recorded point is hours away, because the phone was off or had no battery? Then any position would be a guess. Set a limit, the max time gap, and leave photos beyond it without GPS. GeoStamp uses 30 minutes by default, lets you change it, and lists those photos in its report with the distance in time to the nearest point.

Do it in your browser

Add your Timeline.json and your JPEG photos. GeoStamp matches each photo by time, with time zone and clock correction, shows a preview with a Google Maps link per photo, and gives you a ZIP of copies with GPS in their EXIF plus a report. Nothing is uploaded. Free for the first 20 photos, $9 once for all.

Geotag my photos

Other ways to do it

FAQ

Does this work with RAW files?

GeoStamp writes GPS into JPEG only. For CR2, CR3, NEF, ARW or RAF use ExifTool, or geotag the JPEGs of a RAW + JPEG pair.

Will the old Google Takeout files work?

GeoStamp reads the on-device export Timeline.json. It does not read Records.json or the “Semantic Location History” folders from the old Takeout export.

Is the capture time in my photos changed?

No. The time zone and clock correction are used for the lookup only. DateTimeOriginal stays as the camera wrote it; the corrected moment is written, in UTC, as the GPS date and time.

Is anything uploaded?

No. The Timeline and the photos are read in your browser and the ZIP is built there.

Geotag my photos