Which apps and platforms strip EXIF — and which don't
“Doesn't the platform remove that anyway?” is the most common reason people give for not bothering with EXIF. The answer is: sometimes, in some places, for the copy other users see, and it changes without notice. This guide collects the behaviour that is documented or has been repeatedly confirmed for the big platforms, messengers, email and cloud services, and explains why the safe assumption is still to strip metadata before the file leaves your device.
Why platforms strip at all
Most large services re-encode every uploaded image: they resize it to several sizes, recompress it to save bandwidth and convert it to a house format. Re-encoding through an image library naturally discards the EXIF, IPTC and XMP blocks unless the pipeline copies them across on purpose. Stripping is therefore often a side effect of the delivery system rather than a privacy feature, which is exactly why it is unreliable.
There is also a second copy to think about. Even when the public image is clean, the platform has already parsed the original. Facebook's data policy states that it collects metadata such as the location of a photo; Instagram and Google Photos use timestamps and coordinates to build memories and maps. Stripping on the way out protects other users from you, not you from the platform.
Social networks
Facebook, Instagram, Threads, X, TikTok, LinkedIn, Pinterest and Reddit all serve images without EXIF; a downloaded copy of a post shows no camera, date or GPS. Mastodon strips EXIF on upload by default and only keeps the orientation. These are the platforms where stripping is most consistent, because their media pipelines were built to re-encode everything.
Two caveats apply even here. The original file is kept and analysed on the server side, and features that surface location — check-ins, tagged places, “memories” — draw on it. And behaviour is versioned: a platform can change its pipeline, add an “upload original quality” option or hand files straight through in a new product, and nobody announces that EXIF handling changed.
Messengers: it depends how you send
WhatsApp is the classic case. Sent as a photo, the image is recompressed and loses its EXIF. Sent as a document — the option many people use to preserve quality — the original file goes through untouched, GPS included. Telegram behaves the same way: the compressed “photo” path strips, the “send as file” path keeps everything, and files in channels are served exactly as uploaded.
Signal strips metadata from images it sends. Apple Messages sends the photo you picked from the library as is, including location, unless you open Options in the share sheet and turn Location off. Team tools such as Slack are designed to move files intact and should be assumed to keep everything. When the recipient can choose “Save original”, treat the channel as one that keeps metadata.
Email, cloud drives and everything that stores files
Email attachments are the file, byte for byte; no mail client or server strips anything. Google Drive, Dropbox, OneDrive and iCloud Drive are file stores and keep the original by design — that is their job. Google Photos keeps and indexes metadata, and although it has a setting to hide location in link-shared items, it is off by default and does not cover every sharing path. Backups, NAS boxes and “send large file” services are the same: what you put in is what comes out.
Websites are the least predictable group. WordPress generates resized copies without EXIF but leaves the original upload at its own URL. Forum software varies: Discourse strips image metadata by default through a site setting, many older boards do not. Classifieds and marketplaces usually resize and re-encode, which happens to drop EXIF, but a few serve originals, and the only way to know is to test.
How to check for yourself in 2026
Everything above describes behaviour as of mid-2026, confirmed by uploading test files and downloading them again. It will drift. The test takes two minutes: take a photo with location on, upload it the way you normally would, download the published copy from the other side and drop it into ExifMop. If the score is 100 and no location is listed, that path strips. If not, you have your answer for that platform, that upload option and that day.
The more durable strategy is to make the question irrelevant. Strip metadata from the batch before it goes anywhere, and the behaviour of the recipient no longer matters. Because removal is lossless, it costs nothing in quality, and you can keep the tagged originals in your own library if you value the dates and places for yourself.
The takeaway
Big social networks strip EXIF from what they publish but read it first; messengers strip only on the compressed “photo” path; email, cloud drives and most file stores keep everything. Test a platform if you must, but stripping before upload is the only rule that never goes stale.
More guides
What the GPS data in your photos reveals (and how precise it really is)
The GPS block in a photo is more than a pin on a map: altitude, heading, satellite time and a trail of routine. Here is what the tags hold, how accurate they are, and who reads them.
Lossless EXIF removal vs re-encoding: why the mop matters
Metadata sits in its own segments and chunks, so it can be cut out without touching a pixel. Re-encoding does the opposite: it recompresses the picture, can shift colours and drops the orientation you relied on.