What EXIF and GPS data reveal about your photos

What the fields actually are

EXIF was designed for photographers. Shutter speed, aperture, ISO, focal length, lens, orientation: information that helps you understand how a picture was taken. That part is harmless and often useful, and removing it costs you the ability to learn from your own photographs.

The fields worth caring about are a smaller set. GPS latitude, longitude and sometimes altitude give a position. DateTimeOriginal gives the moment. Make, Model and the vendor MakerNote identify the device, and MakerNote blocks can include a camera body serial number. Software records what edited the file. Artist and Copyright carry whatever name was configured on the device.

IPTC and XMP are two further metadata standards that often ride along, added by editing and cataloguing applications. They can hold captions, keywords, creator names and contact details — filled in by an application without anyone consciously entering them.

Why a location field is different from the others

A single photograph with coordinates is a point on a map. A set of photographs is a pattern: where you live, when you are usually there, where the children go to school, which days you are away.

The obvious cases are the ones people notice — a picture of a bicycle for sale, taken in the front garden, carrying the coordinates of the front garden. The less obvious cases are more common: a photograph in a forum post, a screenshot that was a photograph first, a picture sent to a stranger in a marketplace chat.

Device identifiers are the second category worth understanding. A serial number in a MakerNote links every photograph from one camera together, including photographs published in different places under different names.

Which platforms strip metadata

The honest summary is that behaviour varies by platform, by upload path and over time, so treating any of them as a guarantee is a bad idea.

Large social networks generally re-encode uploaded images, which usually drops EXIF as a side effect. That is a side effect and not a promise: it applies to the version they display, and it does not necessarily apply to a file sent through a chat feature or attached at original quality.

Messaging applications differ significantly. Some strip metadata when an image is sent as a photo and preserve everything when the same image is sent as a file or document — a distinction that is easy to get wrong in a hurry.

Email attaches the file you gave it, unchanged. Cloud storage links share the file you uploaded, unchanged. Neither strips anything.

The reliable approach is to strip before sending, rather than to rely on the recipient’s platform doing it for you.

When you should keep it

Stripping is not automatically the right answer. It is the right answer when a file is about to leave your control and the metadata serves no purpose for the recipient.

• Your own archive. Capture dates and camera settings are what make a photo library searchable years later.
• Journalism, insurance and evidence, where provenance is the point and stripping it destroys the value.
• Photography that you are publishing under your own name, where the Artist and Copyright fields are doing a job you want done.

Worked example: reading one photograph

A JPEG taken on a phone and loaded into the Image Metadata Privacy Tool typically shows something like this: a GPS block with latitude, longitude and altitude; DateTimeOriginal to the second; Make and Model naming the phone; a vendor MakerNote block of a few kilobytes; an orientation flag; and a colour profile.

Three of those matter for sharing. The coordinates place the photograph. The timestamp places it in time. The make, model and MakerNote tie it to one device.

The orientation flag and the colour profile are doing real display work. Removing the profile can shift the colours in a colour-managed viewer, which is why the tool keeps it and says so rather than removing everything and leaving you to discover the change.

Result: After removal the file reports no EXIF, no GPS and no XMP, and the byte count drops by the size of those blocks — typically a few kilobytes, occasionally far more when a large embedded thumbnail goes with them. The picture itself is unchanged, because nothing was re-encoded.

Open the tool

See what is in one of your own photos

Inspection runs in your browser and shows every field it found before you decide to remove anything.

What this does not cover

• Platform stripping behaviour changes without notice and is not something this page can promise on any platform’s behalf. Verify by stripping first.
• Removing metadata does nothing about identifying detail visible in the picture itself.
• The ToolAcre tool reads JPEG, PNG and WebP. It cannot inspect HEIC, TIFF or camera RAW.
• Vendor MakerNote contents are never decoded or displayed here; the block is removed whole.
• This is a privacy explanation, not security advice, and removing metadata makes no file safe.