Comparison
Which apps remove EXIF data when you share a photo?
Signal, Discord, Facebook, X and Slack strip EXIF from photos you post. iMessage, email, AirDrop, iCloud Photos and Google Photos downloads keep everything, GPS included. WhatsApp and Telegram strip in photo mode but preserve every field when you attach the same image as a file.
The split is not social versus private, and it is not big platform versus small. It runs along a duller line: platforms that re-encode your image strip metadata as a side effect, and platforms that deliver the original file keep it. Signal strips because it recompresses. iMessage keeps because it hands over your file untouched. Knowing which bucket an app sits in tells you what your recipient receives. For four popular apps, nobody outside the company actually knows.
Which apps strip EXIF, and which keep it?
Eleven platforms have verifiable behaviour, from vendor source code, official documentation or published testing. Signal, Discord, Facebook, X and Slack remove GPS. iMessage, Gmail, AirDrop, iCloud Photos and Google Photos downloads preserve it. WhatsApp and Telegram depend entirely on whether you send as a photo or as a file.
| Platform | GPS on send | What the recipient gets | Confidence |
|---|---|---|---|
| Signal | Stripped | Re-encoded copy. All EXIF gone except orientation. | High source code |
| Depends | Photo mode: re-encoded, EXIF dropped. Document mode: original bytes, everything intact. | Medium testing | |
| Telegram (cloud) | Depends | Photo mode: re-encoded. "Send as file": original preserved. | Medium bug tracker |
| Apple iMessage | Kept | Your original file, GPS included. Photos shot in the in-Messages camera are the exception. | Medium Apple docs |
| Stripped | Re-encoded, resized above 2048px. Keeps Artist and Copyright; injects its own IPTC tracking field. | Medium IPTC, 2019 | |
| Unverified | No credible public test since 2019. Assume nothing. | Low | |
| X (public posts) | Stripped | Re-encoded. X says it reads EXIF and holds it "temporarily" server-side. | High X help docs |
| X Chat (DMs) | Kept | GPS recoverable by the recipient. X's stripping policy covers public posts only. | Medium |
| Discord | Stripped | EXIF removed before CDN storage. XMP and ICC blocks survive. | High 2025 thesis |
| Slack | Stripped | GPS removed; make and model retained. Behaviour of the download link is undocumented. | Medium 2020 |
| Gmail / email | Kept | Attachments are byte-preserved. Full EXIF and GPS arrive intact. | High |
| Google Photos | Kept | Viewer hides location, file does not. Downloads carry full GPS. | High Google docs |
| iCloud Photos | Kept | "Original formats at full resolution", per Apple. Nothing removed. | High Apple docs |
| iCloud Shared Albums | Unclear | Re-encoded and downscaled to 2048px. Whether GPS survives is undocumented. | Low |
| AirDrop | Kept | Preserved by default. The share sheet's Location toggle still applies. | Medium |
| Reddit, LinkedIn, Snapchat | Unverified | No documentation and no credible testing. LinkedIn's only datapoint, from 2015, says it kept EXIF. | Low |
Confidence reflects source quality, not how confident the internet sounds. "High" means vendor source code, official documentation, or published independent testing.
Why do three popular EXIF claims turn out false?
Three claims repeated across hundreds of articles fail when checked against primary sources: that Signal's send-as-file bypasses stripping, that Discord's CDN keeps the original EXIF, and that Gmail strips metadata. Each is not merely outdated. Each is wrong in the direction that makes people less careful.
Correction 1: Signal has no send-as-file bypass
A 2025 paper claims Signal's document mode retains all EXIF. Signal's Android source defines the document path as everything that is not an image or video, so a JPEG can never route through it. There is no bypass. Signal strips, on both platforms, every time.
Correction 2: Discord's CDN original is already clean
The advice to fetch the cdn.discordapp.com URL "to get the un-stripped original" inverts what happens. Discord strips EXIF before the file reaches the CDN, so the stored original has no EXIF to recover. The media.discordapp.net proxy then strips more.
Correction 3: Gmail does not strip metadata
Email attachments are base64-encoded byte-for-byte; the GPS is in the delivered file. What people observed is their mail client re-encoding on Save Image As. Emailing a photo to protect your location does the opposite of what you think.
Why is "hidden" different from "removed" on Google Photos?
Google Photos separates what its viewer shows from what its files contain. Turning off location sharing hides coordinates in the interface while leaving them in the file, so anyone who downloads the image receives full GPS. The setting governs display only, and the distinction is the single most misread item in this comparison.
The same gap appears on X, which says plainly that it "retains Exif temporarily to process your photo." The served image is clean, the server saw everything. It appears again on Facebook, which strips your EXIF and then injects its own IPTC tracking field into the file it serves.
The useful question is never "does this app show metadata?" It is what does the recipient's copy contain. Those have different answers on at least three of the platforms above, and the interface will not tell you which one you are looking at.
Which platforms can nobody actually verify?
Instagram, Reddit, LinkedIn and Snapchat have no vendor documentation and no credible public testing of EXIF handling. The universal claim that all four strip GPS traces to content farms rather than evidence. LinkedIn's only real datapoint, an embedded-metadata test from 2015, found that it preserved EXIF.
Neither Discord nor Slack publishes a single line about EXIF in any help article or policy. Discord's stripping is well established by a 2025 University of Colorado Denver thesis that tested 233 JPEG and 77 PNG files, but that is a researcher's finding, not a promise the company has made or has to keep.
Two more gaps worth naming. Android's photo picker redacts location EXIF before an app ever sees it unless the app holds ACCESS_MEDIA_LOCATION, which means any "app X strips GPS" test run on Android may be measuring the operating system rather than the app. And Meta's newest confirmation is from 2019. Seven years is a long time in an image pipeline.
How do you check what a platform did to your photo?
Send yourself the photo through the exact path you plan to use, download the received copy, and read its metadata. This is the only method that survives policy changes, silent pipeline rewrites and the gap between documentation and behaviour. It takes under a minute and answers the question for your app version, today.
- Read the original first. Open the photo in Image Inspector and note whether a GPS block exists. If your source file has no location, nothing downstream matters.
- Send it through the real path. The same app can behave differently in photo mode versus file mode, in a DM versus a public post, on iOS versus Android.
- Download the received copy: not the thumbnail, not the preview. The served image and the downloadable original are different files on Google Photos and X.
- Read the received copy. Compare the GPS block against the original. Anything still present is what your recipient has.
Do this once per app you care about and you will have better information than any table on the internet, including this one. Behaviour changes; a test you ran yourself does not go stale quietly.
Key takeaways
- Re-encoding is what strips metadata. Apps that deliver your original file (iMessage, email, AirDrop, iCloud Photos) keep GPS by design.
- WhatsApp and Telegram preserve every EXIF field when you attach a photo as a document instead of sending it as a photo.
- Google Photos hiding location in its viewer does not remove it from the file anyone downloads.
- Instagram, Reddit, LinkedIn and Snapchat EXIF behaviour is unverified; the claim that all four strip GPS has no credible source.
- Signal has no send-as-file bypass, Discord's CDN copy is already EXIF-free, and Gmail does not strip metadata.
- Testing your own send path beats every published table, because platform pipelines change without announcements.
Frequently asked questions
Does WhatsApp remove GPS data from photos?
Sending a photo in WhatsApp's normal image mode re-encodes it, which drops EXIF including GPS. Attaching the same file as a document preserves the original bytes and all metadata. WhatsApp's own documentation never mentions EXIF, so this rests on independent testing rather than a vendor guarantee.
Does iMessage strip location from photos?
No. iMessage delivers the original file, GPS included, when you attach a photo from your library. Apple's Personal Safety User Guide instead tells you to remove location yourself using the share sheet's Options panel, which is a strong signal that iMessage does not do it for you.
Does Google Photos remove location data when sharing?
Google Photos hides location in its viewer, but that is a display setting, not a file change. Anyone who downloads the photo receives the original bytes with full GPS coordinates intact. Hiding location in the interface does not remove it from the file.
Does emailing a photo remove its metadata?
No. Email attachments are base64-encoded byte-for-byte, so a photo arrives with EXIF and GPS fully intact. The common belief that Gmail strips metadata comes from a different behaviour: some mail clients re-encode an image when you use Save Image As.
Does AirDrop keep EXIF and GPS data?
AirDrop preserves metadata by default, and Apple has never documented it stripping anything. The share sheet's Options panel still applies, so turning Location off before you AirDrop removes the GPS fields from the copy your recipient receives.
Is it safe to assume Instagram strips EXIF data?
No. The claim is repeated everywhere but traces to content farms rather than testing or documentation. The last credible check, by the IPTC in 2019, established only that Instagram does not display metadata. Treat Instagram's current behaviour as unverified and strip location yourself.
Before you share
Read the file, not the folklore.
Image Inspector opens a photo on your iPhone and shows you the GPS block, the capture time and the device that took it, before you send it.
About the author
The Image Inspector team · BigBalli
Image Inspector is an iOS app that reads a photo's EXIF, GPS and Apple MakerNote fields on device and reports what travels with the file. We build metadata parsers for a living, which is why this page cites source code and vendor documentation instead of restating what other pages say.