GPX photo geotagging on iPhone & iPad

Geotag camera photos with a GPX track—without a computer.

Import a GPX track, choose camera photos in Apple Photos, then match each capture time to the route. Correct the camera clock and approve only the locations that make sense.

Last updated

Interactive example

Camera clock offset

0 min
−30 min0+30 min
Adjusted camera time: 10:07High confidence — track points are close in time.

The 30-second workflow

A route becomes a location timeline.

  1. Import a timestamped GPX fileLensPin reads track points, UTC times and segment boundaries locally.
  2. Choose the date range and cameraOnly matching camera photos without a location become candidates.
  3. Correct the camera clockApply a fixed offset before filtering and matching.
  4. Review the map and evidenceCheck route points, time gaps, continuity and source agreement.
  5. Save approved locationsUnselected or unsupported photos stay unchanged.

Do not have a track yet?

Record the outing or export it from a GPS watch.

The useful GPX is a recorded activity with timestamps—not simply a route you planned on a map.

START HERE

Choose a GPX source

Compare the quickest paths for iPhone, Apple Watch, Garmin, COROS, and Suunto.

How to get a GPX file →
PHONE OR WATCH

Record a new trip

Use Strava, OsmAnd, Gaia GPS, Guru Maps, WorkOutDoors, or an Apple Watch workout.

Recording instructions →
GPS WATCH

Export an existing activity

Download the recorded workout from Garmin Connect, the COROS app, or the Suunto app.

Watch export instructions →

GPX requirements

Use a timestamped track, not just a line on a map.

LensPin needs valid coordinates and time on GPX track points.

Segment breaks remain safety boundaries. For supported structure, troubleshooting and error messages, see the detailed GPX requirements.

How the suggested point is chosen

Interpolate inside a segment—never across a gap.

Continuous coverage

Between two route points

  • Confirm the surrounding points share a segment
  • Interpolate the coordinate by elapsed time
Gap or edge

Use caution or give no suggestion

  • Never bridge a segment break
  • Respect the point interval and track boundary
A line on a map is not enough.

LensPin checks timestamps and segment structure, not just drawn geometry.

Clock, time zone, and daylight saving

Why an entire batch can land in the wrong place.

Many cameras store local time without a time-zone offset, so travel or daylight-saving changes can shift a whole batch.

Camera clock correction

Apply the known difference only during scanning and matching.

Test a known photo first

Align one remembered place, then review the rest of the batch.

Use both sources together

Let an iPhone photo check the track.

A nearby iPhone photo can support the GPX point. If the sources disagree, LensPin downgrades the suggestion for review.

Within 100 m: supports the trackOver 300 m: conflictNo nearby iPhone photo: GPX stands alone

Your track is ready

Match it to the camera timeline.

The review screen keeps the route evidence attached to the photo instead of reducing the result to a pin.

See the surrounding track points

LensPin shows the points before and after the adjusted capture time, their interval, and whether they belong to one continuous segment.

Inspect gaps and track edges

If the photo falls outside coverage or beside a segment break, the detail view explains the boundary instead of hiding it.

Cross-check with iPhone photos

When both sources are enabled, agreement can support the GPX result and a large disagreement sends it to Review.

GPX parsing stays on the device, and the imported track is not retained after you restart the workflow.

GPX evidence review screenShow the route, surrounding track points, time gap and confidence state. 1290 × 2796 px or equivalent @3x.