Does Facebook Remove EXIF Data?

The short answer

Facebook re-encodes uploaded photos to its own compression settings and sizes, and the images it serves back are generally stripped of EXIF, including GPS coordinates. Someone who downloads your photo from a Facebook post will typically not find camera or location tags in it.

That is a genuine reduction in what other users can see. It is not the same as the metadata never having existed — and it is not the same as the file being empty, because Facebook writes a few fields of its own.

What a photo downloaded from Facebook still contains

Open a photo saved from Facebook in a metadata viewer and the camera's EXIF is gone: no make, model, lens, exposure, original date or GPS. What you usually find instead is IPTC data that Facebook added.

IPTC, the standards body behind that format, investigated in 2019 and found Facebook writing values into two IPTC fields of the images it serves — Special Instructions and Original Transmission Reference — that matched nothing in the uploaded file. The Special Instructions value is a string beginning "FBMD" followed by a long run of hexadecimal characters. IPTC's test also found the value unchanged when the downloaded image was uploaded a second time.

Load a photo you saved from Facebook into the remover on this site and those fields appear in the list, ready to be removed like any other.

Does that code identify who uploaded it?

Nobody outside Meta knows. Facebook has not publicly documented what the FBMD string encodes, and it cannot be decoded from the file. Security researchers have suggested it lets Facebook recognise an image when it reappears, and so link copies back to an upload, but that is inference rather than anything Meta has confirmed.

What is certain is narrower: the string is an identifier Facebook added, it is not in your original photo, and it travels with every copy saved from Facebook unless someone removes it. Removing IPTC data deletes it without touching the picture.

What the distinction means

There are two audiences for your photo's metadata: other users, and the platform. Re-encoding addresses the first. The second still received your original file, complete with whatever it contained, and any platform is free to read and retain what it likes from it, subject to its own policies and applicable law.

If your concern is that a stranger downloading your holiday photo could read its coordinates, uploading to Facebook largely handles that. If your concern is what the company itself holds, it does not.

What Meta says it collects

Meta does not publish a separate policy on EXIF. Its data policy has long said that the information it collects from what you share includes information in or about the content, "like metadata", such as the location of a photo or the date a file was created.

So the stripping you see on the served image is about what other users can read. The location and time recorded by your camera reached Meta with the upload, and what happens to them afterwards is governed by its policies, not by anything visible in the file you get back.

The paths where metadata survives

Stripping is a side effect of re-encoding, and not every path re-encodes. Behaviour changes over time and by product surface, so these are the places worth checking rather than assuming:

• Files sent as attachments or documents in Messenger rather than as photos
• Downloads of your own data through Facebook's data export, which return originals
• Third-party apps and cross-posting integrations that hand your file on unchanged
• Any surface that offers a 'original quality' or 'send as file' option

Why photography groups can't see your settings

Photographers in Facebook groups often ask why nobody can read their shutter speed, aperture or lens. The answer is the same re-encode: the copy Facebook serves has no EXIF, so the settings that came from your camera are not in it, and Facebook does not display EXIF anywhere either.

If you want to share settings, put them in the caption. If you want to keep them private — some photographers do, for client work or technique — the re-encode already does that for the public copy, and cleaning the file before upload does it for the original as well.

The practical recommendation

Clean the file before uploading. It takes a few seconds, it costs nothing, and it makes the outcome independent of a platform policy that can change without you noticing.

This applies across services: the reasoning is identical for Instagram, X, LinkedIn and any other platform, because the variable is their re-encoding behaviour rather than anything about your file.