How to Remove C2PA Metadata From Images

There are three ways most people end up doing this, depending on how much precision you need. Easiest: re-encode the image in your browser. Most precise: exiftool on the command line. Somewhere in between: re-encode with ImageMagick, cwebp, or ffmpeg. All three are below, along with how to confirm it actually worked, because you shouldn't just take our word for it.

The part we have to say, and do mean. Provenance data exists for real reasons. Stripping it to pass off someone else's work, hide that something's AI when people deserve to know, or dodge a disclosure you're actually required to make is the one thing this tool isn't for. See Acceptable Use.

Method 1: Browser-based re-encode (easiest)

Open noc2pa.com, pick a PNG or WebP, and download the JPG it hands back. The image is decoded onto a canvas and re-encoded right there in your browser, which throws away the original metadata container (C2PA manifest included) as a side effect. It's the no-fuss option: nothing to install, and the file never leaves your machine. The trade-off is that JPG is lossy and the output is always a JPG, so it's best for a quick cleanup before you share something, not for archival work.

Method 2: ExifTool (most precise)

ExifTool can drop metadata in place without touching the pixels. The most aggressive version:

exiftool -all= -overwrite_original input.jpg

To go after only C2PA / JUMBF and leave normal EXIF and XMP alone (on recent ExifTool versions):

exiftool -jumbf:all= -overwrite_original input.jpg

This is the precise option. It's lossless, it scripts cleanly, and it'll drop just the JUMBF data while keeping your EXIF if that's what you want. The catch: C2PA coverage depends on your ExifTool version and the file format, and you do need to be comfortable at a command line. The ExifTool detail page digs into where it's reliable and where it isn't.

Method 3: ImageMagick / cwebp / ffmpeg re-encode

Re-encode an image through almost any tool that doesn't deliberately carry metadata forward, and the embedded C2PA manifest gets dropped along with everything else. A few ways to do it:

# ImageMagick: strips all metadata as part of the re-encode
magick input.png -strip output.jpg

# cwebp → JPEG via dwebp piped to a JPEG encoder, or via ImageMagick
magick input.webp -strip output.jpg

# ffmpeg: can also re-encode and strip
ffmpeg -i input.png -map_metadata -1 output.jpg

This is the option that slots into a pipeline you already have. It runs anywhere these tools are installed and behaves predictably. Just remember the -strip or -map_metadata -1 flag is doing the real work. Leave it off and some tools will happily copy the old fields straight into the new file.

Does this work on AI-generated images?

If an AI-generated image carries Content Credentials in a supported format, every method here strips the embedded manifest from the output. What it doesn't do is make the image undetectable as AI. Plenty of services lean on pixel-level fingerprints, invisible watermarks, or hash-matching against known generations, and a metadata strip doesn't lay a finger on any of that. And to be blunt: pulling provenance to fool an audience is exactly the use our Acceptable Use Policy rules out.

Verifying the result

Don't assume it worked. Check.

  1. Drop the output into the official Content Credentials Verify tool. If there's no manifest left, it'll tell you.
  2. Run it through our C2PA Checker for a quick second opinion.
  3. On the command line, exiftool -G1 -a -s output.jpg lists every group ExifTool can see. Make sure no JUMBF group is still in there.

What none of these methods do

Related

Use the C2PA remover