EXIF GPS Photo Finder

EXIF is metadata embedded in JPEG, HEIC, and TIFF files at capture time. When location services are enabled on a phone or a GPS module is attached to a camera, the device writes GPSInfo IFD tags: latitude, longitude, altitude, timestamp, and sometimes compass direction.

These tags survive file copies on disk but are routinely destroyed by social media platforms, messaging app compression, and many image editors on export. The original camera-roll file is your best evidence.

whereisthis.place reads EXIF locally using JavaScript — the same information visible in ExifTool or macOS Preview's Inspector, but with instant map visualization and an AI fallback when tags are absent.

The primary tags are GPSLatitude and GPSLongitude, stored as rational arrays (degrees, minutes, seconds) with GPSLatitudeRef (N/S) and GPSLongitudeRef (E/W). The finder converts these to decimal degrees for mapping.

Secondary tags add verification context. GPSAltitude confirms whether a photo was taken from a tower or ground level. GPSTimeStamp cross-checks against DateTimeOriginal for timezone consistency. GPSImgDirection shows which way the camera pointed — useful for matching Street View perspective.

Server-side EXIF tools require upload — a non-starter for sensitive journalism sources, legal evidence, or personal photos you do not want stored on third-party infrastructure.

whereisthis.place's EXIF GPS finder runs entirely in the browser tab. The file bytes never leave your device during metadata extraction. Only if you explicitly request AI analysis does the image transmit — and even then, processing is in-memory without gallery retention.

This architecture also means EXIF extraction is free without rate limits. Parse a thousand photos locally; you pay nothing because you consume no server resources.

If the finder reports no GPS tags, the file was likely re-encoded. Confirm by checking the sharing path: Instagram, Snapchat, Facebook, and TikTok always strip GPS. WhatsApp photo mode strips; document mode often preserves.

Some privacy-conscious users disable location services for the camera app — the photo has EXIF (camera model, timestamp) but no GPS block. AI visual geolocation is the next step.

Screenshots never contain EXIF GPS regardless of source. The EXIF inspector below shows exactly which tags are present so you know whether to proceed to AI or manual OSINT.

Power users cross-check automated output with manual tools. ExifTool command line (`exiftool -gps:all photo.jpg`) dumps raw tags. macOS Preview → Tools → Show Inspector → GPS tab provides a GUI equivalent.

The interactive EXIF inspector on this page simulates tag reading so you can learn which fields matter before uploading real evidence files. Understanding tag structure helps you spot spoofed coordinates — inconsistent altitude, impossible timestamps, or mismatched device models.

EXIF GPS reveals where a photo was taken, often precise enough to identify a home address from a backyard selfie. Before sharing photos publicly, strip GPS tags using your phone's export settings or tools like `exiftool -gps:all=`.

Conversely, when you need to find where a photo was taken, that same precision is valuable. whereisthis.place does not index or resell extracted coordinates. Use findings responsibly — verify places, not stalk people.

For journalists handling source photos, client-side EXIF reading protects source identity by avoiding unnecessary cloud uploads of raw evidence files.

A DJI Mavic export arrives as a 4K JPEG with rich EXIF beyond basic phone tags. Upload to the EXIF GPS finder. Primary coordinates: 64.1466° N, 21.9426° W — Reykjavik area. GPSAltitude reads 84 m AGL, consistent with a legal drone ceiling rather than ground level. GPSImgDirection: 247° — the camera faced southwest.

Cross-check in the EXIF inspector: Make 'DJI', Model 'FC7303', FocalLength 4.5 mm (ultra-wide aerial perspective). DateTimeOriginal and GPSTimeStamp align within two seconds — no sign of manual timestamp tampering. Open satellite view at the pin: visible geothermal steam plumes match the photo's background, confirming the coordinate against terrain rather than trusting tags alone.

Secondary use of partial EXIF: suppose GPS were stripped but Make/Model and FocalLength remained. You would know the capture was aerial, narrowing search to regions where that drone operator could legally fly — a different investigation path than ground-level AI geolocation. The finder surfaces all tags so you can pivot when GPS alone is missing.

Empty GPS output is not always the end of the EXIF story. Many files retain timestamps, device identifiers, and lens data that constrain AI or manual follow-up. Walk through these steps before declaring the file metadata-dead.

If the finder shows a Software tag from a social platform, treat GPS absence as platform policy — not a camera setting — and request the pre-upload original from the photographer when the case matters.