Check and remove supported GPS metadata from a photo
A photo may contain latitude, longitude and sometimes altitude in supported EXIF data. File Privacy can show recognized GPS coordinates and remove their containing supported metadata as part of a locally created clean copy.
Open the private checker →Why this information can matter
GPS metadata can be useful for organizing a library, but it can also reveal a precise capture location when a file is shared directly. Not every image contains GPS. Camera settings, screenshots, exports, edits and sharing services may omit, change or remove location fields. The only reliable first step for the particular file in your hand is to inspect that file.
Inspect, clean and verify the exact copy
Latitude and longitude are coordinates, not a judgment about whether a location is sensitive. Start with an invented or non-sensitive sample. Never upload your original to a map service merely to test this workflow.
- Open the File Privacy checker. Choose a JPEG/JPG or PNG no larger than 50 MiB with choose a file. Inspection starts in the browser; wait for the findings before deciding to clean.
- Review Exact GPS location and Show technical metadata. Write down only whether supported GPS is present when using a personal photo; do not paste private coordinates into a public bug report.
- If you want the supported metadata removed, choose Clean metadata. This removes supported containing metadata, not just one coordinate field, and creates a separate copy. Keep any original that you need for your private archive.
- Wait for Clean copy verified, then choose Download clean file. A successful re-scan is evidence about the parser's supported fields, not all possible metadata.
- Choose Choose another, then select the downloaded copy in the checker again. Supported GPS should no longer be reported. Confirm the image still opens and its pixel dimensions match the original. Review visible signs, labels, landmarks and the filename separately.
Worked result: a synthetic JPEG
Our non-personal test JPEG was 80 × 40 pixels and 1,358 bytes, with deliberately embedded coordinates 12.341667, 45.680556. Cleaning produced a 1,058-byte JPEG. Reopening it in the checker found no supported GPS; an independent image decoder confirmed the same 80 × 40 dimensions and identical decoded pixels, with no EXIF entries. This is a single container-removal example, not a compression guarantee or visual redaction. It does not show that every possible metadata format was removed.
What to do when the result differs
- No GPS finding: your file may lack supported GPS already. Do not manufacture a location finding or interpret this as proof of anonymity. Inspect visible information and other findings.
- Unsupported or invalid file: confirm the actual format, not just its extension. HEIC, WebP, RAW and PDF are not supported by this release. Keep the original and use a trusted workflow for that format.
- Cleaning or verification fails: do not share an unverified copy on the assumption it was cleaned. Keep the original private, note the error without disclosing metadata and stop.
- Verification passes but a place is visible: metadata removal does not erase pixels, addresses or recognizable landmarks. Review or redact visible content in an appropriate separate tool.
FAQ
Does cleaning change my original?
No. The downloaded file is a new copy. Backups, earlier uploads and other originals are not changed.
Does GPS removal guarantee privacy?
No. Unsupported metadata, filenames and visible clues can still reveal information. The checker does not certify anonymity.
What this version supports
The JPEG parser reads supported GPS information from TIFF/EXIF structures and can report latitude, longitude and altitude when present. The PNG parser can read supported GPS values from an eXIf chunk. Cleaning removes the supported containing metadata containers along with other supported sensitive metadata, rather than editing a single coordinate value in place.
Limits to keep in mind
A missing GPS finding does not prove that no location can be inferred. A filename, landmark, sign, reflection, map, document or visible address may reveal a place. Unsupported or proprietary metadata may also escape detection. File Privacy does not query maps, identify places, or guarantee anonymity; it reports and cleans the supported structures implemented in this release.
Inspection and cleanup run in your browser. Selected file bytes are not uploaded to FrAIFlow servers. The result describes only the supported structures this release can observe.
Related File Privacy guides
Check the file you plan to share
Use the real File Privacy checker for a supported JPEG/JPG or PNG file up to 50 MiB.
Check metadata locally →Browse all guides