Which Social Media Platforms Strip EXIF Data?
You upload a photo. Some platforms erase its hidden GPS and camera data before anyone else can download it, some keep it, and some depend entirely on how you send the file. Here is the full picture across 19 platforms.
Every photo your phone takes records EXIF metadata — GPS coordinates, camera model, exact timestamp, sometimes the direction you were facing. When you share that photo, the platform decides what happens to all of it. Most large networks remove the sensitive parts from the copy other users can download. But the details vary by platform, by feature, and by sending mode — and they change without notice.
The one thing to understand before the table: "stripped" means removed from the downloadable file. It does not mean the platform never saw your data. On nearly every big platform, your original is read and stored server-side at upload and used for location features and ad targeting. Stripping protects you from other users, not from the company. The single documented exception is Signal.
The full comparison
| Platform | Copy others can download | Original kept server-side | Watch out for |
|---|---|---|---|
| Stripped | Yes — read for ads | Recompresses to ~70–75% quality | |
| Stripped | Yes | Same Meta pipeline as Instagram | |
| X (Twitter) | Stripped | Yes | Third-party schedulers & the Data Download export can keep GPS |
| TikTok | Stripped | Yes | DMs & highest-quality modes can retain GPS |
| Stripped | Yes | Applies to posts and profile photos | |
| Stripped | Yes | Only images hosted on i.redd.it; linked Imgur etc. keep whatever the host does | |
| Snapchat | Stripped | — | Snaps, Stories, Chat and Spotlight all processed |
| Stripped | Yes | Standard pin flow | |
| Signal | Stripped | No — nothing kept | Strips before sending; the privacy benchmark |
| Depends | — | Photo: stripped · Document: keeps 100% · "Best quality": GPS survives in ~1 in 4 cases | |
| Telegram | Depends | — | Quick photo: stripped · File / Document: keeps everything |
| Discord | Depends | — | JPEG inline: GPS stripped · PNG, video & file-attachments: kept · undocumented |
| iMessage | Kept | — | Full GPS + camera data reaches the recipient |
| Google Photos | Kept | — | Shared links serve the original with metadata |
| Flickr | Kept | — | Displays EXIF by design; GPS on a map unless you disable it |
| Email (Gmail, Outlook, Mail) | Kept | — | Attachment sends the original file untouched |
| Slack | Kept | — | Shared files retain full metadata |
| AirDrop | Kept | — | Sends the original file byte-for-byte |
| Cloud links (Drive, Dropbox, iCloud) | Kept | — | The shared link serves the original |
Method & sources. This comparison synthesises independent 2025–2026 testing published by MetaClean, EXIFData.org, SammaPix and others, kept where the sources agree and flagged where they diverge (Discord is the clearest example). It is not a claim that Scanly ran these lab tests. Platform pipelines change silently, so treat every row as "true at last check" — last verified August 2026. "Stripped" = removed from the downloadable copy, not proof the platform never read the original.
Public feeds: stripped for viewers, read by the platform
Instagram, Facebook, X, TikTok, LinkedIn, Reddit, Snapchat and Pinterest all remove GPS and most EXIF from the file other users can download. The mechanism is almost always the same: the image is recompressed and resized on upload, and metadata does not survive that pass. The catch is uniform too — the platform reads your original first. Meta, for instance, ingests the GPS at upload and uses it for location and ad features before the public file is ever cleaned.
X has a real loophole worth knowing: images posted through third-party schedulers (Buffer, Hootsuite and similar) and files pulled from X's own Data Download export do not reliably go through the same stripping. If you schedule posts professionally, your GPS may be reaching X intact.
About to post a photo? Check what metadata survives social media compression first.
Check Privacy Score →The privacy benchmark: Signal
Signal is the only major app that strips metadata and keeps nothing server-side. It removes EXIF before the image is even transmitted, so neither the recipient nor Signal retains your GPS. Every other platform in the "stripped" group protects you from other users but not from the company. If your threat model includes the platform, Signal is the exception that actually clears it.
The mode traps: WhatsApp, Telegram, Discord
These three are the ones that catch people out, because the answer flips depending on how you attach the file.
WhatsApp — a normal photo message is compressed and stripped. Send the same image as a "document" (which people do to keep quality) and 100% of the metadata goes with it: GPS, camera model, timestamp, everything. The newer "best quality" option is unreliable too — testing has found GPS surviving in roughly a quarter of cases.
Telegram — the same shape. A quick photo is stripped; a photo sent as a "file" keeps its full metadata.
Discord — the messiest of the three, and undocumented by Discord. A JPEG dropped inline into a message is re-encoded through Discord's CDN and usually loses its GPS. But PNG files, videos, and images sent as file attachments rather than inline images can pass through with metadata intact. Discord has publicly said it strips "some data (EXIF geocoding mostly)" — and "mostly" is doing a lot of work.
The keepers: everything survives
Email, iMessage, Google Photos links, Flickr, Slack, AirDrop and cloud-storage links deliver the original file untouched. Email attachments are the most common accidental leak — every byte of GPS arrives with the recipient. Flickr goes further and displays your EXIF, plotting GPS on a map unless you turn it off. These channels are not doing anything wrong; they are simply built to move the real file, metadata and all.
The recompression footnote
Whenever a platform strips EXIF, it also recompresses and resizes your image — so the file someone downloads from Instagram or X is a lower-quality copy, not your original. If you need to send full-quality images to people you trust, email or cloud storage does that, but full quality means full metadata. You can measure how much a platform degraded a photo by comparing the original and the downloaded copy with our Quality Analyzer.
What to actually do
The pattern across all 19 rows is that you cannot outsource this. Behaviour differs by platform, by feature and by sending mode, and it changes without an announcement. The only approach that is true everywhere is to strip the metadata yourself before it leaves your device.
Check what a photo is carrying with our free EXIF Checker — it shows every embedded field, GPS included. If it flags a location or a camera serial, run the file through the EXIF Remover, which strips the metadata right in your browser (nothing is uploaded), before sharing anywhere. To see exactly where a geotagged photo was taken, the GPS Map plots the coordinates for you. For the wider picture, read our complete Photo Privacy Guide.
What about screenshots?
A screenshot of a photo is a new file carrying your device's metadata, not the original photo's GPS. If someone screenshots an image and re-shares it, the screenshot holds the screenshotter's device info and timestamp — not the original location. This is why screenshots are sometimes used to sanitise a sensitive image, at the cost of quality. Our Screenshot Scanner can tell you whether an image is a screenshot.
Tools used in this guide