Find where your travel photos were taken

Before reverse image search or guessing from palm trees, ask: do I still have the original file? Phone gallery 'details' panels and desktop inspectors reveal GPS IFD tags when location was enabled at shutter time. One batch pass across a vacation folder maps eighty percent of favorites if you preserved originals.

Edited exports—Instagram saves, cropped Stories, Lightroom 'export for web'—usually strip GPS even when the edit looks mild. The workflow splits: originals get EXIF parsing; derivatives get visual or AI fallback. Mixing the paths wastes time running AI on files that still have coordinates in the camera-roll parent.

whereisthis.place reads metadata client-side in the browser. Vacation photos never need to upload to a server for a latitude-longitude read—important when albums include hotel rooms, kids, and license plates you do not want on third-party disks.

Treat EXIF GPS as device-reported, not courtroom-grade. Wrong pins happen indoors with stale fixes. Always glance at the map thumbnail: does terrain match the photo? A Mediterranean cliff labeled as Kansas means bad metadata, not bad software.

Settings → Privacy & Security → Location Services: ON globally. Then Camera → Allow Location Access → While Using the App. 'While Using' embeds GPS on stills and videos; 'Never' guarantees future mysteries.

Photos app respects embedded location for map albums when 'Significant Locations' and system location are on. For privacy after the trip, strip location before public posts—not before you archive originals for yourself.

iCloud Photos 'Download and Keep Originals' matters. Optimize iPhone Storage evicts full HEIC files and may leave you with thumbnails lacking full EXIF on offline devices. Before a long trip, confirm storage headroom or carry portable SSD for camera-roll export at trip end.

AirDrop to Mac: choose Original Format to preserve HEIC and GPS. 'Most Compatible' JPEG conversion sometimes drops auxiliary tags depending on OS version—verify one file after transfer.

Live Photos and HDR stacks still embed location on the primary asset. Burst mode writes GPS per frame when location is enabled—pick the hero frame from burst, metadata follows.

Settings → Location: ON. Then Apps → Camera (or your pro camera app) → Permissions → Location → Allow only while using. Third-party camera apps vary—Open Camera and Lightroom each need separate permission checks.

Google Photos map view aggregates geotagged uploads. Local-only shooters should install an on-device EXIF viewer that does not auto-upload to cloud before parsing sensitive files.

Manufacturer battery optimizers kill background location for third-party apps—not usually the stock camera, but travel workflow apps logging tracks may lose data. Disable optimization for apps you rely on for trip logging.

WhatsApp 'document' send preserves EXIF; ordinary image send compresses and strips. When coordinating with travel partners, share mystery files as documents, not gallery picks.

Samsung and Pixel HEIF/HEIC paths differ slightly in EXIF layout; modern parsers handle both. After OS major upgrades, re-test one file—permission defaults occasionally reset.

Export EXIF latitude and longitude to a spreadsheet: filename, datetime, lat, lon, altitude. Sort by date for chronological albums; cluster by proximity for multi-city road trips where dates blur across time zones.

Map visualization: paste coordinates into Google My Maps, QGIS, or GeoJSON viewers. Clusters along highways reveal overnight stops you forgot. Gap days with no photos still show on itinerary—cross hotel confirmation emails.

Rename files with ISO date + short place label after verification: `2024-06-12_cinque-terre_manarola_IMG_1234.heic`. Future search beats `IMG_1234`. Automation via exiftool: `exiftool -filename<${DateTimeOriginal}_${GPSLatitude}.jpg`—sanitize characters per OS.

Multi-device trips merge phone and mirrorless RAW. Mirrorless may lack GPS unless paired phone writes sidecar; sync clocks before departure so timeline merges align within seconds.

Backup triad: cloud (original quality), local SSD, and printed photobook subset. Metadata survival correlates with original retention—book prints carry no EXIF.

Scanned 35mm slides, 2005 point-and-shoot JPEGs before you enabled phone GPS, and video frame grabs lack useful coordinates. AI geolocation ranks regions from architecture, vegetation, and vehicle cues—jogging memory against trip diaries.

Workflow: run AI on the scan, note top three countries, open calendar for those years, match clothing season and companions' memories. AI proposes 'Portugal Atlantic coast'; you remember a 2011 rental car week—confirm with Flickr album comments or credit card fuel stops.

Do not expect rooftop precision from AI on generic beach scenes. Use AI to narrow 'which coastline' then browse map imagery along that coast for harbor breakwater shapes matching your photo.

Pair AI with sun angle tools when shadows are visible—morning east-lit facades constrain camera bearing. Blog guide on sun estimation complements travel archives.

Privacy: AI analysis on whereisthis.place processes in memory without retaining your vacation uploads—still avoid posting identifiable strangers to public forums when crowdsourcing guesses.

Scenario: 2018 cross-country drive, 4,000 photos, many unlabeled. One favorite shows a river bend from a guardrail overlook, golden hour, arid canyon, no EXIF—exported from an old Google Photos 'assistant' collage.

Step 1: locate original in '2018-09' album on NAS backup. EXIF present: 38.2°N, 109.8°W, elevation 1,950 m, timestamp 2018-09-14 18:42. Map pin: Dead Horse Point area, Utah.

