My camera has no GPS. How do I add the location to each photo?
“My camera has no GPS. I have thousands of trip photos and my Google Maps Timeline export (Timeline.json). How do I add the location to each photo?” GeoStamp does exactly that. Drop your Timeline.json and your JPEGs: it matches each photo to where your phone was at that moment and writes the GPS latitude and longitude into the photo’s EXIF, on copies, right in your browser.
- Nothing uploaded, no Google login
- No Python, no ExifTool, no GPX conversion
- Works on copies: your originals are not changed
At a glance
What GeoStamp does and doesn’t do
- Works withThe Google Maps Timeline export
Timeline.jsonfrom Android or iPhone, plus JPEG photos from any camera. - WritesGPS latitude and longitude into each photo’s EXIF (with the GPS date and time), on copies. Your originals are not modified.
- HandlesCamera time zone, camera clock offset, interpolation between Timeline points, and a max time gap you choose (30 minutes by default).
- Runs onAny browser, on Windows, Mac, Linux or Chromebook. Nothing to install, no Python, no ExifTool.
- FreeThe first 20 photos of each run, with the preview and the report for all of them.
- Full$9 one-time. Every matched photo, any number of trips. No subscription.
- PrivacyYour photos and location history never leave your browser.
- Doesn’tHandle RAW files (CR2, CR3, NEF, ARW, RAF) or video in this version. It doesn’t invent a position when the Timeline has no data near that time. It doesn’t read the old Takeout format
Records.json. Not affiliated with Google.
- Google Photos
- Apple Photos
- Lightroom
- Windows Photos
- Immich
- Synology Photos
default max gap between a photo and a Timeline position; you can change it
How matching worksof your photos and location history sent to any server
How it worksphotos geotagged free per run, with the full preview and report
Try itonce, every photo, no subscription
PricingThe problem
Thousands of trip photos, and none of them knows where it was taken.
“My camera has no GPS. I have thousands of trip photos and my Google Maps Timeline export (Timeline.json). How do I add the location to each photo?”
The camera has no GPS
Most dedicated cameras record when a photo was taken, not where. In Google Photos, Apple Photos or Lightroom the whole trip shows up with no map.
Your phone knew where you were
Google Maps Timeline kept your positions all day. The on-device export gives you one file, Timeline.json, with points, visits and trips, each with its time.
Joining them is a script
The usual answers are Python scripts on GitHub, or converting the Timeline to GPX for ExifTool or Lightroom, and then fighting with time zones by hand.
How it works
Three steps. No Python, no ExifTool, no GPX conversion.
- Step 1
Export your Timeline on your phone
Android: Settings > Location > Location services > Timeline > Export Timeline data. iPhone: in Google Maps, Your timeline > … > Export. You get
Timeline.json. Step-by-step guide - Step 2
Add Timeline.json and your photos
Drop the file and your JPEGs (or a whole folder). Set the camera’s time zone and clock correction if the camera was not on local time. Nothing is uploaded.
- Step 3
Check the preview, download the ZIP
See each photo’s position and open it in Google Maps before anything is written. Then get a ZIP with the geotagged copies and a
report.csv, unmatched photos included.
Geotag
Add your Timeline.json and your photos
Everything runs on this page. Your photos and location history never leave your device.
Drop Timeline.json and your JPEG photos here
Together or one after the other. A folder of photos works too. Nothing is uploaded.
A photo is matched only when the Timeline has a position within the max time gap. When it has none, the photo is left untouched and listed in the report: no position is made up.
Free: GPS written into the first 20 photos per run, with the full preview and report. Unlock every photo for $9.
Standard metadata
Written where photo apps already look.
No sidecar files, no special tags. GeoStamp writes the same EXIF GPS fields a phone or a GPS camera writes, so galleries, maps and backup tools can read them.
- GPSLatitude, GPSLongitudeWith their N/S and E/W references, to a fraction of a meter. Taken from the visit, or interpolated between Timeline points.
- GPSDateStamp, GPSTimeStampThe moment used for the lookup, in UTC as EXIF defines them, after your time zone and clock correction.
- Everything else stays
DateTimeOriginal, camera and lens data, maker notes and the thumbnail are kept. The image data is copied byte for byte: nothing is re-compressed.
$ exiftool -DateTimeOriginal -GPSPosition -GPSDateTime DSC_0412.JPG
Date/Time Original : 2025:06:14 15:42:10
GPS Position : 36 deg 3' 28.44" N, 112 deg 8' 35.16" W
GPS Date/Time : 2025:06:14 22:42:10ZFile, Status, Time used (UTC), Latitude, Longitude, Method, Time gap (s)
DSC_0412.JPG, geotagged, 2025-06-14T22:42:10Z, 36.0579, -112.1431, interpolated, 95
DSC_0413.JPG, geotagged, 2025-06-14T22:44:02Z, 36.0591, -112.1093, visit, 0
DSC_0431.JPG, no match, 2025-06-15T03:05:40Z, , , , 4440What you get
The geotagging app people ask for, as a web page.
Until now this job meant a script from GitHub. GeoStamp does each part of it for you, on Windows or Mac, with nothing to install.
Reads Timeline.json directly
No conversion to GPX or KML first. It reads the timelinePath points, the visits, the trips and the raw signal positions of the on-device export.
Fixes time zone and camera clock
Uses the photo’s own UTC offset when it has one, otherwise the offset your Timeline had that day, or the one you pick. Plus a clock correction in days, hours, minutes and seconds.
Interpolates between points
A photo taken between two Timeline positions gets the point in between, in proportion to the time. A photo taken during a visit gets the place of the visit.
A max time gap you set
By default a photo needs a Timeline position within 30 minutes. If the phone recorded nothing that close, the photo is left alone. No position is invented.
Preview before anything is written
A table with each photo, the time used, the position, how it was found and an “open in Google Maps” link. Change an option and it updates at once.
Originals untouched, unmatched reported
GPS goes into copies, delivered as a ZIP. report.csv lists every photo: position, method, time gap, or the reason it got no match.
Compared
Three ways to geotag photos from a Timeline export.
The free routes are good tools and keep your files on your computer too. GeoStamp is for getting it done without scripts or conversions.
| Feature | GeoStamp | GitHub scripts + ExifTool | Desktop geotaggers that take GPX (Lightroom Classic, GeoSetter, digiKam) |
|---|---|---|---|
| What it is for | Geotagging JPEGs from a Timeline.json, start to finish | The same job, if you can run and adapt a script | Geotagging from a GPS track log, inside a photo manager |
| Cost | Free for 20 photos, $9 once for all | Free | GeoSetter and digiKam are free; Lightroom is a subscription |
| Reads Timeline.json directly | Yes | Depends on the script and the ExifTool version; many guides convert to GPX first | No: convert the Timeline to GPX first |
| Camera time zone and clock offset | Yes, with the Timeline’s own offset as default | Yes, as command-line options you work out | Yes, in a dialog |
| Interpolation and max time gap | Yes, gap configurable | Yes in ExifTool; varies by script | Yes |
| Preview before writing | Yes, with a Google Maps link per photo | Usually not | Yes, on a map |
| Report of photos with no match | Yes, report.csv with the reason | Console output, if any | Varies |
| RAW files and video | No: JPEG only | Yes, ExifTool writes most RAW formats | Yes, most of them |
| What you install | Nothing | Python and/or ExifTool | The application |
| Your original files | Only read; you get copies in a ZIP | Depends on the options you pass | Changed in place or in the catalog |
| Files leave your device | Never | Never | Never |
Pricing
Free for the first 20 photos. $9 once for all of them.
Start free
Free
Geotag the first 20 photos of each run and see the preview and report for all of them.
Geotag my photos- GPS written into the first 20 matched photos
- Preview and report.csv for every photo
- Time zone, clock correction, max gap
- No account
ONE-TIME
GeoStamp Full
one-time · every photo · any number of trips
Unlock every photo, $9- Every matched photo geotagged
- Thousands of photos per run
- Run it again on future trips
- No subscription
FAQ
Questions about geotagging photos from Google Maps Timeline
Want the long version? Read the guide.
Read the guideHow do I add GPS location to photos from a camera that has no GPS?
Use the location history of the phone you carried. Google Maps Timeline records where your phone was, with times. Export it on the phone (it saves a file called Timeline.json), then add that file and your JPEG photos to GeoStamp. For each photo it reads the capture time from the EXIF (DateTimeOriginal), looks up where the Timeline says you were at that moment, and writes that latitude and longitude into the EXIF of a copy of the photo. You get a ZIP with the geotagged copies and a report.
Which time zone does it use? My camera was set to home time.
A camera stores the capture time as a plain clock time with no time zone, while the Timeline uses exact instants. GeoStamp needs to know which zone the camera clock was showing. If a photo carries its own offset (the EXIF tag OffsetTimeOriginal, written by newer cameras), that is used. If not, the default is the UTC offset your Timeline had on that day, which is right when the camera showed local time at the place you were. If the camera stayed on home time during a trip, pick your home offset in “Camera time zone” (for example UTC-05:00). The preview updates at once, and each row opens in Google Maps so you can check a photo you remember.
My camera clock was a few minutes (or an hour) off. Can I correct it?
Yes. “Camera clock correction” adds or subtracts days, hours, minutes and seconds from every photo's capture time before the lookup. If the camera was 7 minutes behind, add 7 minutes. If you forgot daylight saving time, add or subtract 1 hour. A quick way to find the error: take a photo of your phone's clock with the camera and compare. The correction is used for the lookup only. The capture time stored in the photo is not changed.
What happens if my phone was off, in airplane mode or had no signal?
Then the Timeline has no position near that time, and GeoStamp does not make one up. A photo is matched only when the Timeline has a recorded position within the max time gap you choose (30 minutes by default). Photos with nothing that close are left out of the ZIP, untouched, and listed in report.csv with the reason, for example “the nearest Timeline position is 1 h 14 min away”. You can raise the gap if you were standing still, or lower it if you were moving fast.
How does it choose the position between two Timeline points?
If the photo was taken during a visit (a period the Timeline marks as staying at one place), it gets the location of that visit. Otherwise GeoStamp finds the recorded positions just before and just after the photo. When both are within the max time gap, it interpolates on a straight line between them, in proportion to the time. When only one is close enough, it uses that one. The report says which method each photo got (visit, interpolated, path, raw, activity) and how many seconds away the nearest recorded position was.
Does it work with RAW files (CR2, CR3, NEF, ARW, RAF) or video?
Not in this version. GeoStamp writes GPS into JPEG photos only. RAW files, HEIC and videos are listed in the report as “not a JPEG” and are left alone. If you shoot RAW + JPEG, you can geotag the JPEGs here. For RAW files, ExifTool can write GPS tags from the command line.
Are my photos or my location history uploaded anywhere?
No. Your Timeline.json and your photos are read by JavaScript on this page, on your device, and the ZIP is built there too. There is no upload step, no account and no Google login. The “open in Google Maps” links are plain links: a position is sent to Google only if you click one. The only other network requests are for the page itself, cookieless page analytics, and the payment check if you buy the full version, which sends a payment ID and never a file.
How do I export my Google Maps Timeline on Android?
Timeline is now stored on the phone, so the export is made on the phone. On Android open Settings > Location > Location services > Timeline > Export Timeline data. Choose where to save it. The result is one file, Timeline.json. Copy it to the computer where your photos are (email it to yourself, or save it to Drive or a USB cable), then add it here. Menu names change a little between Android versions: if you do not see it, search Settings for “Timeline”.
How do I export my Google Maps Timeline on 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. Google moves these menus from time to time. GeoStamp was tested with exports in the Android layout (a list called semanticSegments). The iPhone file uses a slightly different layout that GeoStamp also reads, but we had no real iPhone export to test with: if yours is not accepted, email support@cedanolabs.org and we will fix it.
Does it read the old Google Takeout Records.json? Do I need to convert to GPX?
No to both. You do not convert anything: GeoStamp reads Timeline.json directly, including its timelinePath points, visits, trips and raw signal positions. It does not read Records.json or the “Semantic Location History” folders from the old Google Takeout export. If you add one of those it tells you so.
Does it change my original photos? What exactly is written?
Your originals are only read. GeoStamp writes into copies and puts them in a ZIP. In each copy it adds the standard EXIF GPS tags: GPSLatitude, GPSLongitude and their N/S, E/W references, plus GPSDateStamp and GPSTimeStamp (the moment used for the lookup, in UTC). Everything else stays as it was: the capture time, camera and lens data, maker notes and thumbnail are kept, and the image data is copied byte for byte with no re-compression.
What if a photo already has GPS?
It is left alone and listed as “already has GPS”. If you want the Timeline position instead, tick “Overwrite GPS already in a photo”.
Do I need Python, ExifTool or the command line? Does it work on Windows and Mac?
Nothing is installed. It is a web page that runs in any current browser on Windows, Mac, Linux or a Chromebook. The scripts you find on GitHub for this job need Python or ExifTool and some editing. GeoStamp does the same job with a file picker.
How many photos can it handle?
Capture times are read from the first part of each file, so the preview of a few thousand photos is quick. The ZIP is built in the browser and holds up to 4 GB and 65,535 files per run. If your photos add up to more than that, run them in batches (a folder per day or per card). Photos that do not fit are listed in the report, never dropped silently.
How does the $9 full version work?
Free writes GPS into the first 20 matched photos of a run and shows the preview and the report for all of them. The full version is a single $9 payment, with no subscription and no account, and writes every matched photo, for any number of trips. It unlocks in the browser you pay from.
Put your trip photos on the map.
Add your Timeline.json and your JPEGs, check the preview, and download the copies with GPS in their EXIF. The first 20 photos are free.