MetaPurge

Facebook photo metadata: what is stripped and what is not

As of writing, Facebook does not display your camera's EXIF on a post, and it does not publish your GPS coordinates from the file. Both of those statements are true. Neither one means the photo you uploaded is clean.

By Rajat Malik Updated 6 min read

"Facebook strips metadata" is one of those claims that is broadly right and practically misleading. It describes what happens to the copy Facebook builds for display. It says nothing about the file on your phone, the file in your backup, or the copy someone downloaded and re-uploaded somewhere else.

To reason about it properly you have to stop thinking about "the photo" and start counting copies. Each copy has its own metadata state, and only one of them is the one you started with.

What people mean by "stripped"

What actually happens on upload is a rebuild. Facebook decodes the image, resizes it for the layouts it serves, and re-encodes it into new files at several sizes. Those files are what viewers see, and they are not your upload.

A rebuild normally produces a minimal metadata block written by the encoder. Camera GPS, lens and body serials, the original capture timestamp and any editor history are not needed for display, so they are not carried over. As of writing that is the observable behaviour, but it is a property of the pipeline, not a promise in a policy document.

The copies, and what each one holds

This is the table worth keeping in mind. The platform copy is clean because it was rebuilt. The other copies were not.

CopyWhere it livesMetadata state
Your original upload Phone, camera roll, desktop folder, device backup Everything the camera wrote, unchanged
Facebook's displayed copy Feed, photo viewer, embeds Re-encoded; camera tags largely gone
A download from Facebook Saved to whoever downloaded it The processed copy, not your original
A shared album entry Album view, uploaded by someone else Processed from whatever that person uploaded
A screenshot of the post The viewer's device Pixels only; none of the original tags
Account data export Archive downloaded from settings Can include original uploads, sometimes old ones

Location is a post field

When you tag a post with a place, you are filling in a field on the post. It is stored as part of the post, alongside the caption and the audience setting. It is not read from the photo's EXIF, and it is not written back into the image that gets served.

So the location you see on a Facebook post and the coordinates inside your JPEG are two unrelated disclosures. Adding a place does not expose the file's GPS tag. Removing the file's GPS tag does not remove the place you tagged. If you want neither, you have to deal with both.

Different fields, different lifetimes Editing or removing a location on a post changes the post field. It does not touch the file you uploaded, and it does not reach copies other people already saved.

The gap: platform copy versus your file

The reassuring version of the story stops at the displayed copy. The complete version continues to the file that is still sitting in your camera roll with the coordinates intact, and to every place that file has already been: cloud backups, shared folders, messaging apps, a laptop that syncs to a drive.

That gap becomes concrete the moment the same image is used somewhere else. The file you uploaded to Facebook is also the file you can attach to an email, drop into a group chat, or hand to a marketplace listing. Those routes do not rebuild anything. The metadata that Facebook's pipeline discarded is still there, ready to travel.

There is a second gap, too: the copy you download from Facebook is not your original. If you clean a downloaded copy and call it a day, you have cleaned the wrong file — the source of truth on your device is untouched.

Downloads, shared albums and screenshots

Downloads inherit the processed copy, which is usually good news for GPS and bad news for quality. Shared albums are a different arrangement: the photos belong to whoever added them, and each was processed from that person's upload. If a friend adds your picture to an album, the metadata state depends on the file they had, not on the one you posted.

Screenshots are the strangest case. They carry no EXIF from the original image at all, because they are a new capture of a screen. Everything visible is preserved, including a street sign, a reflection, a document in the background. People treat a screenshot as a safe way to re-share a photo; it is safe for coordinates and unsafe for content.

If you need a copy that is genuinely clean, clean the original. Do not rely on a platform's derivative and do not rely on a screen capture.

How to check a copy for yourself

Take a photo with location services enabled, confirm the coordinates are present with a metadata reader, upload it, then download it again through the platform's own download option. Inspect that download. If the coordinates are gone, you have verified the feed path on your account, with your app version, on that day.

Repeat the check after a major app update or if you change how you upload. Platforms change their media handling without announcing it, and a result from last year is a data point rather than a guarantee. The same applies to any album or group you use, since those can involve different upload paths.

Clean the file, not the post

The durable fix is to remove metadata before the file leaves your device. Nothing visible changes: the same pixels, the same framing, the same colours, once Orientation and the ICC profile are kept. What goes away is the GPS block, the serial numbers, the original timestamps and the software history.

Then the platform copy and the original agree, and it no longer matters which one someone downloads. If you want to know what a file holds before you decide, read the tag list first — the check is local and changes nothing.

See what your photos are carrying

Drop an image in. MetaPurge lists every tag, then rewrites the file without touching a pixel.

Open the metadata remover

Where to go next

Rajat Malik Frontend architect and the author of MetaPurge. Builds browser tools that keep files on the device, and writes about the parts of the web that leak by default. rajatmalik.dev