How to Check and Remove Location Data from Your Photos

Every photo you take with a smartphone carries more than just pixels. Embedded inside the file is a block of metadata called EXIF — Exchangeable Image File Format — that can record the make and model of your camera, the exact date and time the shutter fired, your exposure settings, and, if location services were enabled, precise GPS coordinates of where you were standing when you took the picture. Sharing a photo of your living room, your kids at the park, or your new car in the driveway can quietly broadcast your home address to anyone who knows where to look. That's not speculation; it's a documented privacy risk, and it's the reason stripping location data before posting or emailing photos is one of the simplest, highest-value privacy habits you can build.

The good news is that removing GPS data is easy. The bad news is that it's inconsistent — different platforms treat metadata differently, and many people assume they're protected when they aren't. Let's walk through exactly what gets embedded, where it survives, and how to strip it reliably on every major platform.

First, understand what you're actually removing. EXIF location fields typically include GPSLatitude, GPSLongitude, GPSAltitude, and sometimes GPSSpeed and GPSImgDirection — effectively a pin on a map accurate to within a few meters. Alongside that, your phone may store the device model, serial number, software version, and timestamps. Photos from professional cameras add even more: lens serial numbers, copyright fields, and IPTC fields that photographers fill in deliberately. Before you strip anything, it helps to see what's actually there. Uploading a photo to FilesAudit's metadata analysis tool shows you the complete EXIF, GPS, and XMP payload of the file in a readable form, so you're not guessing about what you're leaking. Checking one or two representative photos from your camera roll is often a wake-up call — people routinely discover coordinates embedded in photos they swore they'd taken with location services off.

On iPhone, there are two approaches: prevent capture or strip at share time. To stop location recording entirely, go to Settings, then Privacy & Security, then Location Services, then Camera, and set it to Never. Photos taken afterward contain no GPS fields at all. But that doesn't clean your existing library, and many people actually want location data for their own albums — it's how Memories and the Places map work. For sharing, iOS has a built-in solution: when you select a photo and tap the share sheet, tap "Options" at the top and toggle off "Location" (and optionally "All Photos Data"). This sends a version without GPS fields. The catch is that it's per-share and easy to forget, and it only applies through the share sheet — syncing the file through iCloud Drive, AirDrop with full quality, or third-party apps can bypass it.

Android offers a similar split. In Google Photos, you can't edit EXIF directly, but the camera app (Google Camera, Samsung Camera) has a "Save location" or "Location tags" toggle you can switch off going forward. To scrub existing photos, the most practical route is a dedicated app from the Play Store — search for an EXIF remover or use open-source tools like Scrambled Exif or Image Privacy apps — which let you select photos and save stripped copies. Some manufacturers' gallery apps also include a "remove location" option when sharing. As with iOS, the key distinction is whether the app creates a cleaned copy or only strips data when sharing through its own interface. If you email the original file as an attachment, the metadata travels with it.

On a desktop, you have the most control. On Windows, right-click a photo, choose Properties, go to the Details tab, and click "Remove Properties and Personal Information" at the bottom. You can either create a copy with all properties removed or selectively delete fields from the original. It's built in, free, and adequate for GPS stripping — though it doesn't handle every XMP field, and it processes files one at a time unless you multi-select. On macOS, Preview can show you the metadata (Tools, then Show Inspector, then the GPS tab), but it can't remove it directly; the standard tool is the free command-line utility ExifTool, where running `exiftool -gps:all= photo.jpg` deletes only the GPS block while leaving everything else intact, or `exiftool -all= photo.jpg` scrubs the entire metadata payload. ExifTool is the industry standard for a reason — it handles hundreds of metadata formats and works on batches: point it at a folder and it cleans everything in seconds.

Here's the critical nuance most advice articles skip: where you share matters as much as how you clean. Major social platforms — Facebook, Instagram, Twitter/X, TikTok, and LinkedIn — strip EXIF metadata from images at upload, so a photo posted there generally arrives without GPS data even if you didn't clean it yourself. But messaging and file transfer are a different story. WhatsApp and Messenger compress and strip images sent as photos, yet files sent as "documents" bypass that processing entirely. Email attachments are transmitted byte-for-byte unchanged. Cloud links from iCloud, Google Drive, or Dropbox serve the original file. Flickr, notably, preserves EXIF and can even display a public map of where your photos were taken. So the risk ranking looks roughly like this: posting to a major social feed is low risk even uncleaned, sending as a compressed messaging image is mostly safe, and emailing, AirDropping, or linking the original file is full exposure unless you strip it first.

