An image can carry information that is not visible in its pixels. Depending on the camera, phone, editor, and format, metadata may describe the device, lens, capture time, software, author, copyright, orientation, and precise location.
Metadata is not automatically harmful. Photographers use capture settings, archives use dates, and color profiles help rendering. Privacy risk appears when a file is shared outside its original context without understanding what travels with it.
Common metadata groups
EXIF commonly contains camera and capture data. GPS tags can hold latitude, longitude, altitude, and direction. IPTC and XMP may include editorial descriptions, creator information, rights fields, keywords, or editing history. PNG can store text chunks, while JPEG can include comments and application markers.
An embedded thumbnail may be another copy of the image. In unusual workflows it can reveal an earlier crop or edit if software fails to update it correctly.
Why GPS deserves special attention
Precise coordinates can reveal a home, workplace, school, private event, or routine. A public platform may strip metadata on upload, but you should not assume every messaging app, forum, storage provider, or recipient does so.
Inspect the exact file you plan to share. A copy exported by one application may differ from the camera original.
Local inspection reduces exposure
A local metadata viewer reads supported fields in the browser. The metadata does not need to be sent to a website backend. Safe display also matters: malformed strings should be escaped rather than inserted as raw HTML.
The viewer should report what it found, not claim knowledge of every proprietary block. Maker notes and format-specific extensions can be difficult to interpret reliably.
How removal works
For raster images, decode-and-re-encode is a practical cleaning strategy. The browser decodes visible pixels, applies orientation, and creates a new file without carrying common source metadata into the output. This also means some color-profile or high-bit-depth information may change.
SVG needs a different approach because it is markup. Sanitization removes scripts, event-handler attributes, external references, foreign objects, comments, editor metadata, and unsafe style constructs while preserving useful title or description elements when possible.
A privacy checklist
Before sharing a sensitive image:
- Keep a private original.
- Inspect the sharing copy for GPS and identifying fields.
- Apply orientation before removing its tag.
- Remove common metadata.
- Reopen the cleaned file in a separate metadata tool when the stakes are high.
- Confirm that the visible pixels themselves do not reveal location, names, reflections, documents, or screens.
Metadata cleaning cannot remove information that is visibly photographed. It also does not guarantee removal of every undocumented vendor block.
Use the image metadata viewer to inspect supported fields and the metadata cleaner to create a re-encoded sharing copy locally.
Put the guidance into practice
Use the image compressor, image converter, or metadata cleaner to test these choices locally with your own files.