Short answer: yes, WhatsApp strips EXIF metadata — including GPS coordinates — from photos you send the normal way. Long answer: the moment you tap "send as document" instead, it stops stripping anything at all, and the person on the other end gets your exact coordinates, your phone model, and the second you took the picture. That single distinction, photo versus file, decides whether your metadata survives in almost every messaging app, and it's the part most people have never thought about.
I tested nine popular apps and services with a geotagged photo and checked what arrived on the other side. The results split into three clean groups: apps that always strip, apps that never strip, and apps that do either depending on how you send. Let's go through them.
Why apps strip metadata at all (hint: it's not for your privacy)
Messaging apps recompress photos to save bandwidth. When WhatsApp shrinks your 12 MB photo down to a few hundred kilobytes, it re-encodes the JPEG from scratch — and the metadata simply doesn't get copied into the new file. Stripping is mostly a side effect of compression, not a privacy feature someone designed. That explains the pattern you'll see below: whenever an app offers an "original quality" or "send as file" path that skips recompression, the metadata skips the shredder too.
One more thing worth being clear-eyed about: stripping happens on the way out, after the app has the full file. WhatsApp's servers, Meta's infrastructure, Instagram's upload pipeline — they receive your photo with metadata intact and can read all of it before the public or your recipient ever sees a cleaned copy. Removing metadata before the photo leaves your device is the only version of this that protects you from the platform itself.
None of this behavior is contractual, either. Vendors rarely document how they handle metadata, almost never announce changes to it, and the behavior can differ between the iOS and Android builds of the same app. Everything below is what we observed in our own tests as of mid-2026 — treat it as a snapshot, not a promise.
The messaging apps
Sent as a regular photo, WhatsApp compresses the image and strips EXIF, including the GPS block. Sent via the attachment menu as a Document, the file goes through byte-for-byte — every field intact. The newer "HD quality" photo option still recompresses and still strips, in our tests as of mid-2026. So the rule for WhatsApp is simple: photo button safe, document button not.
The rule holds in both directions, by the way. Photos other people send you as documents arrive with their metadata intact, which means a saved WhatsApp media folder can be a mix of clean files and fully loaded ones with no visible difference between them. Worth remembering before you forward anything.
Telegram
Same split, sharper edges. A regular photo send is compressed and stripped. But Telegram's Send as File option is more prominent than WhatsApp's document flow, and plenty of users choose it specifically to preserve image quality — without realising they're preserving their GPS coordinates along with the pixels. If someone sends you a photo "as file" in Telegram, you can read exactly where it was taken. File sends also keep the original filename, which leaks more than you'd think — an IMG_20260214_183042.jpg is a timestamp all by itself.
Signal
Signal strips EXIF metadata from images you send, and unlike the other two it treats this as an explicit privacy commitment rather than a compression side effect. In our tests, photos arrived with camera info and GPS removed. Signal doesn't have a dedicated "document mode" for images the way WhatsApp does, which removes the most common footgun. Of the mainstream messengers it's the one whose defaults I'd trust furthest — though I'd still verify anything sensitive myself.
iMessage
Here's the one that surprises people: iMessage keeps metadata. Apple sends photos at or near original quality, and the EXIF — including location — arrives intact on the recipient's device. Anyone you iMessage a photo to can open the info panel and see a map pin of where you took it. Apple's mitigation lives in the share sheet: tap Options at the top and switch Location off before sending. But that's opt-in, per send, and hidden behind a label nobody taps. (Green-bubble caveat: photos that fall back to MMS get recompressed by the carrier, which usually mangles the metadata along with the quality — but you don't control when that fallback happens, so it's no strategy.)
Facebook Messenger
Regular photo sends are recompressed and stripped, same as WhatsApp — no surprise, same parent company. Files sent through Messenger's file-attachment flow keep their metadata. And as with everything Meta, the original hits their servers first.
The social platforms
Instagram strips EXIF from photos on upload. Download a public Instagram photo and you'll find essentially no capture metadata in it. But Instagram's own data policy makes clear the platform collects metadata from your uploads — location included — for its own use. The public never sees your coordinates; Meta does. If that distinction matters to you, strip before you upload, not after.
X (Twitter)
X has stripped EXIF from uploaded photos for well over a decade — this has been the behavior since the early 2010s, and it's one reason the infamous 2012 John McAfee incident (a Vice journalist's iPhone photo whose intact GPS data revealed McAfee's hideout in Guatemala) happened via a magazine's own website rather than a social network. Public X images carry no EXIF. Same caveat as Instagram: the platform receives the original.
Email and cloud links: nothing is stripped, ever
This is the category people get wrong most often, so let me be blunt: email attachments keep everything. Gmail, Outlook, Proton — an attached photo is transmitted as-is, every byte, GPS block and all. Email predates the entire concept of automatic metadata hygiene, and no mainstream provider rewrites your attachments. The photo you email your landlord, your insurer, or a stranger from a marketplace listing carries your full dossier.
Cloud storage links are the same story. Share a photo via a Google Drive or Dropbox link and the recipient downloads your original file, metadata intact — that's the whole point of cloud storage, faithful copies. Google Photos link-sharing is the partial exception: with "Hide photo location data" enabled it removes GPS (though only GPS) from link downloads. Drive proper does no such thing, and neither does Dropbox.
Zipping photos before you send them changes nothing, in case you were wondering — compressing the container doesn't touch the files inside it. And folders synced through the Drive or Dropbox desktop clients contain originals by definition; that's the product working as intended.
If you regularly send photos by email or cloud link, running them through a metadata remover first should be a habit, teh same way you'd blur a document before posting it.
The full scorecard
Everything above in one table, based on our tests as of mid-2026. Platform behavior changes, so treat this as a snapshot and verify anything you're betting your privacy on.
| App / service | EXIF kept? | GPS kept? | Notes |
|---|---|---|---|
| WhatsApp (photo) | No | No | Recompressed; HD option also strips |
| WhatsApp (document) | Yes | Yes | Byte-for-byte original |
| Telegram (photo) | No | No | Compressed on send |
| Telegram (send as file) | Yes | Yes | Popular for quality; keeps everything |
| Signal | No | No | Strips as a deliberate privacy measure |
| iMessage | Yes | Yes | Share sheet → Options → Location off to strip GPS |
| Facebook Messenger (photo) | No | No | Files sent as attachments keep metadata |
| No (public) | No (public) | Meta collects metadata server-side before stripping | |
| X (Twitter) | No (public) | No (public) | Stripped on upload since the early 2010s |
| Gmail / email attachments | Yes | Yes | Attachments are never modified |
| Google Drive / Dropbox links | Yes | Yes | Recipients download your original file |
The rule of thumb that actually holds
If the app makes your photo smaller, it probably strips metadata. If the app promises to deliver your photo exactly as-is — as a file, a document, an attachment, or an original-quality download — it keeps everything.
That heuristic covers every service in the table, and it'll probably cover the next app you wonder about too. Compression and stripping travel together because stripping is a byproduct of compression.
And you don't have to take my word for any of it — this test is easy to run yourself. Take a photo with location services on, send it through the app in question to a second device (or a patient friend), save the received copy, and open it in our photo metadata viewer. If the GPS section is empty, the app stripped it; if you're looking at a map pin of your kitchen, it didn't. Five minutes, and you'll know the current behavior of your exact app version instead of trusting an article — even this one.
Two practical takeaways. First, never rely on a platform to do your metadata hygiene — behavior varies by send mode, changes between versions, and never protects you from the platform itself. Strip locally before the file leaves your device; our photo remover and GPS-only remover both run entirely in your browser. Second, when you recieve a photo and want to know what it's carrying, check it yourself rather than assuming the sender's app cleaned it. A file sent through the "wrong" button in Telegram or WhatsApp tells you exactly where its sender was standing — which is worth knowing before you forward it anywhere.