That's why the safest workflow is to clean the file itself rather than rely on the platform to do it. Once the GPS fields are gone from the file, it doesn't matter how it travels — email, cloud, USB stick, or a platform you've never heard of. The metadata simply isn't there to leak.

A word of caution about screenshot-based stripping, which people often recommend: taking a screenshot of a photo does produce a new file without the original EXIF, but it also reduces resolution, changes the aspect ratio, and adds its own metadata (device model, screenshot timestamp). It's a privacy hack, not a professional solution. Similarly, re-saving through an editor like Paint or Preview may drop some fields but silently preserve others — XMP sidecar data and embedded thumbnails can survive a naive re-save. Embedded thumbnails are a sneaky one: a photo cropped to hide a sensitive background can still contain the original uncropped image inside its thumbnail. Proper tools like ExifTool, or a dedicated cleaner, remove the thumbnail block too.

There's also a verification step that almost nobody does, and it's worth building into your routine. After stripping, confirm the data is actually gone. Re-open the file in a metadata viewer and check that the GPS fields are empty — not just the ones you expected, but any XMP location fields or IPTC location strings that some editing apps write separately from EXIF GPS. You can drop the cleaned photo into FilesAudit and compare the report against the original: the platform extracts the full metadata block and also computes the file's SHA-256 hash, which is useful beyond privacy. If you're a journalist, lawyer, or archivist, you actually face the opposite problem sometimes — you need to prove a photo is untouched and original, with its metadata intact. In that case, stripping location data is the wrong move; instead you want to document the original file's fingerprint so any later copy can be checked against it. The dedicated guide to JPG metadata explains which fields matter for authenticity versus privacy, and the article on checking whether an email attachment was tampered with covers the hash-comparison side of that workflow.

For people handling photos in bulk — a real estate agency removing coordinates from hundreds of listing photos, a researcher anonymizing field images, a company scrubbing employee photos before publication — manual per-file cleaning doesn't scale. ExifTool scripting handles this if you're comfortable on the command line, and for larger recurring workloads the FilesAudit Desktop App lets you analyze metadata across large batches locally, so you can audit which files contain GPS data before deciding what to strip. An audit-first approach is smarter than blind stripping: some metadata is worth keeping (copyright and creator fields, for instance, which support ownership claims), so knowing exactly what's in each file lets you remove location selectively rather than nuking everything.

It also helps to understand the limits of stripping. Removing EXIF GPS makes the file itself clean, but it doesn't erase location information visible in the image content — landmarks, street signs, license plates, the view from your window. Investigators and OSINT researchers regularly geolocate photos from visual clues alone. Cleaning metadata prevents the automatic, trivially easy leak; it doesn't defeat determined analysis of the picture's contents. Similarly, if you've already shared a photo with location data, stripping your local copy doesn't retract what's out there — anyone who downloaded the original still has it. Prevention beats remediation, every time.

So here's the practical checklist, in plain terms. Decide whether you want location capture off at the camera level (best for privacy, worst for your own organization) or on with stripping at share time. If stripping at share time, use the share-sheet toggle on iOS or a cleaner app on Android for casual sharing, and ExifTool or the Windows Properties dialog for anything you send as an original file. Assume that email attachments, cloud links, AirDrop, and "send as document" transfers preserve everything. Clean the file itself when in doubt. Verify the result with a metadata viewer before sending anything sensitive — a thirty-second check on FilesAudit confirms the GPS block is gone and gives you a documented record of the file's final state. And remember that metadata is only one layer: glance at the image itself for anything that reveals where you are.

Location metadata is genuinely useful — it powers your photo maps, your memories, your search-by-place. The goal isn't to live without it. It's to make sure that the decision of who knows where a photo was taken stays yours, made deliberately, rather than handed silently to every recipient of every file you share. Once you've set up a stripping habit and verified it works, that control costs you nothing but a few seconds per share.