GPS Removal Results for JPEG, PNG and WebP

The privacy path targets EXIF/GPS and ordinary XMP or text metadata where supported. ICC color information is not treated as private location data.

A street sign, building, face or address visible in the pixels remains visible. GPS cleaning reduces metadata exposure but is not complete anonymization.

JPEG uses marker segments, PNG uses length-prefixed chunks and WebP uses RIFF chunks. A safe cleaner cannot apply one search-and-delete routine to all three without risking damaged sizes, flags or compressed image data.

The common product promise is the outcome: create a new file, remove supported privacy blocks and reparse it. The implementation underneath remains format-specific.

Each controlled file contained a known, non-personal coordinate in a supported metadata structure. The lab confirmed GPS before cleaning, ran the format-specific path and used the same parser to inspect the result.

Synthetic coordinates make the result repeatable without publishing anyone’s home or movement. They test code behavior; they are not a survey of phones, cameras or social platforms.

GPS was present in each input and not detected in each accepted output. JPEG scan data, PNG IDAT and WebP image payloads remained on the metadata-only paths. The cleaner created separate files and never changed the selected input.

The result supports supported container structures only. A corrupt length, unusual variant or unsupported format produces a professional error rather than a clean claim.

Dimensions and encoded image data remain. ICC color information stays by default because it affects appearance rather than precise location. Required orientation is handled cautiously so a portrait does not turn sideways after cleaning.

Content Credentials are different: removing or rewriting container information can invalidate provenance. Check C2PA before cleaning and expect the derivative to need its own validation result.

A coordinate in pixels, a street sign, recognizable building or route map remains visible. A cloud photo library may also hold location in its database even when the exported image is clean.

Treat the result as one privacy layer. Review the visible scene, filename, sharing audience and platform behavior before deciding that a copy is appropriate to publish.

If chunk lengths are invalid, dimensions exceed the safety guard or output cannot be reparsed, the operation stops with a specific error. The tool does not replace “unknown” with “GPS removed” merely because a download blob exists.

This distinction matters in batch workflows, where one damaged file can be easy to overlook. Every accepted output needs its own result row; every failure needs a reason and recovery step.

The downloaded filename is not evidence either. A “clean” suffix describes the intended operation; only the second parse demonstrates that supported GPS fields are no longer readable in the accepted output.

When a format is unsupported, return to the original application and export a supported privacy copy instead of forcing a parser through unknown bytes.