Do Instagram, Facebook & WhatsApp Remove EXIF Data?
Which apps strip photo metadata on upload and which preserve it — Instagram, Facebook, X, WhatsApp, iMessage, email, AirDrop — in one table, plus how to check a file yourself.
Social platforms strip metadata; original-file channels don’t. Instagram, Facebook, X/Twitter and Discord re-encode every uploaded image and drop the EXIF block entirely. Email attachments, AirDrop, iMessage, and WhatsApp/Telegram’s “send as document” deliver your original file — GPS coordinates included. The question isn’t “does this app keep metadata” — it’s “does this channel re-encode my file?”
The landscape
| Channel | EXIF/GPS survives? | Why |
|---|---|---|
| Instagram / Facebook / X / Discord post | No | image is re-encoded server-side for display |
| WhatsApp or Telegram — sent as photo | No | compressed copy replaces the original |
| WhatsApp or Telegram — sent as document/file | Yes | original bytes are attached untouched |
| Email attachment (Gmail, Outlook, Apple Mail) | Yes | the file itself is attached, not re-encoded |
| AirDrop | Yes | transfers the original file; iOS Options can exclude photo data |
| iMessage | Yes | full-quality send keeps the EXIF block (share-sheet Options → Location off strips it) |
| Google Photos / Drive / Dropbox link | Yes | downloads are the original upload |
| SMS/MMS | Usually no | carrier-level recompression tends to strip, but varies |
| Screenshot you send onward | No GPS | the screenshot is a new file — though the pixels can still leak location |
The pattern underneath
Re-encoding is the rule that decides it. Any channel that rewrites your image for bandwidth or display — feed posts, compressed sends, thumbnails — destroys the metadata block as a side effect. Any channel that treats your photo as a file — attachments, documents, AirDrop, download links — preserves everything, because nobody touched the bytes.
Two traps worth knowing
The “safe app” assumption. Because Instagram strips metadata, people assume every share path does. The catastrophic version is emailing a home photo to a marketplace buyer, or “sending as document” in WhatsApp to be helpful — both deliver street-level GPS. Strip the file first when the channel is file-faithful.
Asymmetry within one app. WhatsApp alone has both behaviors depending on which attach button you tap. iOS adds a per-share lever: the share sheet’s Options row controls Location and All Photos Data — worth checking before every AirDrop. When in doubt about what a file still carries, drop it in the viewer — parsing happens locally, nothing uploads — and for what a stripped file can still reveal, see what EXIF reveals.
Frequently asked questions
Does Instagram remove EXIF data from photos?
Yes — Instagram re-encodes every uploaded photo server-side, and the re-encoded image carries no EXIF block: no GPS, no camera model, no timestamps. What your followers can download is a stripped derivative. The same applies to Facebook uploads.
Does WhatsApp remove location data from photos?
When you send a photo as a photo, yes — WhatsApp compresses it and the metadata goes with the re-encode. But send as document (Attach → Document) delivers the original file byte-for-byte, GPS tags included. Same split on Telegram: compressed photo = stripped, sent-as-file = preserved.
If I email a photo, does the metadata survive?
Yes — attachments are the original file, byte-identical, GPS and all. This is the most common accidental leak: people assume 'sharing' strips metadata because Instagram does, but email isn't Instagram. Strip the file before attaching, or use the share-sheet option that excludes photo data.
Does iMessage keep photo metadata?
Generally yes — iMessage sends full-quality originals and the EXIF block (including location) travels with it. The sender can remove it: in the iOS share sheet, tap Options at the top and turn off Location / All Photos Data. Recipients can check what arrived by dropping the saved image into the viewer.
Does taking a screenshot of a photo remove its EXIF?
Yes — a screenshot is a new image file with no GPS block (phones don't geotag screenshots), so it's a crude-but-effective strip. The trade-offs: quality drops, the screenshot's own filename betrays capture time and OS, and whatever was on screen — status bar, notifications, open tabs — becomes part of the image. See what screenshots actually record.
Is there a reliable way to know if a channel stripped my photo?
Test it once: send a photo you took at home through the channel, have the recipient save it (not screenshot it), and run it through the EXIF viewer. If GPS fields appear, the channel preserves metadata. Platform behavior changes over time — a 30-second test beats any table, this one included.