photometadata.netEXIF · GPS · METADATA

What EXIF Data Does Facebook Store? (Check Image Metadata)

Short answer: Facebook removes almost all EXIF metadata — GPS, camera model, capture date — from the photo it shows to everyone else. But it reads that data first, and the original file you upload still contains everything. Below: what Facebook keeps versus strips, how to check whether it removed the EXIF from a photo you already posted, and how to view a photo's original metadata before you upload it.

The Short Answer

What other people can see: almost nothing. Facebook re-encodes every uploaded photo and strips the EXIF block from the version it serves publicly. Someone who downloads your photo from a post cannot read its GPS coordinates, camera model, or original capture date from the file.

What Facebook itself gets: the full original. Stripping EXIF from the public copy is not the same as never having it. Facebook receives the unmodified file you upload, reads the metadata it contains, and keeps the original on its servers. The location, timestamp, and device details that were in the file are data Facebook has — they are just not handed to other users.

The file on your device is unchanged. Uploading to Facebook does not edit your local copy. If you later share that same file by email, AirDrop, or message, the EXIF is still in it.

What Metadata Facebook Keeps vs. Strips

It helps to separate three different copies of your photo: the public copy other users can download, what Facebook holds internally, and the original file still sitting on your device.

EXIF fieldIn the public photo?Received by Facebook?
GPS coordinatesStrippedYes — read on upload
Original capture date/timeStrippedYes — read on upload
Camera make and modelStrippedYes — read on upload
Lens, aperture, ISO, shutter speedStrippedYes — read on upload
Facebook's own tracking tag (IPTC)Added by FacebookWritten into the served file
Faces in the imageNot EXIF — analyzed from pixelsProcessed on upload

One field actually gets added. Facebook writes its own identifier into an IPTC block in the file it serves (often visible as an FBMDmarker if you inspect the raw bytes). It is a handling/tracking tag, not your camera data — but it is a reminder that "strips metadata" does not mean "leaves the file untouched."

How Facebook Uses the Metadata It Reads

Removing EXIF from the public copy is a privacy default for other users— it stops strangers from pulling your home coordinates out of a photo. It does not put the data beyond Facebook's own reach. When you upload, the platform can:

  • Read embedded GPS to associate the photo with a place, even if you never added a location tag.
  • Use the capture timestamp to order photos and infer when an event actually happened, separate from when you posted.
  • Note the device from camera make/model, which contributes to the broader profile Meta builds across its apps.
  • Analyze the pixels themselves for faces, objects, and scenes — this is independent of EXIF and happens regardless of what metadata the file carries.

The practical takeaway: stripping happens on the way out, not on the way in. If you do not want Facebook to receive a field, the only reliable fix is to remove it from the file before you upload.

Facebook vs. Instagram vs. WhatsApp: EXIF Handling Compared

All three are owned by Meta, but they handle metadata a little differently depending on how a photo is sent:

PlatformEXIF in the shared copyNotes
Facebook (feed post)StrippedRe-encoded; adds its own IPTC tag. Original read on upload.
Instagram (post / story)StrippedSame pipeline. See our Instagram metadata guide.
WhatsApp (sent as "Photo")StrippedCompressed; EXIF removed from the compressed image.
WhatsApp (sent as "Document")KeptSends the original file as-is — full EXIF, including GPS. See does WhatsApp remove EXIF data.
iMessage (blue bubble)KeptDelivers your file as an attachment — GPS and camera data go with it. See does iMessage remove EXIF data.

The WhatsApp "Document" case is the one that trips people up: sending a photo as a file attachment instead of a normal photo preserves every EXIF field, GPS included. If you forward a photo that way, you are sharing the original metadata with whoever receives it.

How to Check if Facebook Removed Your EXIF Data

You do not have to take anyone's word for it — you can verify the stripping yourself on a photo you have already posted, in about a minute:

  1. Save the photo back from the post.Open your own post, then right-click the image and choose "Save image as…" on desktop, or long-press and save on mobile. This is the copy Facebook serves to everyone — the one that matters for what strangers can read.
  2. Open that saved file in an EXIF viewer. Drop it into our EXIF viewer — it reads the file in your browser, so nothing gets uploaded anywhere.
  3. Look for what should be missing. On a stripped file there is no GPSLatitude / GPSLongitude block, no Make or Model, and no DateTimeOriginal. You will usually still see basic image properties — pixel dimensions, color space — because those are part of the image itself, not the EXIF block.
  4. Expect Facebook's own tag instead. Many downloaded Facebook images carry an IPTC entry containing an FBMDmarker that Facebook writes on the way out. Seeing it is a good sign you really are looking at Facebook's re-encoded copy and not your original. The pixel dimensions are another clue — Facebook resizes on upload, so they often differ from the file you sent.
  5. If you still see GPS, you checked the wrong file. The usual causes: you opened the original from your own camera roll, or someone sent you the picture as a file attachment rather than you downloading it from the post. A file sent as a document is the untouched original, not Facebook's copy.

