ID photo metadata: what the file reveals

You already know that a passport data page shows your document number, date of birth and signature — that is the part everybody weighs up before hitting send. What almost nobody weighs up is that a photo is a file, and files carry a second set of data that nothing on screen reveals.

What is actually inside the file

Digital cameras and phones write structured metadata into the image using Exif, the Exchangeable image file format standardised as CIPA DC-008. A typical smartphone photo carries:

the capture date and time, usually with the local UTC offset, so the file states both when and in which time zone you were;
the make and model of the device, and in some camera bodies a serial number that ties every photo from that camera together;
lens and exposure settings, harmless on their own but useful for correlating one file with another;
the software that last wrote the file, which quietly announces that the image was edited;
GPS latitude and longitude, if location services were enabled for the camera.

Why the GPS field matters more than the rest

Because a photo of an identity document is almost always taken somewhere meaningful. You lay the passport on a table at home, or on a desk at work, and press the shutter. Consumer GPS is typically accurate to a few metres, so the coordinates do not describe a neighbourhood — they describe a building.

Put differently: a location-tagged photo of your passport hands the recipient your document and your home address, and does it without anyone deciding to disclose it. The ICO makes the same point in its guidance on disclosing information safely, which gives Exif its own section precisely because photographs from phones and tablets “can include the GPS coordinates of where the image was taken as well as other data about the device”.

The redacted photo that is not: the embedded thumbnail

This is the single most important thing on this page.

A JPEG does not contain one image. The Exif structure records the primary image in one directory and, separately, a small thumbnail in another, generated at capture time so that gallery apps can render a grid without decoding full-size files. Some editors update the main image and copy the metadata block across unchanged — which means the old preview rides along.

The consequence is uncomfortable: you can black out the document number, save the file, look at it, see the black box, and still be shipping a small, legible copy of the unredacted frame inside the same file. It is not hypothetical and it is not rare in older toolchains.

There is one reliable way around it. Do not edit an existing photo in place and hope. Export a new, flattened image — a file written from pixels — so there is no inherited metadata block and no stale preview to inherit. That is also the ICO’s advice for image redaction generally: export to a simple un-layered format so the redactions are permanent. The wider version of that argument is in blurring an ID photo manually versus using an app.

What about screenshots and screen recordings?

A screenshot has no lens and no GPS fix, so it carries no coordinates. It does normally record the device model, the operating system and the time, which is enough to link files to one device.

The real exposure in a screenshot is not metadata at all — it is the frame. A screenshot of a chat window carries the surrounding messages, the contact name, often a phone number, and the notification banner that happened to be on screen. People send screenshots because they feel more casual than a photo. They are frequently worse.

Which channels strip metadata, and which do not

Be careful here, because the honest answer is “it depends on the exact send path”, and the failure is silent — nothing tells you which one you used.

Channel	Does it strip metadata?	What to do
WhatsApp, Signal, Telegram sent as a photo	Usually yes — the image is re-encoded	Do not rely on it; verify once with a test file
The same apps, sent as a file / document	Usually no — original bytes are preserved	Strip before sending
Email attachment	No	Strip before sending
AirDrop, Quick Share, Bluetooth	No	Strip before sending
Cloud-drive link (Drive, Dropbox, iCloud)	No	Strip before sharing the link
Large social platforms (upload)	Usually yes — re-encoded on upload	Irrelevant: never post an ID at all
Upload form on a company’s website	Depends entirely on that site	Assume no

Spain’s national cybersecurity institute, INCIBE, sets out the same split in its explainer on what is hidden behind a photo: the big messengers and social networks drop metadata, while cloud storage services do not.

The working rule is simple. Assume the metadata is preserved unless you know otherwise for that exact route, because the cost of being wrong is one-directional.

Why this is a data-protection question, not just a privacy nicety

Metadata that relates to an identified or identifiable person is personal data in its own right. Article 4(1) of the GDPR defines personal data as any information relating to such a person, and names location data explicitly among the identifiers that make someone identifiable.

That matters in two directions. For you, a location-tagged ID photo is a bigger disclosure than the document alone. For the recipient, it is a bigger holding — more personal data, retained longer than they realise, on an inbox server nobody is actively managing. If you are asking a company to delete a copy afterwards, this is part of what you are asking them to delete: see can a company legally keep a copy of your ID.

How to check what your photo is carrying

Take one minute and look, once, at a photo you have already sent. It changes how you treat the next one.

