Photos to grandparents
Texted from a beach. The kids' GPS, the iPhone's serial, and the timezone arrive in grandparents' iCloud backup along with the smile.
iMessage, email, AirDrop, and most "send as file" flows are strict pipes — they hand the receiver the same file you attached, metadata and all. That's how a casual photo of the kids on a weekend afternoon arrives in someone's inbox with the exact GPS of the playground, your iPhone serial, and an embedded thumbnail of the version before you cropped a face out.
Strict pipes vs. soft strips
| App / channel | Behavior |
|---|---|
| iMessage / Messages | Original metadata preserved (by design) |
| WhatsApp (Photo mode) | Re-encoded — most EXIF dropped as side effect |
| WhatsApp (Send as file) | Preserved — full metadata reaches recipient |
| Signal | EXIF stripped, image re-encoded (privacy-first) |
| Telegram (Photo mode) | EXIF stripped on most paths |
| Telegram (Send as file) | Preserved |
| Email (Gmail, Outlook, Apple Mail) | Preserved — attachment is byte-identical |
| AirDrop / iCloud Drive | Preserved — that's the feature |
| Discord, Slack DM | Generally preserved |
The privacy-first apps (Signal especially) do the right thing — but every other app on this list is a strict delivery pipe by default, sometimes with a "send as file" escape hatch that bypasses any strip behavior the app might have had.
When it matters
Texted from a beach. The kids' GPS, the iPhone's serial, and the timezone arrive in grandparents' iCloud backup along with the smile.
Email an expense-report photo to accounting. The receipt is in the picture. Your home Wi-Fi GPS is in the metadata. The two travel together.
A friend asks for the full-res. The original carries every field WhatsApp's re-encode would have dropped. The "send as file" toggle is a one-tap undo.
FAQ for messaging
No. iMessage delivers photos as-is by design — Apple wants the recipient to see the same image you saw, including metadata. The exception is the small "sticker-size" preview that gets auto-compressed; for that the EXIF is collapsed. For any normally-sized photo, every hidden field (GPS, camera serial, owner UUID, Live Photo trailer) reaches the recipient.
WhatsApp re-encodes photos at upload, which drops most EXIF as a side effect of the compression. GPS, capture time, and orientation are typically gone. Documents sent through the "Send as file" path are different — those preserve metadata. Videos are re-encoded too; the per-frame GPS track an iPhone wrote into the original is dropped, but the size and quality drop noticeably.
Yes. Signal strips EXIF metadata from photos at send and re-encodes at a lower quality bound for the same goal. It's one of the few mainstream apps that actively defends the sender. Even so, stripping locally first means the original file on your device — the one Signal reads from — doesn't carry the metadata in the first place, which matters for sender-side backups and for any other app that happens to read the same library.
Telegram strips EXIF from photos in the "Photo" mode, but if you choose "Send as File" (or send a HEIC the app doesn't auto-convert) the original metadata is preserved. The default behavior depends on the platform and the image type, so the safer rule is: strip locally before you send.
Yes. Email attachments are byte-identical to the file you attached. Whatever metadata was in the JPEG / HEIC / MP4 is delivered to the recipient. Gmail's web compose, Apple Mail, Outlook — all behave the same way. Email is a strict pipe, not a privacy filter.
AirDrop is a copy with metadata fully preserved — that's the feature. So is iCloud sync. So is Google Photos sync. The metadata travels with the file. Strip with Tracemute when you want the recipient (even if that recipient is future-you on a different device) to receive only the picture.
iMessage, email, and AirDrop deliver the file as-is. Use Tracemute to remove the GPS, the camera serial, and the embedded thumbnail before you attach. Same photo. Cleaner.
More situations