Guide
Photo EXIF and GPS metadata privacy
A shared photo can carry a second, invisible description: where it was taken, which camera took it, and who last edited it. This page explains those fields, what the local photo scanner can see, and what it leaves alone.
What EXIF and GPS actually store
JPEG, and often WebP, can embed a TIFF-style EXIF block. Common tags include Make, Model, DateTimeOriginal, Artist, and a GPS IFD with latitude and longitude. PNG more often stores the same ideas in text chunks or an XMP packet. XMP is XML and can repeat creator, date, and location values that also appear in EXIF.
Those values are useful for a photographer and risky in a group chat or a public album. A GPS fix can point at a home. A serial number or lens id can tie many files to one device. A timestamp can line up with other posts.
What the local scanner checks
The photo tool accepts JPEG, PNG, and WebP up to 50 MB. It parses supported metadata in the browser and can report types such as IMAGE_GPS_LOCATION, device make and model, capture time, artist, copyright, user comment, and selected XMP fields. A file that is not one of those formats stops with an unsupported-type message and does not produce a findings list.
Processing uses a same-origin worker. The page does not upload the photo to PrivacyFileLab. You can clear the selection in the page. That clears this tab’s view; it does not reach into other apps that already received the file.
Detection is not the same as removal
The first result is a list. Nothing is rewritten until you choose Clean metadata. Cleaning builds a new file without the supported tags the scanner found, then scans that output. Download the cleaned file only after you have read the before and after counts. Keep the original somewhere you control until the cleaned file opens and looks right.
Removal cannot promise that every private tag from every camera vendor is gone. Some makers store notes in places this version does not name. If a tag matters, open the cleaned file in another metadata viewer you trust and compare.
What stays in the pixels
This scanner does not look at faces, license plates, whiteboards, or screenshots. A photo of a boarding pass is still a photo of a boarding pass after metadata is removed. Stripping GPS also does nothing about a street sign in the frame. If the picture itself is sensitive, cropping or not sharing it is the control that matters.
A fictional example
Imagine a JPEG exported from a phone. The EXIF GPS IFD says 37.77500, -122.41944, the model string is a camera name, and DateTimeOriginal is last Tuesday evening. The scanner should surface the GPS and device fields. A PNG with an Author text chunk should surface that author. A WebP with an EXIF make tag should surface the make. None of these findings describe the people in the frame.
Those coordinates are an illustration, not a place you should look up. After cleaning, scan the downloaded file again. If GPS is gone from the supported fields and the picture still shows a house number, the metadata risk changed and the visual risk did not.
Frequently asked questions
Quick answers from this guide.
Does “no findings” mean the photo is anonymous?
No. It means this version did not find the metadata fields it knows. The pixels can still identify a person or a place.
Should I clean every photo before a private family chat?
Clean when the receiver should not learn your camera identity or a precise location. For a chat that already knows where you live, the visible content may be the larger question.
Can this page read GPS from the browser itself?
No. Geolocation is disabled by the Permissions-Policy, and the only coordinates considered are those inside the file you select.