Does Facebook Remove EXIF Data?

Yes — Facebook removes EXIF data from the photos you upload to your feed, timeline, album, and group photos. The image is decoded and re-encoded on Facebook’s servers, so GPS coordinates, capture timestamps, camera make and model, lens data, exposure settings, and serial numbers do not survive into the copy other people see or download. The two places the original file can still leak are Facebook’s file upload surfaces (including the Files tab in Groups) and the wider Marketplace economy, where original-resolution files routinely circulate outside Facebook’s re-encoding pipeline.

What Facebook does on upload

Like Instagram, Facebook does not surgically remove individual EXIF keys. It rebuilds the image:

1. The original file is uploaded.
2. The server decodes it to pixels.
3. The pixels are resized, cropped, and colour-processed to Facebook’s own output profile.
4. A fresh JPEG is encoded, with Facebook’s own container fields written into it.

Your original metadata is therefore never copied forward — the EXIF APP1 segment, XMP packet, IPTC block, and embedded thumbnail are replaced rather than filtered. The copy you download from facebook.com is a new file.

Facebook may write its own generated fields into the served image, for example copyright/IPTC-style bookkeeping entries or a small XMP packet identifying the asset. Those are platform-generated rather than your original camera data, but they are still present in the file — another reason to check the file instead of assuming “clean” means “empty”.

Facebook vs Instagram vs other platforms

Behaviour differs per platform and per upload mode. The table below reflects widely documented behaviour as of the time of writing; platform pipelines change without notice, so treat it as a strong prior and verify.

Platform	Standard image upload	What happens	Original EXIF in the served copy
Facebook (feed, albums, groups)	Photos	Decoded and re-encoded	Removed
Facebook Groups -> Files	Any file	Stored as an attachment	Preserved - downloadable as uploaded
Facebook Marketplace listing photos	Photos	Same re-encode pipeline as feed	Removed
Instagram (posts, carousels, Stories)	Photos/video	Re-encoded or transcoded to video	Removed
Instagram direct messages (sent as a file)	Attachment	Delivered as a file	Often preserved - verify on receipt
WhatsApp - sent as a photo	Photo	Compressed and re-encoded	Removed
WhatsApp - sent as a document	File	Sent byte-for-byte	Preserved
X / Twitter	Photo	Processed and re-encoded by the upload pipeline	Removed in the standard app; some integration and API paths have historically differed
Discord - image attachment	Image	Attachment proxy recompresses to a web image	Removed
Discord - uploaded as a file	File	Stored as-is	Preserved
Telegram - sent as a photo	Photo	Compressed to JPEG	Removed
Telegram - sent as a document	File	Stored and served unmodified	Preserved

The rule behind the table: any surface that treats your image as a “file” rather than a “photo” hands over the original bytes. Compression-based messaging apps are the classic example — the same photo sent two ways behaves completely differently.

Where behaviour is uncertain, assume the metadata is still there. The cost of that assumption is a five-second check; the opposite assumption costs you your home address.

Where the original file can still leak

Facebook Groups file uploads

This is the most direct leak path on Facebook itself. Groups have a separate Files tab where any member can upload a document, archive, or image and other members download it. Those attachments are stored as ordinary files, not as processed Facebook photos, so a file uploaded that way can carry the full EXIF block of the original photograph, including the GPS coordinates and the camera serial number. The same applies to anything uploaded through the Files tab of a Messenger chat. If you need to hand someone a high-resolution or lossless copy, that is exactly what will happen — and exactly why you should strip it first.

Marketplace, and where the original file really escapes

Marketplace listing photos go through the same re-encoding pipeline as feed photos, so the pictures attached to a listing are normally metadata-free. The real leak is one step removed:

• Sellers routinely attach the original file outside Facebook — a Google Drive or Dropbox link, a photo hosted on their own site, a WeTransfer link — so the buyer can get maximum resolution. Those are the untouched originals, metadata and all.
• Buyers often ask for “the original photo” in the comment thread. Answering that request with the camera file hands over the coordinates.
• Order receipts, invoice PDFs, and shipping documents are frequently attached to the purchase, and a PDF built from your phone photos can embed those images with their EXIF intact.
• The moment a file leaves Facebook for a direct-message channel or an external link, Facebook’s stripping no longer applies to it at all.

If you sell on Marketplace, treat every listing photo as a candidate for the “original please” follow-up, and pre-empt it by sanitising the file you send.

Facebook still knows things EXIF never told it

Stripping a file’s metadata does not make a post anonymous. A photo post still reveals the account behind it, the caption and hashtags, any check-in or location tag, Facebook’s own generated labels and alt text, and behavioural signals about when and to whom you posted. None of these live in the file; they live in Facebook’s database and are reachable through the API. If your concern is “a stranger learns my home address”, a location tag on the post is a more direct route than EXIF.

Always check the original file, not the re-hosted copy

This is the single most important habit for anyone testing metadata behaviour, and it is where most online advice goes wrong. Inspecting the copy on facebook.com tells you what Facebook’s CDN did. It tells you nothing about the file still in your camera roll — the one that will be attached to a PDF, AirDropped, emailed, or listed on Marketplace tomorrow.

A workable routine:

1. Inspect the original with the freexifdata EXIF viewer — read-only, entirely in your browser, nothing is uploaded.
2. Use the GPS photo checker if location is the specific concern.
3. Sanitise before you send, using remove EXIF data, and keep a note of the settings you care about — camera model, lens model, date time original, orientation — if you want them preserved.
4. Cross-check the platform copy only as a secondary test, never as a substitute for step 1.

A note on what “remove” means in a browser: the technique is to render the decoded pixels onto an off-screen canvas and encode a new image from that canvas, which physically cannot carry the old header across. You get a clean file in exchange for a re-encode, which for most web images is invisible. The EXIF tag reference lists what each field tells you before you decide what to keep.

Caveats and honest limits

• Facebook’s pipeline has changed repeatedly over the years, including periods when metadata behaved differently for different surfaces. The table above is a summary of documented behaviour, not a contractual guarantee, and we do not run a live test suite against Meta’s infrastructure.
• Third-party tools that scrape Facebook (downloaders, mirrors, archiving services) serve Facebook’s processed copy but frequently re-wrap it with their own metadata — a new filename, a source URL, a “downloaded by” comment. That is not original EXIF, but it does leak information about who fetched the file and when.
• Some mobile apps export with EXIF intact or re-inject the fields they read, so the file you choose in the share sheet may not be the file the camera produced.
• “Uploaded as a document” behaviour is the least stable area across all of these apps. Verify the received file rather than trusting the send button.
• Facebook’s own systems read metadata during the upload sequence before it is stripped: the stripping protects the published copy, not the platform’s processing of the original.