How to Remove EXIF Data From a Photo on Android

Guides that claim “tap Gallery → Settings → Remove EXIF” on every Android phone are inventing a menu. If you need to remove EXIF data from a photo on Android, start from an honest baseline: there is no single universal built-in EXIF editor across all manufacturers. Pixel, Samsung, OnePlus, and budget OEM skins ship different Camera apps, different Galleries, and different share sheets. What follows is what you can verify in practice — especially around Google Photos — and why a browser-based wipe is usually more reliable than hunting a per-device setting.

What Android photos embed

With location allowed for Camera, many Android JPEGs include GPS plus standard EXIF: device model, timestamp, orientation, and software strings. Messaging apps and social clients then diverge: some recompress and drop parts of the header; some send the file largely intact, especially when you choose “document” or “file” style sharing instead of in-chat media compression. You cannot infer cleanliness from “I posted it and the on-screen preview looked fine.”

Stop new geotags at the source (not a full wipe)

On most phones you can limit future location tags:

• Open Settings → Location (wording varies slightly by OEM) and review which apps may use location.
• Open the Camera app’s own settings and look for a control such as Location tags / Save location / Geotag — if your OEM provides one — and turn it off.

That reduces new GPS in future shots. It does not strip EXIF from the photo already in DCIM, and it does not remove camera model or DateTimeOriginal. Treat capture settings as prevention, not cleanup.

Google Photos: what it does and does not strip

Google Photos is common on Android, but it is a library and backup product first — not a dedicated EXIF sterilizer.

In your library: Google Photos generally retains the metadata that arrived with the file (including location when present). That powers map views, search, and memories. Backing a photo up to Photos is not the same as scrubbing it.

When sharing: Behavior depends on the path. Some Google Photos share flows expose a control related to removing location for that share when location exists. That control — when it appears — is about location for the outbound share, not a promise that every EXIF field is gone. Sharing into another app through the Android system share sheet can pass along a file that still carries camera and time tags; in some cases it may still carry GPS depending on how the receiving app requests the content.

Shared albums vs. one-off links: Album collaboration features are built around browsing a set of media; do not assume album members cannot learn location cues that Photos still associates with items. If privacy matters, strip the file before it enters a shared album.

Info / remove location inside Photos: Google Photos can show location on a photo’s info surface and may let you remove location from that item in the Photos experience. Treat that as managing Photos’ location association — and still verify any file you download or forward if your threat model cares about the bytes on disk.

Bottom line for Google Photos: useful for viewing; unreliable as your only EXIF removal tool; location-oriented controls ≠ full metadata wipe.

OEM Galleries and “share without location”

Samsung Gallery and other OEM galleries sometimes offer share options that omit location. Those menus are real on some devices and absent on others. Even when present, they typically target geotags, not a complete EXIF purge. Because the labels and locations move between One UI / skin versions, this guide will not invent a single tap path and pretend it ships on every Android phone.

If your Gallery shows an explicit “remove location” or similar toggle on the share sheet, you may use it for low-stakes shares — then verify. If you cannot find such a control, you are not missing a secret universal Android feature; you are seeing fragmentation.

Why a browser-based tool is more reliable

A browser wipe sidesteps OEM UI drift:

• Same steps on Pixel and Samsung. Open the site, choose a JPEG/PNG, strip, download.
• No mystery APK. You are not granting a random cleaner broad storage permissions beyond what the browser file picker already scopes.
• Full common-tag pass. MetadataWipe rebuilds a browser-generated image so typical EXIF/IPTC/XMP blocks are not copied into the export — not merely hiding location in one app’s database.
• Works offline after load. Once the page is available, processing stays on-device in browser memory; your photo is not sent to MetadataWipe servers for the wipe.

Step-by-step: MetadataWipe on Android

1. In Files / Downloads, keep a copy of the photo you plan to send (JPEG or PNG).
2. Open Chrome (or another up-to-date mobile browser) and go to MetadataWipe.
3. Choose the image from local storage. Review the metadata summary if tags are present.
4. Run Remove Metadata and save the downloaded -metadatawipe file.
5. Share that cleaned file from Files — not the original Camera folder item.

Repeat per image for a carousel. The current tool processes one still image at a time; privacy does not require a bulk server batch — it requires every outbound file to be clean.

Messaging and social caveats on Android

WhatsApp, Telegram, Signal, and similar: In-chat “photo” sends are often recompressed; “as file/document” sends may preserve more of the original header. Strip first if the recipient could save the file.

Gmail and file attachments: Attachments generally send the bytes you picked. A dirty JPEG stays dirty.

Instagram / TikTok / Facebook apps: Platforms may re-encode on their side, but that is their pipeline, not your guarantee — and drafts, multi-app shares, or “open in browser” flows can differ. Cleaning on-device before you hand the file to the app remains the step you control.

Nearby Share / Bluetooth / USB: These are file transfers. They do not strip EXIF.

Screenshots and scanned PDFs saved as images

Android screenshots are new captures. They may lack camera GPS yet still include device/software metadata. Scanned documents saved as JPEG/PNG from a scanner app can embed scanner software tags and sometimes timestamps. Run the same wipe on anything you will email as an image attachment.

Verification habit

After cleaning, reopen the export in MetadataWipe or any EXIF viewer you trust and confirm GPS, model, and date fields are gone. If a share is sensitive (home interior, kids’ school event, workplace), verification is part of the workflow — not optional polish.

Quick Android policy you can reuse

• Turn off Camera location if you do not need geotags going forward.
• Do not trust Gallery folklore menus that “every Android has.”
• Treat Google Photos location controls as location-only, share-path-dependent help.
• Wipe JPEG/PNG in the browser before public or commercial shares.
• Attach from the cleaned download, never straight from DCIM for those shares.

When an OEM “cleaner” app is the wrong move

Search results for Android EXIF removers often push installable apps with broad storage access. Some are fine; many are unnecessary if a browser tool already solves the file in front of you. Prefer the least privilege path: the browser file picker scopes a single image you chose, MetadataWipe rewrites a downloadable copy, and you delete the dirty original from the share folder when you are done. If you later change phones, the browser habit travels with you — the Samsung-only Gallery toggle does not.

Also watch for apps that “hide location in the gallery view” without rewriting the file. A viewer filter is not the same as a clean JPEG on disk. Always confirm by opening the outbound file in a second tool before a high-stakes send.