Does my camera clock need to be set to UTC for GPX geotagging to work?

No — but you need to know the offset between your camera's clock and UTC and supply it to the tool. GPX track points are always timestamped in UTC; your camera's DateTimeOriginal is typically in local time (or UTC but drifted). Lightroom lets you set a tracklog time offset with a slider; ExifTool accepts it via -geosync in HH:MM:SS. The safest way to measure it: photograph your GPS unit's time display at the start of the shoot, then compare that image's DateTimeOriginal to the UTC time on screen. Even a 30-second drift moves you roughly 40–50 meters along a track at walking pace.

Can I use a GPX track from my phone to geotag DSLR or mirrorless photos?

Yes — that is the standard approach. Run a dedicated logging app in the background on your phone while you shoot with a separate camera. As long as your camera clock is within a few minutes of real time, the timestamp match is reliable. Errors appear when the phone's app pauses for power saving, the battery dies mid-shoot, or you cross time zones without updating the camera clock. Measure the offset once at the start of the day and you won't need to think about it again.

Which GPS logger apps export GPX files?

On iOS: Gaia GPS, Trails, and OsmAnd all export standard GPX. On Android: GPSLogger is purpose-built for background logging — it's lightweight and produces clean GPX with minimal battery impact; OsmAnd and Gaia also work well. Garmin handheld GPS units and watches export GPX directly or via Garmin Connect. The resulting .gpx file is standard XML and works with every tool in this guide.

ExifTool says 'No GPS track points found in time range' — what's wrong?

Almost always a clock offset. The DateTimeOriginal values in your photos don't overlap with the time range in the GPX file — typically because the camera was on local time and the track is in UTC. Calculate the difference and rerun with -geosync=+HH:MM:SS (positive if the camera was behind GPS time, negative if ahead). Add -v2 to the command for verbose output that shows exactly which timestamps are being compared and where the gap falls.

What if I forgot to record a track, or the track file is corrupted?

Without a track there are no timestamps to correlate against — the GPX method can't run. You have two fallbacks. If you remember roughly where you were, drop a manual pin in Lightroom's Map module or any EXIF editor. If you genuinely don't know, RetroTagr's AI can infer a likely location from the photo's visual content — landmarks, architecture, terrain — and propose it for you to review before any GPS is written. The geotagging photos without GPS guide covers that workflow in full.

How to Geotag Photos from a GPX Track

Sync a GPX tracklog to your photos in Lightroom or ExifTool, handle the camera-clock offset that trips most people, and what to do when there's no track.

GPX geotagging works on a simple idea: a GPS logger records your position every few seconds as a track, software matches each photo's timestamp against the nearest track point, and interpolates coordinates for every frame in between. The result is standard EXIF GPS written into each file — and every map, photo manager, or gallery that reads EXIF will show the right location with no further work.

In practice two things trip people up: forgetting to start the logger before the shoot begins, and not accounting for the gap between the camera's clock and GPS time. Both are easy to handle once you know about them.

TL;DR: Record a GPX track on your phone (Gaia GPS, OsmAnd, or GPSLogger for Android) while you shoot. In Lightroom Classic: Map > Tracklog > Load Tracklog, optionally set a time offset, then Auto-Tag Selected Photos. With ExifTool: exiftool -geotag track.gpx /photos/, adding -geosync for any clock offset. No track at all — old trip, forgotten logger, crashed app — see the geotagging without GPS guide for the AI fallback.

Step 0: record and export the GPX

GPX (GPS Exchange Format) is a standard XML format that every logger exports and every geotagging tool accepts. You don't need a dedicated device — a phone app running quietly in the background is enough for most shoots.

iOS: Gaia GPS, Trails, and OsmAnd all export standard .gpx files.
Android: GPSLogger is purpose-built for background logging — it's lightweight, stays running across the full shoot, and produces clean GPX with low battery cost. Gaia GPS and OsmAnd are also reliable.
Dedicated GPS units: Garmin handhelds and sport watches export GPX via Garmin Connect or directly from the device's USB mass storage.

Start the logger before you take your first frame. A track that starts five minutes into the shoot leaves those early photos unmatched.

The clock-sync problem

GPX track points are timestamped in UTC. Your camera's DateTimeOriginal is almost certainly in local time — or in UTC but drifted by some number of seconds over time. Without accounting for this gap, the timestamp matching will either fail entirely or place photos in the wrong location.

The reliable fix is to photograph your GPS unit's time display (or a GPS-synced clock app on your phone) at the start of the shoot. After downloading, open that reference photo's EXIF DateTimeOriginal and compare it to the UTC time shown on screen. The difference, in seconds or HH:MM:SS, is the offset you'll feed to Lightroom or ExifTool below.

A 30-second drift moves a walking-pace subject roughly 50 meters along the track — visible on a map. It's worth measuring.

Method 1 — Lightroom Classic Map module

Lightroom Classic has first-class GPX support built directly into the Map module. It shows the matched track on screen before you commit, handles the time-zone offset interactively, and writes coordinates back to the original files through the standard Save Metadata command.

