A guide to sensitive JPEG/PNG metadata, in-browser removal, and verification of the sanitized result.
What travels beyond the pixels
JPEG files can contain camera, lens, time, orientation, software, and GPS EXIF fields. PNG can carry text chunks, color profiles, and application-specific data. File names and cloud-sharing records are separate metadata layers.
Risk depends on context. A camera model may be harmless in a product shot, while exact coordinates from a home photo can expose routines or location.
Why removal often means re-encoding
A broadly compatible browser approach decodes the pixels, draws them to a clean canvas, and exports a new image without copying common EXIF blocks. JPEG quality or size may change, and animation or specialist color profiles can be lost.
Create a new copy instead of overwriting the source. Use a descriptive new name that contains no personal information.
Inspect, clean, and verify
A short detected-field list is not proof that every proprietary block is absent. After cleaning, upload the downloaded copy again and inspect it. For high-risk publication, verify with an independent desktop tool.
Metadata removal cannot hide faces, plates, documents, reflections, or landmarks visible in the pixels.
- Scan the cleaned copy again.
- Review sensitive details inside the image.
- Keep the source in controlled storage.
Build an organizational sharing standard
Use a fixed intake pipeline for journalism, field work, or customer support: source verification, personal-data review, metadata removal, visual redaction, and publication approval. Do not assume a messaging app always strips metadata; behavior changes by app and transfer mode.
If later integrity evidence is needed, record a SHA-256 digest of the source in restricted storage. A digest does not conceal a file; it only helps detect changes.
Visual suggestion: A three-panel diagram showing the original photo, metadata layer, and verified clean copy. This article is general information, not legal or security advice.