The six GPS EXIF fields that store your location
Location data in a JPEG or HEIC photo lives inside the GPS IFD (Image File Directory), a dedicated block within the EXIF structure. Six tags carry the core coordinate information.
GPSLatitude stores the latitude as three rational numbers representing degrees, minutes, and decimal seconds — for example, 51 degrees, 30 minutes, 26.4 seconds. GPSLatitudeRef is a single character, either "N" or "S", that gives the hemisphere. Together they describe a north-south position to roughly 1–3 metres depending on the GPS chipset quality. GPSLongitude and GPSLongitudeRef ("E" or "W") do the same for the east-west axis. GPSAltitude records elevation above sea level in metres as a rational number, and GPSAltitudeRef flags whether the value is above (0) or below (1) mean sea level. A seventh tag, GPSTimeStamp, stores the UTC time of the GPS fix as three rationals for hour, minute, and second, corroborating the DateTimeOriginal field and sometimes allowing reconstruction of a timeline even after the camera's local-time field is stripped.
Beyond the six core fields, the GPS IFD can include GPSImgDirection (compass bearing the camera faced, in degrees), GPSSpeed (speed at capture, relevant for action cameras and dashcams), and GPSDestBearing or GPSDestLatitude/Longitude if the camera logged a target destination. iPhones write GPSImgDirection consistently; Android handsets vary by manufacturer.
What iPhone records and the two ways to control it
An iPhone embeds GPS coordinates in every photo taken when location services are enabled for the Camera app. The coordinates are written at capture time into the EXIF GPS IFD and are not displayed in the Photos thumbnail grid — they are invisible to casual inspection but are present in the raw file.
Apple provides two distinct controls. The first is the Camera location toggle in Settings → Privacy & Security → Location Services → Camera. Setting this to "Never" stops the Camera app from accessing GPS entirely, so photos are taken without any GPS fields. This is a permanent setting that applies to every photo until you change it. The drawback is that features like automatic location-based album grouping in Photos stop working.
The second control operates at share time rather than capture time. In the iOS Photos app, when you tap the share icon, you see a "Location" toggle in the share sheet above the app grid. Turning this off strips the GPS IFD fields before the file is handed to the receiving app. Critically, this toggle resets to "on" for every new share — you must remember to turn it off each time. The original file stored on your device retains the GPS data; only the copy being shared has it removed.
A third path exists for AirDrop specifically: when you share via AirDrop, iOS does not automatically strip location data even if the Photos share-sheet toggle was set to off on a previous share. Each AirDrop transfer must be handled with the share-sheet toggle actively disabled at that moment.
Android location recording and removal options
Android's stock Camera app (and the Google Camera app) includes a "Save location" toggle within the app settings. When enabled, the Camera requests fine-location permission from the OS and writes GPS coordinates into EXIF on capture. Disabling the toggle inside the Camera app is the simplest permanent fix; the app stops writing GPS fields to new photos.
Samsung's Camera app on Galaxy devices carries the same toggle under Settings → Location tags. On devices running One UI, this toggle is labeled "Location tags" and appears near the top of Camera settings. Pixel devices running the Google Camera app show it as "Save location" under camera settings. In both cases, disabling it removes GPS fields from all subsequent photos.
For photos already on the device, the Android Files app does not expose metadata editing. Third-party apps can write to EXIF fields if the storage permission is granted, but the reliable approach for bulk removal before sharing is to use a browser-based EXIF remover that processes the file locally without uploading it to a server. Google Photos does not strip location data from downloads or shares — it preserves the original file metadata.
Privacy risks of posting location-bearing photos
The risk from unstripped GPS coordinates is most acute in specific sharing contexts. Secondhand marketplace listings (Craigslist, Facebook Marketplace, Gumtree) expose photos as downloadable files to every visitor. A photo of an item taken at home carries the home's coordinates in the EXIF block, allowing any buyer or malicious actor to extract the address with a free metadata viewer. This is a well-documented pattern: sellers unknowingly disclose their home address to strangers at scale.
Rental listings photographed by the tenant create the same exposure: the building's GPS position is embedded in every photo, confirming the exact address even if it was omitted from the listing text. Dating apps that allow photo uploads may or may not strip metadata before display; if the raw file is accessible, coordinates from photos taken at a workplace or regular location reveal a pattern of movement.
Most major social platforms — Instagram, Facebook, X (formerly Twitter), TikTok — strip GPS EXIF data from photos upon upload as part of their image recompression pipeline. However, this stripping is not guaranteed for every upload path or API endpoint, and direct-download features on some platforms provide the original file. Relying on a platform to strip location data is not a substitute for removing it before the upload.
C2PA and XMP: the second and third location containers
EXIF is not the only place location data can live in an image file. Two additional systems can carry independent location records.
C2PA (Coalition for Content Provenance and Authenticity) is a cryptographically signed manifest embedded in the image file. It can record a "location assertion" as a named GPS coordinate within the manifest JSON structure. Crucially, removing the EXIF GPS IFD does not affect the C2PA manifest — the two structures are separate. Cameras and phones that write C2PA (a growing set including recent iPhones, Leica cameras, and some Android models) may embed location in the manifest even after EXIF GPS removal. Reading a C2PA manifest requires a dedicated viewer; the location assertion field is listed under the "actions" or "location" claim in the manifest JSON. Removing C2PA entirely involves stripping the entire C2PA block, which also discards provenance assertions.
XMP (Extensible Metadata Platform) is an XML-based metadata block that can be embedded alongside EXIF in a JPEG or as a separate sidecar file. The XMP spec includes exif:GPSLatitude and exif:GPSLongitude properties that mirror the EXIF GPS fields. Camera apps and photo-editing software that write XMP can therefore write GPS coordinates into both the EXIF GPS IFD and the XMP block simultaneously. A tool that removes only the EXIF GPS IFD without touching the XMP block leaves a redundant location record in the XMP. A complete location strip requires removing GPS fields from EXIF, XMP, and (where present) C2PA.
Removing location data in bulk
Removing GPS data from a single photo before sharing is straightforward with the iOS share-sheet toggle or a browser-based tool. Removing it from many photos — such as a batch of listing photos, an event album, or a folder before a backup upload — requires an approach that scales.
On macOS, the command-line tool ExifTool by Phil Harvey is the standard for batch metadata work. The command exiftool -gps:all= -overwrite_original *.jpg removes all GPS-namespace tags from every JPEG in the current directory without creating backup copies. Adding -r makes it recursive across subdirectories. The -gps:all= syntax targets the GPS IFD specifically, leaving all non-GPS EXIF tags (camera model, aperture, shutter speed, ISO) intact. To also strip XMP GPS fields, add -XMP:GPSLatitude= -XMP:GPSLongitude= -XMP:GPSAltitude= to the same command.
On Windows, ExifTool runs identically from Command Prompt or PowerShell. The command syntax is the same; point it at a folder with a path instead of a glob pattern: exiftool -gps:all= -overwrite_original "C:\Photos\Listings".
For users who prefer a graphical interface on macOS, the built-in Photos app does not expose bulk metadata editing. Third-party apps like ImageOptim can batch-process files and offer metadata removal as part of optimisation. On iOS, Apple's Shortcuts app can be used to build an automation that runs each selected photo through the share-sheet with location toggled off, though this is slower than desktop batch tools.
Surgical GPS removal versus full EXIF deletion: when each is appropriate
Removing location data does not require removing all EXIF metadata. The choice between selective GPS removal and full EXIF deletion depends on what the recipient needs and what you are willing to disclose.
GPS-only removal strips the GPSLatitude, GPSLatitudeRef, GPSLongitude, GPSLongitudeRef, GPSAltitude, GPSAltitudeRef, GPSTimeStamp, GPSDateStamp, and related GPS IFD tags while leaving all other EXIF data in place. The recipient can still see the camera model, lens, aperture, shutter speed, ISO, DateTimeOriginal, and any other technical metadata. This is appropriate for photography clients who need technical shooting data for post-processing, licensing archives where technical metadata has legal value, or print workflows where color space and resolution tags must remain.
Full EXIF deletion removes all metadata blocks — EXIF, IPTC, XMP, and any manufacturer MakerNote data. The output file contains only pixel data and a minimal JFIF or baseline JPEG header. This is appropriate when the audience is anonymous (a public marketplace listing, a forum post), when total metadata minimisation is the goal, or when you do not know what the downstream system does with metadata. The trade-off is loss of all technical data, including color space information, which can affect how some displays and printers render the image.
A middle path used in professional publishing is to write back clean metadata: strip everything, then re-embed only approved fields (copyright, author, color space, resolution) using a tool like ExifTool. This produces a file with the minimum required metadata and no residual GPS, device fingerprint, or serial-number-class information.