One caveat worth being clear about: a clean result proves the public copy is clean. It says nothing about what Facebook received. The original you uploaded still had every field in it, and that upload already happened.

How to View Original Photo Metadata Before Uploading

You cannot inspect Facebook's servers, but you can read the exact file it will receive — the original still sitting on your device. Whatever is in that file is what Facebook gets. Five minutes, no software to install:

  1. Start from the original, not a Facebook copy. This is the opposite of the check above: a photo downloaded back from a post is the stripped public version and will tell you nothing about what you handed over. Use the file in your camera roll or photo library, and not a screenshot of it (screenshots carry the screenshotting device's metadata, not the source photo's).
  2. Open it in an EXIF viewer. Drop the file into our EXIF viewer. It parses the file in your browser — nothing is uploaded to a server, so checking a sensitive photo does not put it online.
  3. Read the four fields that matter. GPSLatitude / GPSLongitude(plotted on a map — if a pin lands on your house, so does Facebook's copy), DateTimeOriginal (the second the shutter fired, not when you posted), Make and Model (your device), and Software (the editing app, and on some cameras a body serial number that links your photos to each other).
  4. Translate each field into what it reveals. A GPS pin plus a timestamp is a place-and-time record. Repeat it across an album and it becomes a pattern: where you live, when you are away from home, which device you shoot on. Facebook does not need to publish any of it to have it.
  5. Strip anything you would rather not hand over, then re-open the cleaned file in the viewer to confirm the GPS block is gone before you upload. Details in the next section.

Want to see what Facebook has already stored from past uploads? Its data export includes your uploaded photos with a metadata file alongside them, which for many photos records the upload IP address and the original capture timestamp. Open Facebook's settings and search for Download your information(it lives under Accounts Center, and Meta moves the menu around), request the "Posts" or "Photos and videos" category in JSON, and look at the media_metadata block in the export. Note that the export shows what Facebook chooses to give back, which is not necessarily everything it derived on upload.

See what Facebook will read before you upload.

Check any photo's GPS, capture date, and camera details in your browser — nothing leaves your device.

Open the EXIF Viewer

How to Sanitize Metadata Before Posting

Because Facebook reads the original on upload, the only way to keep a field out of its hands is to strip it from the file first. A few options, fastest first:

  • Use our metadata remover. Our remove metadata tool strips EXIF in the browser and gives you back a clean copy to upload. Nothing is sent to a server.
  • iPhone:in Photos, tap Share, then "Options" at the top, and turn off "Location." You can also remove location from the photo itself via the info panel. Full steps in our iPhone EXIF guide.
  • Android: turn off location saving in the camera app, or remove it per-photo in Google Photos. See our Android EXIF guide.
  • Disable geotagging at the source. If you turn off location for the camera app, new photos never get GPS in the first place — nothing to strip later.
  • Run through a pre-share checklist. Our strip metadata before sharing guide walks through what to check and clear before a photo leaves your device, whatever platform it is headed to.

Facebook is one destination among many, and the rules differ by platform — some strip on upload, some pass your file through untouched. X works the same way Facebook does, minus the added tracking tag: what EXIF data Twitter/X stores has the field-by-field breakdown. Our photo privacy guide covers which is which, and what a photo can give away beyond the EXIF block.

Related Guides

Frequently Asked Questions

Does Facebook remove EXIF data?

Yes — from the version Facebook serves publicly. GPS, capture date, camera model, and exposure settings are all stripped from the copy other people can download. It does not edit the original file on your device, and it does not stop Facebook from reading the metadata on upload. Facebook also adds its own IPTC tracking tag to the served image.

Does Facebook store GPS from photos?

Facebook strips GPS coordinates from the photo it shows other users, so strangers cannot read your location from a downloaded copy. But Facebook receives the original file when you upload and can read the embedded GPS for its own use. If you do not want Facebook to have the coordinates at all, remove them from the file before uploading.

How do I check if Facebook removed my EXIF data?

Save the photo back from your own post — right-click and "Save image as…" on desktop, or long-press on mobile — and open that saved file in an EXIF viewer. On a stripped file there is no GPS block, no camera make or model, and no original capture date; you will often find an IPTC entry with an FBMD marker that Facebook added instead. If GPS is still there, you almost certainly opened your original file rather than the copy downloaded from Facebook.

Can someone find my location from a photo I posted on Facebook?

Not from the EXIF of a normal feed photo — Facebook strips the GPS before serving it. The risks that remain are a location you manually tagged, recognizable landmarks visible in the image itself, or a copy of the original file shared somewhere that does not strip metadata.

How is this different from WhatsApp?

WhatsApp strips EXIF when you send a picture as a normal "Photo," just like Facebook. But if you send the same image as a "Document," WhatsApp transfers the original file untouched — full EXIF, including GPS. Facebook feed posts are always re-encoded and stripped.

How do I check photo metadata before uploading?

Open the original file — not a screenshot, and not a copy downloaded back from Facebook — in an EXIF viewer. It will show GPS coordinates, the original capture date, and camera details — exactly the data Facebook receives on upload. If you want to keep any of it private, strip it with our remove metadata tool first.