Quick answer: inspect the original locally, turn off or remove GPS fields, export a separate copy, and keep the original untouched. No metadata tool can guarantee what a future platform will add or infer.
Why a photo can reveal a place
Many phones and cameras can write location coordinates into the photo file at capture time. The picture may show an ordinary room or a blank wall, while its metadata contains a latitude and longitude that can point to a home, workplace, school, or travel stop.
That information is usually stored in EXIF, a set of tags used by cameras and photo libraries. Location is only one category. Capture time, device model, editing software, copyright notes, orientation, and an embedded thumbnail can also travel with the file.
What to check before you send
A good preflight separates fields by sensitivity instead of treating every tag as equally risky. Start with:
- GPS coordinates: the highest-priority field because it can identify a precise place.
- Device details: manufacturer, camera model, serial-like identifiers, and software names.
- Timeline details: capture and modification dates that add context to the image.
- Previews and editing history: thumbnails, app names, and export traces that may reveal more than expected.
When you use a checker, prefer one that shows the exact values, lets you choose fields individually, and creates a new file. “Clean” should be an auditable result, not a vague label.
Keep the original and create a cleaned copy
Removing metadata can affect useful information. Orientation may help an app display the image correctly, and copyright fields may be important to you. A reversible workflow lets you retain those fields or restore them later when the format supports it.
Preflight processes supported images in the browser. The original stays on your device and is never overwritten. The resulting manifest lists what was selected, removed, retained, unsupported, or left unverified.
What about MP4 and MOV files?
Short videos are more complicated than still images because a container can hold multiple streams, codec data, timestamps, location atoms, and encoder tags. A browser can identify some container signals, but it cannot always prove that every stream was inspected or predict what a messaging platform will do next.
That is why a responsible video checker should show limitations clearly. If a tool cannot clean a format deterministically, it should leave the file unchanged and record that limitation rather than claiming a perfect privacy guarantee.
A simple pre-share routine
- Inspect the original before uploading it anywhere.
- Review GPS and device fields first, then timestamps and editing metadata.
- Choose only the fields you want to remove.
- Export a new copy and keep its before/after manifest.
- Remember that platforms may recompress, transform, or re-encode media after upload.
Try the local checker: Open preflight and inspect a photo before you share it ↗