WhatsApp already compressed my photo. Is GPS gone from my phone?

The copy in the chat thread is WhatsApp’s recode. The file in Photos is a different object. Strip does not reach into the album. Clean a download, then send that file.

Should I send as photo or as document after Strip?

Photo: WhatsApp will recode again; quality drops, tags on their copy usually die, your album is still dirty unless you send the cleaned file. Document: closer to the bytes you picked — so those bytes must already be the stripped download, not the Camera Roll original.

Does Status or View once clean the original?

No. Those are delivery modes. They do not rewrite Camera Roll. A later “forward original” or a desktop grab from Pictures can still leak GPS.

WhatsApp Desktop picked a file from Pictures. Is that safe?

Desktop often sends the disk file, not a mobile recode. That is the dangerous path. Point it at the Downloads copy you verified in Strip, not at DCIM or iCloud.

WhatsApp: the bubble is not the file on disk

Updated 6 September 2026

Three different objects get called “the photo.” The chat bubble is WhatsApp’s recode. The JPEG in Photos is still the camera file. “Send as document” can ship those original bytes. Strip can clean a copy you download. It cannot edit the thread, and it cannot edit Camera Roll.

Why “WhatsApp already stripped it” is the wrong sentence

Recipients often get a recompressed still. WhatsApp may drop EXIF on that recode. That is their CDN and their encoder, this month, for that send type. It is not a rewrite of your album. The next time you forward from Photos, attach the same still to Mail, post it to a marketplace, or open WhatsApp Desktop on a folder of originals, the GPS IFD is still there.

Status, View once, disappearing messages, and starred messages are delivery modes. They do not walk through DCIM and empty GPSLatitude. A “they only saw it once” send still left the original on your device and, depending on backup, in a cloud copy you do not think about.

Photo send versus document send

Send as photo. WhatsApp recodes. Quality drops. Their copy to the other phone is usually a new JPEG. Tags on that copy often die because the encoder never copied them. Your Camera Roll is untouched. If you later export “original” from Photos, you export the dirty file.

Send as document. You are closer to attaching the bytes you picked. That is useful when you want the other person to receive the stripped download without a second recode. It is dangerous when you pick Recents: document send will happily ship GPS. Document is not a cleaner. Document is a pipe. Put a verified file in the pipe.

HD / quality toggles inside WhatsApp change their recode. They do not strip the album. Do not turn HD on “for privacy.” Privacy here is which file you pointed at.

WhatsApp Desktop is the leaky path

On a phone, a photo send at least recodes. On desktop, the attach dialog often reads a file from Pictures, iCloud Drive, or a synced DCIM folder and sends those bytes. Journalists, sellers, and family admins do this when they “just grab it from the computer.” If that computer has the camera original, WhatsApp Desktop will send the camera original. Point it at the Downloads file you verified in this tab.

What this page will not talk about

This is not how to fit a JPEG under a mail cap, and it is not Safari’s blob share sheet. Those are other tools’ ceilings. This page is only: bubble ≠ disk ≠ document. For iCloud versus the download, use iPhone. For a listing thumbnail versus the seller’s disk, use marketplace. For the GPS field names, use EXIF / GPS.

A sequence that matches how the apps actually work

If the still is HEIC, export JPEG first. Inspect the JPEG — conversion copies tags.
Strip in Safari or desktop Chromium with the tab in the foreground. Airplane mode is fine after load.
Save into Files with a name you will recognize. Re-drop it. Empty GPS.
In WhatsApp, attach from Files (or document from that folder). Skip Recents.
If you need the other person to receive your cleaned pixels without another recode, send as document — of the stripped file only.
If you already sent the album original as document, you cannot unsay it. Clean the next file. Delete the original from Photos if you do not want it on the next attach.

Backups and “I already deleted the chat”

Deleting a thread does not delete Camera Roll. A WhatsApp backup is not Strip. Google Drive / iCloud chat backups are out of this tool’s scope; we do not open them. The file you care about is the JPEG you still have in Photos. Inspect that. If GPS remains, strip a copy before the next send, then consider deleting the original in Photos yourself.

What looks like a bug and is not

Recipient says the photo looks soft — their recode. Not Strip Fast (Fast does not recompress JPEG).
Recipient has no GPS, you still do — expected. Two files.
Forward from the thread looks clean, forward from Photos is not — you forwarded two different objects.
Desktop attach leaked — it read Pictures. Point at Downloads.

Honesty limits

Strip does not patch WhatsApp. It does not disable their encoder. It does not reach Media/WhatsApp/Images on Android or the iOS app sandbox. Empty GPS on the file you hold, then a share sheet that points at that file, is the whole job. If the picture shows a street, the street is still in the pixels. Crop is a different decision.