Pick photos directly or scan a period
Choose a specific batch from Apple Photos, or use shortcuts such as the last week, last month, previous month, or a custom date range.
A transparent matching workflow
LensPin starts with camera photos already in Apple Photos. It compares each capture time with a continuous GPX track, nearby geotagged iPhone photos, or both—then presents a location suggestion you can verify.
The complete flow
Inside the app
A trip may contain thousands of phone photos, several cameras, a wrong camera clock, or originals stored in iCloud. LensPin narrows the job before it starts matching.
Choose a specific batch from Apple Photos, or use shortcuts such as the last week, last month, previous month, or a custom date range.
LensPin reads EXIF make and model, groups eligible photos, and excludes screenshots, unknown-camera images, and photos that already have a location.
Apply a fixed camera-clock offset before filtering and matching. The original capture time and the time shown by Apple Photos are not rewritten.
A maximum anchor interval limits both GPX point spacing and the distance in time to nearby iPhone photos, so LensPin does not quietly widen the search.
How sources are used
When both sources are available, LensPin prefers continuous track evidence. Nearby iPhone photos can confirm the same area, reveal a conflict, or fill a period without continuous GPX coverage.
LensPin interpolates by capture time only within the same valid track segment. It never crosses a recorded segment break or an implausible jump.
Only photos LensPin can identify as Apple iPhone photos become anchors. Before-and-after anchors are stronger when they are close in both time and place.
Results that say what they know
The categories help you triage a batch. They are not claims of exact accuracy.
Evidence is close in time and internally consistent. These suggestions are selected by default, but still wait for confirmation.
The suggestion may rely on one-sided, sparse, distant, or partly conflicting evidence. Inspect the map and explanation before selecting it.
There is not enough safe evidence. LensPin shows track coverage or anchor gaps and leaves the photo unchanged.
LensPin uses points to compare evidence and choose safe defaults. A 92-point example does not mean a 92% chance that the suggested coordinate is correct.
After you confirm
LensPin adds a Photos-library location only to the items you approve. It reads each asset again immediately before the change, so a photo that gained a location elsewhere is skipped instead of overwritten.
Add GPS to the current non-destructive Photos edit when the format supports it. The original photo or RAW remains recoverable.
Added, skipped, failed, album warnings, and EXIF fallbacks are reported as different outcomes.
Successful updates appear together, with a map and coordinates you can inspect again after the batch is complete.
Ready to review the trip?
GPX and nearby iPhone photos lead to the same review-first workflow. For technical details, see location writeback and supported formats.