EXIF GPS Complete Guide

EXIF (Exchangeable Image File Format) is metadata embedded in JPEG, TIFF, HEIC, and some RAW files. Beyond GPS, EXIF records camera make and model, lens focal length, shutter speed, ISO, flash status, and capture datetime. GPS tags are optional — present only when location services were enabled for the camera app at shutter time.

Standard GPS EXIF fields include GPSLatitude, GPSLongitude, GPSAltitude, GPSTimeStamp, and GPSImgDirection (compass bearing). Coordinates are stored as degrees, minutes, seconds with hemisphere references (N/S, E/W). Software converts these to decimal degrees for map display.

EXIF lives in the file header, not in the pixel data. Stripping EXIF does not visually change the image — it removes the metadata block. Re-adding fake GPS later is possible with editing tools, which is why verification workflows cross-check EXIF against visual scene content.

Smartphones request location from GPS, Wi-Fi, and cell tower fusion when the camera app opens. If permission is granted, coordinates write into EXIF at capture. Accuracy typically ranges from 3–15 meters outdoors; indoor captures may inherit last-known location with lower accuracy.

Dedicated cameras with GPS modules (some DSLRs, action cameras, drones) embed coordinates similarly. Drones also store flight telemetry in separate XMP or proprietary formats beyond standard EXIF.

Screenshots never inherit scene GPS. They create a new file with metadata about the screenshot action, not the location depicted. Social media 'location tags' are platform metadata stored on servers — not EXIF in the downloadable image.

Client-side extraction is the privacy-safe default. JavaScript libraries like exifr parse EXIF locally in your browser — the file never uploads to a server. whereisthis.place uses this approach for free instant GPS reads.

Desktop alternatives include ExifTool (command line, gold standard for forensic work), macOS Preview (Inspector → GPS tab on some files), and Windows Properties → Details tab (limited fields).

Mobile: iOS Photos shows location on a map for originals in your library but strips GPS on share unless using 'Include Location' on AirDrop to trusted devices. Android Google Photos displays location for backed-up originals.

Workflow: obtain original file → parse locally → if GPS present, plot decimal coordinates on map → visually verify scene matches satellite imagery → document extraction method and timestamp for audit trails.

GPSLatitude and GPSLongitude are the core fields. Example: 48.8584° N, 2.2945° E places you at the Eiffel Tower area. Always check hemisphere references — a sign error flips you to the wrong hemisphere.

GPSAltitude indicates meters above sea level. Useful for mountain photography verification but rarely decisive alone. GPSImgDirection shows compass bearing the camera faced — helpful for orienting street-view comparisons.

DateTimeOriginal versus GPS timestamp: these can differ if the camera clock was wrong or GPS lock arrived seconds after shutter. For forensic timelines, note both and flag discrepancies over 60 seconds.

DOP ( dilution of precision ) fields when present indicate GPS accuracy confidence. Higher DOP means less reliable coordinates — rare in smartphone EXIF but appears in survey-grade GPS cameras.

Social platforms remove GPS to protect user privacy at scale. Facebook, Instagram, Twitter/X, TikTok, and LinkedIn strip location tags on upload by policy. Users rarely notice because in-app location features use separate platform metadata.

Messaging apps compress and strip. WhatsApp, Telegram, and Signal re-encode images for bandwidth, typically removing EXIF. Request 'document' or original file send options when investigating.

Email clients vary. Some preserve EXIF on direct attachment; webmail re-encoding may strip. Cloud share links often serve processed previews without metadata.

Editing software may strip by default. Export dialogs in Photoshop, Lightroom, and Canva often include 'Remove location info' checkboxes — verify settings before assuming EXIF survived editing.

Posting an original JPEG from your home garden can leak exact home coordinates to anyone who downloads and inspects EXIF. High-profile cases include celebrities and activists compromised by overlooked metadata.

Children and domestic settings deserve extra caution. Family photos with GPS enabled reveal school routes, homes, and routines when shared in parent groups as originals.

Journalists and sources: sending raw files to newsrooms preserves GPS — good for verification, risky if published raw to audiences. Establish newsroom policies for metadata handling.

The Privacy Toggle interactive below demonstrates what metadata reveals and how stripping works before you share.

iOS: before sharing, use Shortcuts or third-party EXIF strippers, or share via apps configured to export without location. macOS Photos share sheet often strips location — verify in Preview after export.

Android: Google Photos 'Remove location' option on share; dedicated EXIF editor apps for batch processing.

Desktop batch: ExifTool command `exiftool -gps:all= -overwrite_original *.jpg` removes GPS tags while preserving other EXIF if desired.

Best practice: maintain two copies — archival original with EXIF for personal records, shareable export with GPS stripped. Never rely on platforms to strip for you; some niche forums and email paths preserve metadata.

EXIF can be edited. Tools add, modify, or remove GPS tags without changing pixels. Treat unexpected EXIF as hypothesis, not proof — verify against visual scene content.

