INITIALISATION DU SYSTÈME...
The native iOS and Android options strip location only. This guide shows what they leave behind and how to get a genuinely clean file straight from your phone.
On iPhone and Android alike, the system can strip a photo's location when you share it, but it does not strip the rest of the metadata: the device model, the exact date and the software version stay in the file. This guide covers the native methods, what they actually remove, and how to get a fully clean file.
A smartphone writes a block of metadata describing the shot into every picture. GPS coordinates get the most attention, but they are not alone: the phone model, a timestamp accurate to the second and the system version sit there too, and they survive cropping and copying. Our guide to EXIF and GPS data covers those fields in detail.
The distinction that matters here is simple: removing the location and removing the metadata are two different operations. The native tools on both systems do the first, never the second.
iOS offers a setting in the share sheet that leaves the position out of the copy you send. The exact wording changes between system versions, but the path stays the same.
In the privacy settings, location services can be denied to the Camera app, so future photos are taken without coordinates. Two limits: photos already in your library keep theirs, and the other fields keep being written.
Neither touches the device model, the capture date or the software that saved the file. A photo 'without location' therefore remains perfectly tied to one device and one precise moment.
Android does not impose a single gallery, and behaviour depends on the app in use. The most common route goes through Google Photos.
Vendor skins sometimes add their own details menu with an entry to clear the position of a saved photo. Here too the operation covers location alone, its effect depends on the app, and nothing guarantees the exported file is free of the other fields.
| Method | Removes GPS | Removes date, model, software | Changes the original file |
|---|---|---|---|
| iOS share option | Yes, on the copy sent | No | No |
| Location denied to Camera | Yes, for future photos | No | No |
| Android remove-location | Yes, on the copy sent | No | No |
| Screenshot of the photo | Yes | Replaced by the screenshot's own | Creates a new file |
| Full re-encode | Yes | Yes | Produces a clean file |
HEIC, the default on iPhone for several generations, is a container: it carries the same EXIF fields as a JPEG, coordinates included. Converting it is not enough, because a conversion without re-encoding usually copies the metadata straight into the output file.
A Live Photo pairs the image with a short video clip carrying metadata of its own. Sharing one therefore means sharing two files, one of which most image-cleaning tools ignore. Converting the Live Photo to a still before publishing removes that second surface.
To remove the whole block rather than just the position, the image has to be re-encoded. That can be done straight from the phone's browser, with no app to install and without the photo leaving the device.
The process redraws the image from its pixels alone: no metadata block survives, by construction rather than by filtering. The security page explains the mechanism, and our local vs cloud comparison covers local processing against remote services.
These questions cover mobile devices. For the contents of the EXIF block itself see the EXIF and GPS guide, and for the provenance of generated images see the questions hub.
It stops new coordinates from being written, but it does nothing to photos you already took, which keep their GPS. It also removes none of the other fields: the phone model, the exact timestamp and the software version keep being written into every file.
No, it removes location only. The label says as much: it speaks of location data, not of metadata. The capture date, the device model and the software all remain in the shared file.
Because the app usually keeps its own copy of that information in a local database, separate from the file. The exported photo can be clean while the gallery still plots it on a map. Only a check of the exported file settles it.
Yes, in full. Those transfers copy the file as is, with no re-encode: the recipient gets exactly what the original holds, GPS included. The same applies to an email or messaging attachment.
Yes. HEIC is a different container, not a protection: it carries the same EXIF fields, GPS included. Converting a HEIC to JPEG without re-encoding usually copies those fields straight into the converted file.
With the native options, yes: they apply to one share and leave your files untouched. A re-encode, by contrast, produces a permanently clean file that you can reuse as many times as you need.