Adobe Firefly can attach tamper-evident Content Credentials to generated assets. This tool removes supported credentials stored inside JPG or PNG containers and can clean related XMP, IPTC, EXIF, creator, software, and date fields without uploading the file.
Supported JPEG APP11 and PNG caBX C2PA containers are removed locally alongside selected XMP, IPTC, EXIF, and ordinary metadata. The encoded image content is preserved when the original format supports container-only cleanup.
This page only handles file-level data the browser can safely inspect and remove, so ordinary metadata cleanup never triggers an upload or charge.
Detect and remove supported Content Credentials containers without converting the image into a screenshot or flattening it through a lossy round trip.
Review XMP, IPTC, creator, software, editing, date, and other supported fields that may accompany the provenance manifest.
Removing supported credentials embedded in the file is a browser operation and does not require a paid server job.
Adobe says a copy of Content Credentials may also be stored in its public Content Credentials cloud. Removing the embedded file manifest does not delete a remote record or guarantee that Adobe's Inspect service cannot recover related provenance.
File formats are messy. These answers describe the supported behavior of this version—not a promise that every trace everywhere has disappeared.
It removes supported C2PA containers embedded in JPG and PNG files and reports the result. Unsupported, malformed, external, or future manifest formats may not be removed.
No. A local file cleaner cannot delete a credential copy stored by Adobe or another provider. It only changes the downloaded file you select.
For supported original-mode JPG and PNG cleanup, the credential container is removed without recompressing the encoded image pixels.
