An image file can contain more than visible pixels. Cameras, phones, scanners, and editing software may add metadata that helps organize or interpret a file. Some of it is harmless; some can reveal details you did not intend to share.
Common metadata fields
EXIF data can include camera make and model, lens, exposure, focal length, ISO, orientation, and capture time. A device may also store GPS coordinates when location tagging is enabled.
Other metadata systems can contain copyright fields, creator names, keywords, captions, color profiles, software identifiers, editing history, or application-specific values. PNG and WebP have their own chunks and containers; metadata is not exclusive to JPEG.
Not every file contains every field. Messaging apps and social platforms may strip or rewrite metadata, while direct file sharing may preserve it.
Why orientation matters
Some photographs store camera pixels in one orientation and use EXIF Orientation to tell viewers how to rotate them. A metadata-removal workflow must first decode the image with the orientation applied, then write the pixels in their visible direction. Otherwise, the clean copy can appear rotated.
ImagesCompressor requests orientation-aware decoding from browser image APIs before re-encoding. Browser behavior can still vary, so inspect the downloaded result.
How local re-encoding removes metadata
The remove image metadata tool decodes the source into pixels and writes a new JPEG, PNG, or WebP. It does not copy source metadata blocks into the output. This is a robust removal approach for the supported formats.
Re-encoding is different from deleting selected EXIF tags. It creates a new file, which also means a lossy output such as JPEG or WebP can change pixel detail. Choose PNG when lossless pixel storage is more important than size, or use a suitable quality for photographic output.
For the broader question of what local, browser-based processing does and does not protect, see How Browser-Based Image Processing Protects Privacy.
What metadata removal does not hide
Removing EXIF cannot conceal information visible in the picture. Faces, vehicle plates, documents, street names, QR codes, reflections, screens, and recognizable locations remain in the pixels.
It also does not control copies that already exist. If you previously uploaded the original, creating a clean version does not remove metadata from that earlier copy.
File-system metadata is separate. Your computer may track creation dates, tags, cloud history, or permissions outside the bytes of the image. A downloaded clean copy gets new file-system properties from the destination environment.
A safer sharing checklist
- Work from a copy and retain the original privately.
- Remove embedded metadata through a verified re-encode.
- Inspect the visible image for sensitive details.
- Confirm the orientation and colors of the output.
- Share through a channel whose privacy behavior you understand.
For especially sensitive content, do not rely on a general-purpose web tool alone. Use an offline, audited workflow appropriate to your risk level.
Conclusion
Metadata can be useful, but it deserves review before public sharing. A clean re-encode prevents supported source metadata from being copied, while a visual inspection catches sensitive information that no metadata tool can remove automatically.