macOS — open in Preview, then Tools → Show Inspector. The (i) tab lists Exif; a GPS tab appears with a map if coordinates are present.
Windows — right-click the file → Properties → Details. The same dialog offers Remove Properties and Personal Information, which writes a cleaned copy.
iPhone — open the photo in Photos and swipe up or tap the info button. To strip on send, use the share sheet → Options at the top → switch Location off.
Android — open the photo in Photos and tap Details; location can usually be removed there or in the share sheet.
Terminal — exiftool photo.jpg lists everything; exiftool -all= photo.jpg removes every block, thumbnail included.

If you have already sent files without checking, the practical follow-up is in you already sent an unredacted ID copy — and the same request that asks a recipient to delete the image covers its metadata too.

The one-step version

All of the above collapses into a single habit: never send the original camera file. Send a copy you generated. Redact the fields that matter, watermark it for the recipient as described in how to watermark a copy of your ID, and export it as a flat image. The new file has no inherited coordinates, no camera serial, no capture time and no stale thumbnail, because none of that was ever written into it.

That is why the channel question in is it safe to send your ID over WhatsApp or email matters less once you fix the file — and why a full-fidelity original is the wrong thing to be sending in the first place, whatever the reason you are sending it. The fields on the document are only half of what you are handing over; see can someone steal your identity from an ID photo for the other half.

Anonymize my ID produces a newly generated, flattened image on the device, so the original capture metadata — coordinates included — does not ride along with the copy you send.

Check and strip the metadata before you send an ID photo

Look at what the file is carrying. On macOS, open the image in Preview and choose Tools → Show Inspector, then the (i) and GPS tabs. On Windows, right-click the file → Properties → Details. On iPhone, open the photo in Photos and swipe up or tap the info button; on Android, open it in Photos and tap Details. If you see a map, coordinates, or a camera serial number, the file is carrying more than the document.
Check the thumbnail, not only the main image. If you have edited or covered fields in an existing photo, the embedded preview may still show the original frame. In a terminal, exiftool -b -ThumbnailImage photo.jpg > thumb.jpg extracts it so you can look at it. If you cannot check, do not send an edited file — send a freshly exported one.
Turn off location at share time on mobile. On iPhone, use the share sheet, tap Options at the top, and switch Location off before sending. On Android, the share sheet or Google Photos offers a comparable option on most devices, and you can also delete the location from the photo's Details panel.
Remove file properties on Windows. Right-click the image → Properties → Details → Remove Properties and Personal Information, then choose to create a copy with all possible properties removed. Send that copy rather than the original.
Strip everything with exiftool if you are comfortable in a terminal. exiftool -all= photo.jpg removes every metadata block, thumbnail included, and keeps a backup of the original alongside it. Verify with exiftool photo.jpg that nothing is left beyond the basic image dimensions.
Or simply export a new flattened image. Re-exporting a redacted, flattened copy generally writes a new file from the pixels and leaves the original capture metadata behind. Send that file, and delete the original photo from the chat or draft once the recipient has confirmed receipt.

Frequently asked questions

What metadata does a photo of my ID contain?

Typically the capture date and time with the local UTC offset, the make and model of the phone or camera, lens and exposure settings, the software that last wrote the file, and — if location services were enabled for the camera — GPS latitude and longitude. Some camera bodies also record a serial number. A JPEG usually stores a small embedded thumbnail of the image as well.

Can someone find my home address from an ID photo?

If the photo carries GPS coordinates and you took it at home, yes — the coordinates are typically accurate to within a few metres, and pasting them into any map gives the building. This is why a passport photographed on a kitchen table is a bigger disclosure than the document alone. Turning off location for the camera, or stripping the metadata, removes it.

Does WhatsApp remove the metadata from photos?

Sending an image as a photo generally re-encodes it and drops the Exif block, and most large social platforms do the same. Sending the same image as a document or file usually preserves the original bytes intact, as do email attachments, AirDrop and cloud-drive links. Because the difference is invisible from the sender's side, treat metadata as preserved unless you have checked.

Can a redacted photo still contain the unredacted version?

It can. The Exif standard stores a thumbnail separately from the main image, and some editors rewrite the main image while copying the old metadata across unchanged — leaving a small but legible preview of the original frame inside the file. Exporting a new flattened image, rather than editing an existing one in place, avoids this entirely.

Do screenshots have metadata?

Screenshots carry no GPS coordinates, because nothing was captured through a lens, but they do usually record the device model, the operating system and the time. The bigger problem with a screenshot is what is in the frame: a screenshot of a chat shows the surrounding messages, the contact name and often the phone number.

Is photo metadata personal data under the GDPR?

Where it relates to an identified or identifiable person it is, under the definition in Article 4(1). Location data is named in that definition as an identifier, so a location-tagged ID photo sitting in a recipient's inbox is a larger disclosure than the document by itself, and their obligations over it are correspondingly larger.

What a photo of your ID gives away besides the ID

Short answer