Step 2: compare photo ridge line to map terrain; match Colorado River bend orientation. Confidence high without AI.

Alternate branch: if only collage remained, AI ranks Colorado Plateau canyon country; itinerary PDF lists Moab nights 12–15 Sept; sun azimuth from shadow on guardrail matches west-facing overlook—same conclusion, slower path.

Lesson: two minutes on originals beat an hour of AI when metadata survives. AI is the backup for true loss, not laziness before checking NAS.

Stripping location on share copies protects home and hotel patterns. iOS: duplicate photo → share duplicate with location off in export options. Android varies by gallery—use strip-location export in Google Photos before public upload.

Social platforms routinely remove EXIF anyway, but stripping locally prevents accidental document sends with GPS intact. See photography privacy guide for journalist-adjacent travelers blogging live.

Kids and school locations: family travel blogs should blur house numbers and strip school pickup geotags from weekday photos intermixed with vacation shots in same camera roll.

Cross-border road trips scramble chronological sorts: crossing from Slovenia to Croatia at midnight leaves photos dated in conflicting zones if phones auto-adjust slowly. Set camera clock to UTC for long overland segments, or annotate border crossing in a notes app with timestamp.

Roaming SIM swaps change phone time sources; airplane mode through multiple countries without sync produces bursts dated before previous city. After landing, open Maps once to refresh timezone before shooting hero landmarks.

Train photographers shooting from windows get GPS tracks offset from subject—coordinates tag the rails, not the mountain photographed across the valley. Interpret EXIF as camera position, then infer subject bearing from photo content and compass if recorded.

Cruise ships lose GNSS precision near steel superstructure; deck photos may geotag to open ocean while actually in fjord. Use port-day folders manually labeled when ship GPS drifts.

Hiking and backcountry photos add terrain interpretation: EXIF tags the trail switchback where you stood, not the peak in frame. Note compass bearing from photo content—snow line, ridgeline silhouette—and cross-check against peakbagging sites and trail wiki photos shot from the same switchback. A cluster of GPS points along a known trail segment confirms the hike; a single ocean-coordinate EXIF on a summit photo usually means the phone lost lock and cached the marina departure point.

Offline travel complicates metadata survival in non-obvious ways. You disable roaming data in Patagonia but GPS still writes tags; later, iCloud uploads the batch when you reach Santiago Wi-Fi and re-sorts albums by upload time instead of capture time. When reconciling a trip folder, sort by EXIF DateTimeOriginal, not file modified date, or you'll merge Chile captures into the wrong vacation album. Portable SSD imports at the hotel each night preserve both timestamps and originals before cloud sync reorders your library silently.

Pre-trip checklist laminated in passport pouch: location on, originals setting, clock sync, test EXIF, spare storage. Post-trip: import within 48 hours while memory fresh; batch geotag verification Sunday after return.

whereisthis.place EXIF inspector validates a drag-drop sample in seconds—no account required for metadata read. Follow with map plot and album naming.

For multi-year backlog projects, tackle one trip folder per session sorted by most recent first—recent trips have denser metadata and living memory.

When gifting photos to relatives, include a map PDF export of key coordinates—metadata in files they may not know how to read.

Journal apps paired with photo dates reconstruct narrative: 'Tuesday market in Oaxaca' plus EXIF cluster confirms which of twelve similar plaza shots belongs to which morning.

Group trips split photos across six phones—merge EXIF CSV exports from each participant before clustering, or one person's map shows only half the itinerary. Designate one travel buddy as metadata steward who collects document sends nightly; WhatsApp compressed picks from others may lack GPS even when your phone captured the same scene with tags intact.

International family groups often mix WeChat, WhatsApp, and iMessage—each path strips differently. Ask relatives abroad to resend favorites as documents through the app they actually received them on, not as forwarded previews that recompress mid-chain.

Ten-year photo libraries intimidate. Sort by year, then month; run EXIF-only pass flagging files with GPS IFD present versus absent. Attack absent bucket only for favorites—ignore blurry duplicates.

Grandparent slide scans: ask which trip decade before AI. Human memory narrows search space more than algorithms alone. Label scans 'c.1978 per Mom' separately from verified geotags.

Duplicate detection merges burst shots; keep best composition, retain GPS from any burst member—EXIF often identical across burst siblings.

Celebrate partial wins: 'somewhere in Provence 2003' beats total mystery. Precision can improve later when you find the rental car receipt with pickup address.

Action-camera and GoPro clips often embed GPS in video metadata while companion JPEG grabs from the same session lack tags—check both containers before running AI on a low-res export. For long video libraries, sample one GPS track per hiking day and interpolate approximate positions for untagged stills by timestamp proximity rather than geolocating every frame individually.

Scanned print photos from pre-digital trips deserve a separate folder naming convention—prefix 'SCAN_' and never merge them into phone-original albums without a manual decade label. Otherwise a 2024 scan of a 1998 print inherits confusing file dates and sends you hunting EXIF that never existed. Pair scans with one paragraph of travel journal context in the album description; human prose often beats AI when the scene is a generic beach but you remember which island ferry you took that week.