Switch to the Map module in Lightroom Classic.
Choose Map > Tracklog > Load Tracklog and select your .gpx file. The track appears as a colored line on the map.
If your camera clock was off, choose Map > Tracklog > Set Tracklog Time Offset before the next step. Enter the offset in HH:mm format — for example, +02:00 if your camera was two hours behind UTC.
In the filmstrip, select the photos whose capture times fall within the track's time range.
Choose Map > Tracklog > Auto-Tag Selected Photos. Lightroom interpolates each photo's position between the nearest two track points and drops a pin on the map.
Review the pins. If any photo landed on the wrong road or in the wrong city, you can drag it manually. When everything looks right, run Metadata > Save Metadata to Files (⌘S / Ctrl+S) to write the GPS coordinates from the catalog into the actual image files.

This is the natural path if Lightroom Classic is already your editing workflow. The map preview before committing is valuable — mismatched photos show up visually rather than silently.

Method 2 — ExifTool, for any software stack

ExifTool works independently of any photo manager. It reads the GPX file, reads DateTimeOriginal from each image, finds the nearest track point in time, and writes the standard GPS EXIF tags in place. Because it's command-line, it works on any operating system and is scriptable across any directory structure.

Basic command — process an entire folder:

exiftool -geotag track.gpx /path/to/photos/

If the camera clock was off, add -geosync with the offset. Positive means the camera was behind GPS time (common when the camera was on local time and GPS is UTC):

exiftool -geosync=+02:00:00 -geotag track.gpx /path/to/photos/

To process multiple GPX files at once — useful for multi-day trips with one file per day:

exiftool -geotag "day1.gpx" -geotag "day2.gpx" /path/to/photos/

Verify a single photo after tagging:

exiftool -GPS:all photo.jpg

You should see GPS Latitude, GPS Longitude, GPS Latitude Ref, and GPS Longitude Ref with values that match the route.

If ExifTool reports Warning: No GPS track points found in time range, the timestamps don't overlap — almost always the UTC-vs-local-time gap described above. Add -v2 to print verbose matching output showing exactly which timestamps are being compared and where the gap falls. ExifTool backs up originals by default (suffixed _original); once you've verified a sample, rerun with -overwrite_original to skip the backups.

Method 3 — Other tools

A few alternatives worth knowing about:

digiKam (free, cross-platform) — open source photo manager with a GPX correlation panel and an interactive time-offset slider. Good option if you want the map-preview workflow without a Creative Cloud subscription.
HoudahGeo (macOS, paid) — dedicated geotagging tool with Lightroom integration and support for mixing multiple GPS sources and correcting per-camera clock drift across a group shoot.
gpscorrelate (Linux, free CLI) — minimal, focused on GPX-to-EXIF correlation with no photo management layer on top.

For most photographers, Lightroom or ExifTool covers the job. The others matter when the situation is more complex: multiple cameras with independent clock drift, GPS tracks from several sources, or a Linux-only pipeline.

What if there's no track at all?

The GPX method only works if a track was recorded. That handles every future shoot once you build the habit. It doesn't help for:

Old trips where you weren't logging GPS
Camera rolls from a borrowed or secondhand camera
Sessions where the phone died or the app crashed before you exported

For those photos, there are no timestamps to correlate against. Two fallbacks:

Manual pin. If you remember roughly where you were, drop a pin in Lightroom's Map module or any EXIF editor. This works for "I know it was central Tokyo, near the Senso-ji" — not for "I have no idea."

AI inference. RetroTagr analyzes each photo's visual content — recognizable landmarks, architectural style, vegetation, terrain, road markings — and proposes a likely location. You review the suggestion on a map and confirm or adjust it before any GPS is written to the file. It's the specific tool for the case where there's genuinely no location information to start from. The geotagging photos without GPS guide covers the full workflow.

RetroTagr does not do GPX track correlation — it owns the gap the track-sync method can't reach.

Which method should you use?

Situation	Best fit
Lightroom Classic is already your editing app	Method 1 — Load Tracklog in the Map module
Not using Lightroom, or need to script it	Method 2 — ExifTool -geotag
Multi-day trip, one GPX file per day	ExifTool with stacked -geotag flags
Camera clock was significantly off	Either method with time offset / -geosync
No track recorded; remember where you were	Manual pin in Lightroom or an EXIF editor
No track recorded; location unknown	AI inference — see the without-GPS guide

Wrap-up

GPX geotagging is the highest-accuracy approach when you have the data: every photo gets an interpolated coordinate typically within a few meters of the real position. The two steps that most often break a first attempt — starting the logger before frame one, and correcting the camera-clock offset — become a natural part of the pre-shoot routine after the first time.

The hard limit is when no track exists. No software can correlate against data that was never recorded. Manual pinning covers what you remember; AI inference from visual content covers what you don't. The without-GPS guide handles that path in detail, and if you're weighing Lightroom's built-in map tools against a dedicated web workflow, the RetroTagr vs Lightroom comparison lays out where each one fits best.