Back to home

Supported Formats & FAQ

See supported image formats, metadata cleanup limits, retained orientation and color information, and troubleshooting for AI Metadata Remover.

Last updated: 2026-11-18

Supported formats

FormatInspected and cleanedPreserved
Static JPG/JPEG

EXIF including GPS, standard XMP, Photoshop/IPTC resources, comments; conservative handling of C2PA candidate segments

Compressed scan data, JFIF display data, ICC profiles, Adobe color transform, necessary orientation

Static PNG

EXIF, tEXt/zTXt/iTXt text, modified time, embedded caBX credential containers

IDAT, palette, transparency, supported color and display chunks, necessary orientation

Static WebPEXIF, XMP, embedded C2PA credential containers

VP8/VP8L image data, transparency, ICC profile, necessary orientation; RIFF size and flags updated

Static HEIC / HEIF (HEVC)

Supported EXIF/GPS, XMP metadata items, item/handler descriptions, and unused media/padding bytes

Original HEVC data, codec and display properties, supported ICC/color/rotation/alpha/depth/HDR-gain-map data, thumbnails, and necessary minimal EXIF orientation

Static AVIF

Supported EXIF/GPS, XMP metadata items, item/handler descriptions, and unused media/padding bytes

Original AV1 data, transparency, supported ICC/color/rotation/HDR properties, and necessary minimal EXIF orientation

Credential containers are reported without verifying signatures or assertions. Complex multi-segment JPEG credential layouts and unfamiliar containers may be rejected. Support for one embedded layout does not establish compatibility with every generator. The tool never promises that an image is AI-generated or that a platform label will disappear.

HEIC/HEIF and AVIF processing

These formats keep their original format; files are not converted to JPEG or PNG and no decoder or file is downloaded from a third party. Cleanup edits the image container, removes supported EXIF and XMP records and their references, and clears obsolete payload bytes. Required orientation may remain in a minimal EXIF item. The output is parsed again and the retained coded image data and supported display properties are compared byte for byte.

A successful check concerns the supported container structure, not full validation of the underlying HEVC or AV1 bitstream. The tool tries the browser's native preview. If the browser lacks the decoder, it shows a preview-unavailable notice and still permits container-verified cleanup. You should open the copy in an app that supports the format. The filename extension and MIME type follow the detected format.

Animation/track containers, unrelated photo collections, external data references, overlapping payloads, encrypted items, unknown boxes, and unsupported item/property layouts are rejected. HEIF/AVIF C2PA or JUMBF layouts are not supported in this version and fail closed rather than being marked clean. HEIF here means the supported HEVC still-image layouts, not every codec that can be placed in HEIF. Thumbnails and supported display auxiliaries are retained and listed.

Removed data is replaced by zero-filled space to keep remaining item offsets correct, so file size may stay the same. This is metadata cleanup, not file compression.

Limits

One photo at a time, up to 20 MB (20,000,000 bytes), 40 megapixels, 4,096 interpreted fields, 8,192 container segments, eight levels of EXIF directory traversal, and a total 1 MB decompressed metadata-text budget. A task is canceled after 15 seconds. There is no daily quota.

Animated PNG/WebP/AVIF/HEIF, multi-photo collections, TIFF, RAW, PDF, video, JPEG extensions outside the supported paths, and damaged or ambiguous files are rejected. A misleading filename extension does not change the real file type. Unknown containers block cleanup instead of being silently retained or removed.

Do my photos leave the browser?

No. Files, previews, names, and field values remain on your device. This version has no analytics, ads, session replay, or upload endpoint. See Privacy.

Does cleaning affect image quality?

The tool does not re-encode the compressed image data. It preserves supported display-related information and re-inspects the output before offering a download. Your browser must also be able to decode the result. Keep your original and check appearance in your intended viewing app.

Why is some EXIF still present?

A fresh minimal EXIF directory may retain only the orientation needed for correct display. Removing every EXIF byte could rotate the image in some viewers. Retained information is listed in your report.

What if nothing is found?

“No supported removable metadata found” means nothing removable was found within the supported fields. It is not proof of human authorship, authenticity, privacy in every context, or the absence of invisible watermarks.

Why might an AI label remain?

A platform may use pixel signals, watermarks, historical records, or other information. This tool cannot modify existing posts or guarantee how a platform classifies an image. C2PA can describe many types of creation, and removing embedded credentials does not delete external records.

What if I get an error?

Check the file size and format. Try a current browser and a smaller static image. Unknown containers, failed integrity checks, and unsupported encodings block downloads because the output cannot be fully verified. Choosing another photo or canceling clears the current task; your original remains unchanged.

Contact

Email hello@metadataclear.com for product support or to report a reproducible issue. Describe the error, format, and browser without attaching private files or copying sensitive metadata.

Reproduce a cleanup

Use the public verification sample to inspect a known synthetic PNG, compare the cleaned output and reproduce the result. It contains invented values, not a personal photo or a certified export from an AI generator.

Technical references

  • W3C PNG specification: the distinction between image-data chunks, text chunks, and EXIF metadata.
  • C2PA Content Credentials specification, version 2.2: provenance records, validation and soft bindings. Embedded container inspection by this tool is not signature validation; external records may still exist.
  • Content Credentials: provenance information can describe how content was created and edited; a credential is not by itself proof of AI authorship.
  • Google DeepMind SynthID: invisible watermarking is a different mechanism from file metadata. This tool preserves the compressed image data and does not remove such watermarks.

References describe the underlying technologies. They do not certify this tool or establish that any platform will remove a label. See AI labels and metadata for that boundary.

Contact: hello@metadataclear.com