What the Tool Can Check
- Whether a supported file contains embedded C2PA data
- Whether the cleaned copy no longer contains that embedded credential
- Whether ordinary payload and color data stayed intact
Learn what C2PA Content Credentials record, how they relate to AI labels, and what is lost when an embedded credential is removed.
Quick Answer
C2PA Content Credentials can carry provenance and editing history inside a file. This tool can remove a supported embedded credential from a new local copy, but that also removes the embedded provenance record from that copy.
Drop images here, paste from your clipboard, or choose files
JPG & PNG · WebP beta · Up to 25MB each · No upload
Last reviewed: 2026-09-03 Based on: official C2PA and Adobe documentation + local file-format testing Platform behavior may change
01
Inspect the file locally to confirm whether embedded C2PA exists.
02
Review the one-time warning before keeping a cleaned copy.
03
Download only the verified cleaned copy if you want a publish-ready variant.
04
Archive the original if you want to preserve provenance.
You lose the embedded provenance package and the editing history that can travel with that file copy.
Check supported file signals before posting a lightly edited real photo.
Guide →Inspect Photoshop exports for embedded credentials and AI-related metadata.
Guide →Review file-level signals before you publish a cleaned local copy to Facebook.
Guide →Understand which file signals, disclosures, and platform systems may contribute.
Guide →