Can ExifTool Remove C2PA Metadata?

Short answer: partially, depending on the file format and what's inside. ExifTool is excellent at editing the metadata structures it knows — EXIF, IPTC, XMP, and many camera-specific fields. C2PA / Content Credentials is a newer, structurally different layer (a JUMBF box wrapped in format-specific containers) and ExifTool's coverage is uneven across formats. This page walks through what works, what doesn't, and what to verify afterward.

How C2PA is stored, and why that matters for ExifTool

C2PA manifests are packaged inside JUMBF boxes embedded into the image file. The container that holds the JUMBF box is format-specific:

JPEG: APP11 marker segments.
PNG: a custom caBX chunk.
WebP: RIFF chunks.
HEIF / AVIF / MP4: ISOBMFF boxes.

ExifTool can read and (for some formats) remove these containers. But C2PA isn't a standard "tag" you can target with -EXIF:all=. Whether ExifTool drops it depends on whether the format-specific writer module includes the JUMBF segment when it rebuilds the file.

What works today

The most reliable single command for stripping every metadata field ExifTool knows about is:

exiftool -all= -overwrite_original input.jpg

For JPEG, this strips EXIF, IPTC, XMP, and Photoshop blocks, and in current ExifTool builds it also drops the APP11 segment that carries C2PA on JPEG. For PNG, the same command drops standard textual chunks; whether it also removes the caBX chunk depends on your ExifTool version. Newer builds explicitly recognize and can remove JUMBF / C2PA chunks; older builds may pass them through untouched.

To target only C2PA-related structures (without nuking everything else), recent ExifTool builds support:

exiftool -jumbf:all= -overwrite_original input.jpg

This deletes JUMBF data while leaving normal EXIF and XMP intact — useful if you want to drop C2PA but keep the camera and editing metadata.

Where it gets fuzzy

WebP and AVIF: ExifTool's coverage of C2PA inside RIFF / ISOBMFF containers has been improving but isn't guaranteed across versions. Verify the result.
Older ExifTool builds: pre-12.50 builds did not recognize the C2PA-specific PNG chunk. If you're on a system with an older build, the caBX chunk may pass through your "-all=" command intact.
Sidecar / external claims: a C2PA manifest can reference data stored outside the file (a "soft binding"). Removing the embedded manifest does nothing about external records.

Always verify the output with the official Content Credentials Verify tool rather than trusting that the command did what you wanted.

Re-encode vs. ExifTool: which should you use?

For most users, the practical difference is:

Approach	Pros	Cons
ExifTool	Lossless — pixel data is preserved exactly. Granular — you can drop just JUMBF and keep EXIF if you want. Scriptable.	Coverage of C2PA depends on ExifTool version and file format. Requires command-line comfort.
Browser re-encode (e.g., noc2pa.com)	Predictably drops everything in the original container. No tools to install. Output JPG is universally compatible.	JPG is lossy — pixel-perfect output is not preserved. Drops all metadata, including fields you might have wanted to keep.

If you care about lossless output or want to keep some metadata, use ExifTool and verify. If you just want a clean JPG to share, the in-browser converter is faster and harder to misconfigure.

How to verify the result

Run the file through the Content Credentials Verify tool. If no manifest is present, the page will say so.
Use our C2PA Checker for a quick second opinion.
Check with exiftool -G1 -a -s output.jpg to list every group and tag ExifTool can see, and confirm there's no JUMBF group remaining.