Skip to the tool

Methodology

How Untagly reads and removes metadata

This page documents what the tool does to your file, block by block, so you can judge the result for yourself and check it with other software.

Last updated

The short version

  1. Your browser reads the file into memory. Nothing is uploaded.
  2. Untagly walks the file’s container structure and identifies each metadata block by its marker.
  3. Each block is classified by type and checked for AI-related content.
  4. A new file is produced from the original bytes without the blocks you chose to remove. In JPG, PNG and WebP they are left out. In HEIC and AVIF they are overwritten in place.

The image is never decoded. Compressed pixel data is copied from the old file to the new one byte for byte, which is why there is no quality loss and why the tool is fast even on large photos.

What it reads in each format

FormatBlockReported as
JPGAPP1 starting with ExifEXIF
JPGAPP1 with the Adobe XMP namespaceXMP
JPGAPP11 (JUMBF)C2PA
JPGAPP13 (Photoshop / IPTC-IIM)IPTC
JPGCOMText
PNGcaBXC2PA
PNGiTXt keyed XML:com.adobe.xmpXMP
PNGeXIfEXIF
PNGother tEXt, iTXt, zTXt, and tIMEText
WebPC2PA chunkC2PA
WebPXMP chunkXMP
WebPEXIF chunkEXIF
HEIC / AVIFitem of type ExifEXIF
HEIC / AVIFmime item with content type application/rdf+xmlXMP
HEIC / AVIFuuid box carrying the C2PA identifierC2PA

Why HEIC is handled differently

A JPG is a chain of segments, so a segment can be dropped and the rest still lines up. A HEIC, the format iPhones use by default, is an index: a table near the start of the file records the exact byte position of every item, including the image tiles. Cutting bytes out would shift everything after them and break that table.

So for HEIC and AVIF the tool leaves the structure alone and overwrites the contents of the metadata items. An EXIF item becomes an empty EXIF record, an XMP item becomes an empty XMP packet padded with spaces, and a Content Credentials box is zeroed and marked as free space. Three consequences follow:

  • The cleaned file is exactly the same size as the original.
  • Other software will still see that an EXIF or XMP item exists, but it will find nothing inside. Untagly’s own scanner reports such an emptied item as “not present”.
  • Rotation and color are unaffected, because HEIC stores them as image properties and not in EXIF. No orientation value needs to be written back.

HEIC support is newer than the other formats and has been checked against fewer real-world files. If a photo from your phone is read incorrectly, please tell us which device and iOS version produced it.

How a block becomes an “AI trigger”

The red marking in the inspector follows fixed rules:

  • Any C2PA manifest is flagged. Platforms check for Content Credentials first, and the tool does not parse the manifest deeply enough to tell a harmless one from one that records a generative action. Flagging all of them is the cautious choice.
  • XMP, IPTC, EXIF and text blocks are flagged when their content matches known AI signals. These are the IPTC source types ending in AlgorithmicMedia, references to C2PA, and the names of generative tools and models.
  • PNG text chunks keyed parameters, prompt or workflow are flagged. These are the keys Stable Diffusion front ends use to store generation settings.

This is pattern matching, not a verdict on the image. A block can be flagged because an editor’s name contains a matching word, and a file with unusual tagging could slip through. Open any row to read what was matched.

What is kept

  • Image data. Every byte of compressed pixel data, in the original order.
  • Color profile. ICC profiles are left in place so colors do not shift.
  • Orientation. When EXIF is removed from a JPG, the tool writes back a minimal EXIF block that holds only the orientation value. Without it, portrait photos would display sideways.
  • Unflagged blocks, in “AI tags only” mode. Camera EXIF and other metadata with no AI reference stay in the file.

Metadata is removed a whole block at a time. If your copyright notice sits in the same XMP packet as an AI source tag, both go. The tool does not edit individual fields inside a packet.

Known limits

  • Invisible watermarks. Marks such as SynthID are embedded in the pixels. No metadata tool can see or remove them.
  • Formats. TIFF, RAW and video files are not supported. For a Live Photo, only the still image is handled, not its video.
  • HEIC items stored indirectly. The tool follows metadata items stored in the file body or in the item data box. An item assembled from other items is skipped and left as it is.
  • Data after the end of a JPG. Some phones append a second image or a depth map after the main picture. The tool leaves anything after the image stream untouched, so metadata inside that appended data is not removed.
  • Signature validity. The tool reports that a C2PA manifest is present. It does not verify the signature or read the individual assertions.
  • Platform behavior. A file with no metadata can still be labeled if the platform’s own detection decides to.

How to check the result yourself

You should not have to take our word for it. Three independent checks:

  • Run exiftool -a -G1 yourfile.jpg on the original and on the cleaned copy and compare the output. ExifTool is free, open-source software.
  • Upload the cleaned copy to the Content Authenticity Initiative’s public Verify tool. It should report no Content Credentials.
  • Compare the pixels. Open both files in an image editor as layers and set the blend mode to Difference. The result should be solid black.

If any of these shows something the tool missed, please send us the details. Reports like that are how the parser gets better.