Signs of tampering: GPS coordinates pointing to ocean while scene shows urban street; timestamp inconsistent with shadow direction; camera model field mismatched with known source device.

Chain of custody: record who provided the file, transfer method, and hash (SHA-256) at receipt. Re-hash after analysis to confirm file integrity.

For legal contexts, consult jurisdiction-specific rules on metadata admissibility. EXIF supports investigations; court standards vary.

A photographer has 4,000 unlabeled JPEGs from a 2015 road trip. No album organization. Goal: map all photos.

Batch ExifTool extract: `exiftool -csv -GPSLatitude -GPSLongitude -DateTimeOriginal -r ./2015-trip/ > locations.csv`. Result: 2,847 files contain GPS; 1,153 do not (indoor shots, GPS disabled moments, stripped exports).

Import CSV to Google My Maps — instant route visualization across Utah and Arizona. The 1,153 without GPS get queued for manual review or AI geolocation as secondary pass.

Total processing time: 12 minutes for extraction and mapping. Without EXIF, the same project spans weeks of visual analysis. This is why EXIF-first workflows matter.

Always run EXIF before AI or manual visual work. whereisthis.place automates this ordering — browser EXIF read, then optional AI when coordinates are absent.

Link EXIF results to verification: plot on satellite, confirm architecture match, check timestamp against known events. GPS alone without scene check risks acting on corrupted metadata.

For teams, template a one-line EXIF summary in investigation notes: 'GPS present: 34.0522° N, 118.2437° W, 2024-03-15 14:32 local, iPhone 14 Pro, verified against scene.'

See our EXIF GPS photo finder money page for the fastest client-side tool, and the master geolocation guide for full pipeline context.

Understanding where EXIF dies helps you request originals from the right source before investigating pixels.

WhatsApp and Telegram re-encode images for bandwidth — treat forwards as EXIF-stripped unless sent as documents. iMessage sometimes preserves metadata on direct sends between iPhones but not always on group forwards.

Google Photos shared links often serve compressed previews — download 'original' explicitly when collaborating on investigations. Dropbox and Google Drive direct file links usually preserve EXIF if the uploaded file contained it.

Twitter/X and Facebook strip GPS on upload universally in current policies. Flickr and some photography communities preserve EXIF by default — check uploader settings on archival photo platforms.

DJI and most consumer drones embed GPS in both image EXIF and flight logs (.SRT, .LRF, or app-exported KML). Cross-reference image EXIF against flight log when investigating discrepancy.

GoPro and action cameras with GPS enabled write coordinates when lock acquired — fast motion and underwater housings often block GPS, leaving empty tags despite outdoor capture.

Drone EXIF may include gimbal pitch and flight altitude separate from GPS altitude field — useful for matching aerial perspective against satellite tilt views.

Regulatory geofencing does not remove EXIF — it restricts flight. Coordinates still reflect actual shutter position when GPS lock succeeded.

Personal travel archives and professional shoot catalogs benefit from batch extraction before manual review. ExifTool command `exiftool -csv -GPS:GPSLatitude -GPS:GPSLongitude -DateTimeOriginal -r ./folder/ > out.csv` produces spreadsheet-ready output in seconds.

Filter CSV to rows with non-empty GPS — sort by date to reconstruct trip timelines automatically. Unmatched files become your AI or manual visual queue.

Lightroom and Capture One map modules offer GUI batch geotagging for files missing GPS when you know shoot location from planner notes. Do not confuse planner geotags with camera-embedded forensic GPS.

whereisthis.place complements batch CLI tools with spot validation — upload suspicious outliers where CSV coordinates contradict remembered scene content to catch corrupted or edited metadata.

GPS shows null despite shooting outdoors: location services disabled for camera app, GPS lock not acquired before shutter, or airplane mode active. Check phone settings and retest with a fresh shot.

Coordinates plot in ocean or wrong continent: usually corrupted file, edited metadata, or hemisphere parsing error. Verify against visible scene before trusting.

DateTimeOriginal wrong by hours: timezone not embedded correctly or camera clock unset. GPS timestamp may differ from DateTimeOriginal — note both in forensic logs.

HEIC not parsing in older tools: update parser or convert to JPEG preserving metadata with `exiftool -tagsfromfile source.HEIC dest.jpg` before analysis.

Professional workflows sometimes store GPS in XMP sidecar files (.xmp) alongside RAW originals rather than embedded EXIF. Lightroom writes both depending on catalog settings.

When auditing location metadata, check embedded EXIF, XMP sidecar, and IPTC fields — tools may display merged view while export strips only one format.

ExifTool reads all namespaces: `exiftool -a -G1 -s image.jpg` shows every tag group. GPS may appear under [EXIF] or [XMP-exif] with duplicate values that should match.

whereisthis.place browser inspector focuses on embedded EXIF in uploaded JPEG/HEIC. RAW and sidecar-heavy workflows should use ExifTool locally before web inspection.