EXIF, XMP, IPTC, and GPS metadata explained for photo sharing.

EXIF: camera and capture context

EXIF is commonly written by cameras and phones. It can include camera model, lens details, exposure settings, capture time, orientation, embedded thumbnails, and sometimes GPS coordinates. This information is useful when organizing private photo libraries, but it is often unnecessary when a photo is posted publicly or sent outside a trusted group.

XMP: editing and workflow information

XMP is flexible metadata used by many editing, design, and publishing tools. It can store labels, ratings, creator names, software history, descriptions, and workflow fields. A photo exported from an editor may carry XMP even when the visible image looks final. Public copies rarely need internal editing history.

IPTC: captions, rights, and publishing data

IPTC metadata is common in photography, journalism, media libraries, and agency workflows. It may include captions, copyright notices, creator information, keywords, location descriptions, and licensing context. Unlike some metadata, IPTC can be important for attribution. Before removing it, decide whether rights information should remain in the file or be communicated elsewhere on the page where the image appears.

Embedded thumbnails

Some image files contain embedded thumbnails or preview data. In older workflows, previews may not match the final visible image. Removing common metadata containers can reduce this risk, but users should still open the cleaned output and check the actual image.

What this cleaner actually removes from PNG

The DataClean PNG path removes tEXt, iTXt, zTXt, eXIf and tIME chunks. It copies the remaining chunks instead of re-encoding the pixels. That distinction matters: text comments can disappear while color-management chunks and image dimensions remain.

On the home page, Run sample check adds a synthetic Comment in a tEXt chunk, calls the same cleaner used for your PNG files, and compares the compressed IDAT bytes before and after. The result is calculated in your browser. It is a narrow, reproducible check of comment removal, not a claim that every file or PNG extension is covered.

Why some metadata should remain

PNG color information and transparency help a viewer display an image. Removing every non-pixel byte indiscriminately can damage appearance. Unknown private chunks are not removed by this implementation. If you need exhaustive removal of vendor-specific information, inspect the output with a separate tool and use a workflow designed for that format.

The W3C PNG specification distinguishes image, text, color and animation chunks.

Match the container to the question

Report row	What the count tells you	What it does not tell you
JPEG APP1	EXIF/XMP-style segments are present	Whether a particular segment contains GPS
JPEG APP13	Photoshop/IPTC-style segments are present	Whether attribution is legally required
PNG tEXt/iTXt/zTXt	Text containers are present	Whether the text is sensitive
WebP EXIF/XMP	Recognized chunks are present	Whether unknown private data also exists

Two exports of the same photograph can differ

A camera JPEG may carry EXIF while a design-tool PNG of the same pixels carries a software comment. They look alike, but a filename or visual comparison cannot tell you which metadata structure each uses. Inspect the actual final export. Do not infer that the PNG is automatically free of metadata or that an EXIF-free image has no other descriptive fields.

Attribution before deletion

Ask the photographer or asset owner which credit and licensing information must travel with the image. Write any necessary public credit in the destination caption or asset record before deleting embedded attribution. DataClean cannot decide who owns the image or whether a field is needed for your agreement. Removing a copyright field does not remove copyright.