How to Remove C2PA Content Credentials

C2PA Content Credentials are the new standard for content provenance. They're embedded as APP11/JUMBF segments in JPEG files and caBX chunks in PNG files. These credentials contain verifiable information about how an image was created — including the AI tool used, the prompt, creation date, and digital signatures.

Most "metadata removers" miss C2PA data entirely because they only target EXIF tags. Tools like ExifTool may strip EXIF but leave JUMBF segments intact. Even image re-encoding through canvas or image editors may preserve C2PA data if the software is C2PA-aware.

C2PA Content Credentials are used by Adobe Firefly, Microsoft Designer, Canva, Leica cameras, Nikon Z8/Z9, and many other tools and devices. If your image came from any of these sources, it likely contains C2PA data that standard metadata tools won't remove.

How to tell if your image has C2PA data. The easiest way is to drop the file into the checker below — if AI Provenance or C2PA Content Credentials show up, you have it. You can also try the official verify tool at contentauthenticity.org, which reads the manifest and shows the tool, date, and edit history. A JPG that is much larger than you would expect for its dimensions is another hint, because the JUMBF manifest adds weight. PNGs from Firefly or Designer often carry both a C2PA chunk and plain-text fields with prompts or job IDs.

Step-by-step: remove C2PA before sharing. First, keep a backup of the original in a private folder in case you need to prove ownership later. Second, drop a copy into the tool below and wait for the preview — it should list what was found and removed. Third, download the clean copy and verify it: run it through the checker again and confirm no C2PA entry appears. Fourth, use that clean copy for uploads, client delivery, or marketplace listings. Do the cleaning before you resize or convert formats, because some editors re-attach a fresh manifest when you export with Content Credentials turned on.

What gets removed vs what survives. A proper byte-level cleaner removes the APP11/JUMBF segment in JPEGs, the caBX / jumb chunks in PNGs, plus EXIF, XMP, IPTC, embedded thumbnails, and fields like Digital Source Type. What survives is the pixels themselves — colours, sharpness, and resolution stay the same. What does not survive is the verifiable history: once the manifest is gone, nobody can cryptographically prove from the file alone which AI tool made it. Note that platforms may still label an image as AI based on how it looks or on your own disclosure, even when the file is technically clean.

Common mistakes. The biggest mistake is running a file through a basic EXIF remover and assuming the job is done — most of those leave JUMBF untouched. Another is opening the image in Photoshop or Lightroom and re-exporting with Content Credentials still enabled, which writes a brand-new manifest right back in. People also forget about copies: they clean one JPG for a client but leave the original PNG with C2PA in a shared Drive folder, or they post the clean image but send the dirty one by email. Clean every distributed copy, not just the one you upload first.

Settings worth checking. In Photoshop, go to Preferences → History & Content Credentials and turn off automatic attaching if you do not want new exports to carry credentials. In Lightroom, check export settings for Content Credentials. In Canva and Firefly, look for provenance or Content Credentials toggles before downloading. Turning these off helps for future exports, but it does nothing for files you already downloaded — those still need to be stripped.

Frequently asked questions

Will removing C2PA reduce image quality?
No, when done properly. C2PA data lives in separate JUMBF segments, not in the pixels. A byte-level remover deletes those segments without re-encoding the image, so quality, resolution, and colours stay identical — the file just gets a little smaller.

Can I remove C2PA with ExifTool?
Sometimes, but not reliably. ExifTool is excellent for EXIF and XMP, yet JUMBF removal requires specific directives and does not work for every file type or manifest version. If you are not comfortable with command-line flags, a dedicated cleaner that handles JUMBF structurally is simpler and less error-prone.

Is it okay to remove C2PA data?
For your own images, yes — it is your file and your privacy choice. Just remember that removing the technical marker does not remove your responsibility to follow marketplace or platform rules about disclosing AI-generated content when they ask for it.

Drop your AI-generated images below to strip C2PA Content Credentials and all other metadata in one step. Vantawebs preserves your original image quality while removing every trace of provenance data.