Most people believe WhatsApp strips photo metadata. Most people are thinking about the ordinary path: pick a picture, hit send, and the app quietly resizes it. That path does usually remove the camera's location block, because the app re-encodes the image to save bandwidth.
But WhatsApp also has a document path, and a file sent that way is not rebuilt. It is uploaded and delivered as the same file, and every tag it arrived with is still inside it when your contact saves it. The two paths sit next to each other in the same chat, and which one you used is not always obvious after the fact.
Two ways to send one photo
The difference is not about encryption or privacy settings. It is about whether the app decodes the image before sending it. Decoding means rebuilding from pixels, and a rebuild rarely carries the original metadata forward.
| Action | What happens to the bytes | What to assume |
|---|---|---|
| Sent as a photo from the gallery | Decoded, resized, re-compressed for delivery | GPS and most EXIF are usually gone |
| Sent as a document | Uploaded and delivered as the same file, within the size limit | Assume every tag is intact |
| Taken with the in-app camera | Captured and compressed by the app itself | Usually stripped, but not promised |
| Forwarding a received photo | Re-sends the copy already in the chat, not your original | Depends on that copy, not on your file |
| Saving a photo a contact sent | Writes the compressed copy to your device | Only what that copy still had |
| Chat backup to a cloud account | Stored by your cloud provider, outside the chat's end-to-end encryption unless encrypted backups are on | A second copy of everything you sent |
Sending as a photo
When you send an image through the normal photo path, the app is optimising for a chat bubble on a phone screen. It does not need a 12-megapixel file to do that, so it resizes and re-compresses. As of writing, this is the default experience on both mobile platforms, though quality settings and app versions vary.
The metadata block goes with the pixels that were discarded. GPS, lens data, capture time and serial numbers are not part of the re-encoding job, so they disappear without anyone deciding to remove them. That is why the result can look like a privacy feature while remaining an accident of compression.
Two caveats come with that accident. First, it removes the metadata from that copy, not from the original on your phone. Second, it tells you nothing about future app versions; a pipeline change is not a policy announcement.
Sending as a document
The document path exists so people can send contracts, spreadsheets and design files. The service treats what you attach as an opaque blob. It is not decoded, not resized, and not re-compressed, so the file your contact saves is the file you sent, up to the size limit in force at the time.
For a photo, that means the full EXIF block travels: the coordinates where it was taken, the device model, the serial number, the original timestamp, and any edit history a desktop editor wrote into the file. If you have ever wondered why "WhatsApp strips metadata" failed you, this is usually the reason.
Which one you are actually using
The test is not what you intended, but what the attachment looks like in the chat. A photo sent the compressed way appears inline as a picture, often with a small preview and a caption box. A file sent as a document appears as an attachment with a name and a size, and usually needs a tap to open.
That distinction matters when you are sending something sensitive and assuming the app will clean it. If you can see a file name and a file size, you used the path that preserves everything. If you can only see the picture, you used the path that probably re-encoded it — probably, on this version, on this platform.
A second check is worth doing once: send a photo to yourself through both paths, save both, and compare the tag lists. That takes a minute and settles the question for your own app version instead of relying on a general claim.
Why "it's just WhatsApp" is not a guarantee
Three things weaken the reassurance. The first is the document path, which exists on every platform and preserves everything. The second is the recipient's side: saving, forwarding, backing up and screenshotting all happen after the app has finished with the file, and none of them cleans anything.
The third is version drift. Compression targets change with network conditions, device capabilities and app releases. A behaviour you confirmed last year is a data point, not a contract. If a photo must not carry coordinates, the only reliable fix is to remove them before the file leaves your device.
What to do before you send
Strip first, then choose a path based on how much quality you need. Removing metadata does not change a pixel, so a cleaned original sent as a document looks exactly as good as the unclean one and no longer carries the location. If you send it as a photo instead, the app will compress it either way.
Keep Orientation and the ICC colour profile when you clean, because those affect
display rather than identity. Everything else — GPS, serials, timestamps, software history —
can go. If you are unsure what a specific file holds, check it before sending rather than
after.
See what your photos are carrying
Drop an image in. MetaPurge lists every tag, then rewrites the file without touching a pixel.
Open the metadata removerWhere to go next
- Does Instagram remove EXIF? — the same re-encode logic, and where it stops applying.
- Email and cloud photo metadata — the other routes where the original file travels unchanged.
- What is EXIF metadata? — the tags a phone writes, and which ones identify you.