LensPin
  1. LensPin
  2. Support

LensPin support

Find the reason, then the safest next step.

Choose the part of the workflow that is unclear: GPX import, iCloud assets, supported formats, matching, or location writeback.

Support topics

Start here.

How to get a timestamped GPX fileRecord with an iPhone or Apple Watch, or export an activity from Garmin, COROS, or Suunto. GPX requirements and import errorsTrack points, timestamps, segment breaks, invalid files, and coverage gaps. iCloud Photos and long scansDownloads, progress, background limits, storage, and resuming work. Location writeback and EXIF GPSPhotos-library location, optional non-destructive EXIF edit, skipped items, and verification. Supported formats and current limitsJPEG, HEIC, DNG/RAW, video, GPX, iOS versions, and fallback behavior. How matching worksSource priority, camera clock adjustment, review states, and safety checks.

Before reporting a problem

Keep the evidence that explains the run.

  1. Note the device, iOS version and cameraInclude the camera make and model shown in LensPin.
  2. Describe the evidence sourceSay whether the run used GPX, nearby iPhone photos, or both—and whether a clock offset was applied.
  3. Keep the completion counts or failure reasonAdded, failed, skipped, album warnings, and EXIF fallbacks describe different outcomes.
Protect private data.

Do not send a full photo library, private GPX route, or precise home coordinates when a filename, time gap, status label, and redacted screenshot are enough.