Remove metadata from JPEG images

JPEG metadata beyond the image

A JPEG can carry location, authorship and device fields in EXIF, IPTC or XMP. Comments, previews and private application segments are separate structures to inspect. The report describes what the selected file contains; a camera model or extension does not establish that a particular field is present.

• EXIF/GPS fields, author/device/software details
• IPTC authorship/contact fields and XMP properties
• Comments, MakerNote, thumbnails/previews and unknown application segments

Supported JPEG metadata removal

The supported path removes parser-identified EXIF, IPTC and XMP fields and containers, then independently checks the processed bytes. Read the field and container findings together. A removed author field does not by itself show that an embedded preview, private segment or other unassessed structure has been cleared.

Retained JFIF and colour structures

A JFIF header can be needed for compatible display, and an assessed public ICC profile can be needed for colour rendering. Those structures have separate dispositions from privacy metadata. The parser treats a JFIF thumbnail differently from the header, so check exactly which structure the report kept.

• The assessed JFIF header, without an embedded thumbnail.
• An ICC colour profile assessed as public and structural.
• Compressed image data and the structures required to decode it.

JPEG limits and unresolved findings

Private extensions and malformed application segments can prevent the parser from establishing a complete result. The workflow does not promise to understand every MakerNote or vendor payload. Check residual and unassessed findings rather than inferring support from the filename, file size or the visible image alone.

• An embedded JFIF thumbnail has a separate privacy disposition from the retained header.
• Private ICC extensions and malformed segment boundaries can remain unassessed or cause processing to fail.
• Every private application segment or MakerNote is not necessarily understood.
• No generic file size or processing-time guarantee applies.