Remove GPS Location Data from Photos Guide 2026
Remove GPS location data from photos before posting, verify the clean copy, and keep the original file untouched.
Contents
Everyone’s been here: a harmless porch photo, a school-event snapshot, or a marketplace pickup picture is ready to post, then the map pin in the info panel makes the file feel less harmless. To remove GPS location data from photos, use the built-in Photos or camera settings first, export a clean copy, then verify that the copy no longer shows a location.
The fastest safe path
Start with the tool already on the device. On iPhone, remove location in Photos or turn off Location in the share sheet. On Android, turn off the camera’s location tag before the next shot. For a file you are about to post, make a clean copy and check that copy before upload.
That split matters. Hiding location for one iPhone share is not the same as stripping every metadata field from a file you will reuse later. Stopping future GPS tags is a third job. Apple documents all three paths: remove location from a photo, turn off Location while sharing, or set Camera location access to Never in Settings.
When you need a clean copy rather than a one-time share, use remove GPS metadata and download the stripped file. The caveat is plain: keep the original somewhere else, because metadata is useful for searching your own library later (which is usually why the phone saved it).
iPhone and iPad Photos
For one iPhone photo, open Photos, choose the image, tap the More button, then use Adjust Location > No Location. If you are sharing immediately from Photos, open the share sheet, tap Options, turn off Location, and then send the image. Apple’s Personal Safety guide, published in October 2025, names both controls.
I use the share-sheet toggle only for throwaway sends, like texting one photo to a friend. For a public post, client handoff, or anything that might get reposted, I prefer a separate clean export because it gives you a file you can inspect without trusting the next app in the chain.
There is also the future-facing setting: Settings > Privacy & Security > Location Services > Camera > Never. That stops new camera location collection on iPhone or iPad, but it won’t rewrite the photos already sitting in your library. Old files still need their own pass.
If the same photo is going into an email thread, make the clean copy first, then handle size separately. The workflow in our email attachment copy guide is a better second step than smashing quality before you’ve removed the data you care about.
Android and Google Photos
Android is messier because the label changes by maker. Google’s help page lists Save location for Google devices, Location tags for Samsung, Geo-tag photos for HTC, and Store location data for OnePlus. Same concept, different switch.
Open the camera app settings first. If you find Save location or Location tags, turn it off before you take the next photo. That’s the boring fix. It protects tomorrow’s files, not yesterday’s gallery, which is why a cleanup pass still matters for anything already shot.
Google Photos adds one more wrinkle: it distinguishes camera-captured location from estimated location. Google says estimated locations won’t be shared even when you include location details, but it also warns that people may still infer place from landmarks in the photo. That warning is the part most metadata tutorials skip.
So if a product photo shows a street sign in the background, EXIF removal only solves half the problem. Strip the data, then crop or blur a face or plate when the pixels themselves reveal the place.
Windows and Mac checks
Windows File Explorer can show the obvious metadata: right-click the image, open Properties, then check the Details tab. If GPS fields are visible there, do not post that copy. Use the remove-properties option if it’s available for your file type, then save a copy and check the copy again.
On Mac, Photos handles the cleanest location workflow for pictures inside the library: select the photo, use Image > Location, then hide or remove the location depending on the available control. Preview can be useful for inspecting and exporting, but I wouldn’t treat a Preview resave as a complete metadata scrub unless I checked the result afterward.
The practical test is not glamorous: open the exported file in a different place than the editor you used (a dull check, but a useful one). If the map, latitude, longitude, camera serial, or owner field still appears, the file is not clean enough for a public post.
Format changes can complicate that check. A transparent PNG flattened to JPG may fix compatibility while creating a visible matte, which is a different problem; this transparent cutout note explains why the background can change when alpha disappears. If an upload form demands a JPG, make the metadata-clean file first, then convert the format.
Batch cleanup without trusting the upload form
For a folder of photos, don’t rely on Instagram, Facebook, Etsy, Craigslist, or a forum upload form to remove metadata for you. Some platforms strip parts of EXIF. Some preserve parts. Some generate multiple derivatives. The only file you control is the one you upload.
Use Araluma EXIF Remover when you want the simple browser path for JPG, PNG, or HEIC files. It is built for the common phone-photo job: remove GPS location, camera data, date, and personal metadata, then download a cleaner copy for sharing.
For command-line batches, ExifTool is the heavyweight option. The fetched documentation lists Version 13.59, dated May 27, 2026, and documents -all= as the syntax that deletes all metadata. It also preserves the original file by adding _original when writing, which is exactly the behavior you want before running a folder-wide cleanup.
That power has a price. ExifTool is fantastic if you’re comfortable in Terminal or PowerShell; it’s overkill if you have three HEIC photos from an iPhone and a post due in five minutes. For those quick web handoffs, a browser cleaner plus a manual verification pass is the better trade-off.
If the cleaned file still needs a compatibility format, make that a separate step. Use an upload-form JPG when a portal rejects WebP or HEIC-adjacent workflows, or send photos as a PDF when the recipient needs one review file instead of a loose set of images.
The verification pass
Verification is where the sloppy guides usually stop too early. They say “remove metadata,” but the safer routine is “remove, download, inspect, then post.” Four verbs. Worth the extra minute.
Use this check before a public upload:
- Open the cleaned copy, not the original.
- Look for a map, GPS, latitude, longitude, or location name.
- Check obvious personal fields: camera owner, author, copyright, software, and original date.
- Reopen the same file in a second app or web viewer if the first app hides details.
- Post only that verified copy.
EXIF can include more than a map pin. The standard family can carry date and time information, camera settings, geographic data, copyright details, and thumbnails. Most people only worry about GPS, but a client file named with a product launch date or a camera owner field can be just as awkward in the wrong place.
Once the metadata is clean, you can use Araluma Compress for upload size. Do it in that order. Compression first can create another export you then have to scrub again, and that is how small workflow mistakes multiply.
When metadata removal is not enough
GPS metadata tells one story. The image tells another. A storefront reflection, license plate, school logo, distinctive window view, or delivery label can reveal location even after every EXIF field is gone.
My rule is simple: if the place matters, inspect the pixels after you inspect the metadata. Crop the background tighter, blur identifiers, or choose another frame. Keep the original for your archive, publish the clean copy, and don’t let a map pin decide who gets more information than the photo needed to carry.
