Skip to content
Privacy5 min read

What your photos reveal about you — and how to remove it

Every phone photo carries hidden data, often including exactly where it was taken. What is in there and how to strip it before you post.

By Shekhar P ·

Take a photograph on a phone and you record more than the image. Embedded in the file, invisible unless you go looking, is a block of metadata describing when the photo was taken, what took it, the exact camera settings — and, on most phones by default, the precise latitude and longitude of where you were standing.

That last one is the reason this matters. The coordinates are typically accurate to within a few metres. Photograph something in your living room, post the file somewhere that preserves metadata, and you have published your home address to anyone who thinks to look.

What is actually in there

The standard is called EXIF — Exchangeable Image File Format — and it has been embedded in photographs since the late 1990s. A typical phone photo contains something like this:

FieldTypical value
Date and time2026-03-14 18:42:07
GPS latitude / longitude51.5014, -0.1419
GPS altitude23m
Camera make and modelApple iPhone 15 Pro
LensMain camera, 24mm f/1.78
Exposure, ISO, aperture1/120s, ISO 400, f/1.78
OrientationRotate 90° clockwise
Software17.4.1

Some cameras add more: a serial number, the owner name if it was set, and on some phones a thumbnail of the original image — which survives even if you crop the visible photo, a fact that has caught out more than one person who cropped something out and published the file anyway.

Why the location field is the dangerous one

The other fields are mostly harmless. The coordinates are not, for three reasons.

They are precise. Not "London" but a specific point, usually within a few metres. Precise enough to identify a building, often a specific room.

They accumulate. One photograph gives one location. A collection of photographs from the same account gives a pattern: where someone lives, where they work, what time they leave, where their children go to school. No single photo reveals that; a year of them does.

Nobody expects them. A photograph of a sofa does not look like a document containing your address, which is exactly why people post it.

The classic case is the online marketplace listing. Someone photographs an item at home, posts it, arranges to meet a buyer in a public place for safety — and the listing photo already told the buyer where they live.

Which platforms strip it, and which do not

This is the part where the advice usually goes wrong, because it varies by platform and changes over time.

Generally stripped: Facebook, Instagram, X and most large social networks remove EXIF when processing uploads. They do this for bandwidth reasons as much as privacy — and note that removing it from the public copy does not mean they did not read it first.

Generally preserved: email attachments, cloud storage links, messaging apps sending "as a file" rather than as a photo, most forums, most marketplace and classified sites, and anything you upload to a personal website or blog.

Varies: WhatsApp and similar apps usually strip metadata when sending as a photo but preserve it when sending as a document. This distinction catches people out constantly, because the file arrives looking identical either way.

The safe assumption is that metadata survives unless you know otherwise. Strip it before uploading rather than relying on the recipient's platform to do it.

How to check what a photo contains

Before removing anything, it is worth looking once — the reaction to seeing your own coordinates is more persuasive than any article.

On Windows: right-click the file, Properties, Details tab. Scroll to the GPS section.

On macOS: open in Preview, then Tools → Show Inspector, and choose the GPS tab.

On iPhone: open the photo, swipe up or tap the info button. If location was recorded, a map appears.

On Android: open in Google Photos, tap the info button. Location shows as a map if present.

If you see a map, that file contains your coordinates.

How to remove it

Several approaches, depending on what you are doing.

Turn it off at the source. The most reliable fix is not recording it in the first place. On iPhone: Settings → Privacy & Security → Location Services → Camera → Never. On Android: open Camera, then settings, and disable location tags. You lose the ability to see photos on a map in your library, which some people value — this is a genuine trade-off rather than a pure win.

Strip it from existing files. On Windows, right-click → Properties → Details → "Remove Properties and Personal Information" creates a cleaned copy. On macOS, Preview's inspector lets you remove location data directly.

Re-encode the image. This is the approach most people end up using without realising. Any tool that decodes an image and re-encodes it produces a file with no metadata at all, because the metadata is not part of the pixel data and is simply not carried across.

That means resizing, compressing or converting an image strips EXIF as a side effect. If you were going to compress the photo before uploading it anyway — which you probably should be, for size reasons — the metadata problem solves itself. The same applies to the resizer and the converter.

One caution with online tools here: if the point is to remove sensitive location data, uploading the file complete with that data to someone else's server to have it removed is a slightly odd sequence of events. Use something that processes locally, or do it on your own machine.

Screenshots have their own problem

Screenshots do not carry GPS coordinates, but they carry something arguably worse: whatever was on screen.

The recurring failures are worth naming. Browser tabs showing pages you did not mean to share. Notification banners arriving mid-capture. Autocomplete suggestions in a search box. A taskbar showing which applications are open. Account names, email addresses and partial card numbers in the corner of an otherwise innocuous capture.

Cropping helps, but crop properly rather than covering. Drawing a black box over something in an image editor and saving as PNG usually works — but not always. There have been repeated incidents where a "redaction" was applied as a layer that could be removed, or where a pixelation was reversible enough to recover the text underneath. If something genuinely must not be readable, crop it out of the image entirely rather than covering it up.

A short checklist before posting

Worth running through for anything going somewhere public.

  1. Was it taken at home, or somewhere you do not want identified? If so, strip the metadata.
  2. Is it a marketplace listing? Always strip. This is the highest-risk category.
  3. Does the frame contain anything you did not intend? Reflections in windows and mirrors, documents on a desk, screens in the background, house numbers, vehicle plates, school uniforms.
  4. Is it a screenshot? Check the edges — notifications, tabs, taskbar, account name.
  5. Are you sending as a photo or as a file? In messaging apps these behave differently.

The reasonable position

None of this means metadata is bad. It is genuinely useful: it lets you sort a photo library by date, find pictures from a particular trip, and remember which lens produced a shot you liked. Photographers rely on it.

The problem is not that it exists, it is that it is invisible and travels with the file by default. Keep it in your own library, where it is useful. Strip it from anything that leaves — which, conveniently, is usually the same moment you were going to resize the photo anyway.

More reading

← All articles · 10 published