Remove Content Credentials From an Image

"Content Credentials" is the name Adobe and the C2PA alliance gave to the provenance information that can be baked into an image: who made it, what tools touched it, whether AI was involved, how it was edited. Under the hood it's the C2PA standard doing the work, usually as a JUMBF box tucked inside the file.

If you'd rather not carry all that around, say to keep personal metadata off a picture before it goes public, the simplest fix is to re-encode it. That's all our tool does: drop a PNG or WebP into the converter and it hands back a JPG with the embedded provenance stripped out in the process. It all happens in your browser. The image isn't uploaded anywhere.

One honest caveat first. Content Credentials do help viewers and platforms understand how an image was made. Stripping them to mislead people who reasonably expect that context isn't something we can technically stop you doing, but it's squarely against our Acceptable Use Policy, and we'd ask you not to.

Why a re-encode removes Content Credentials

Content Credentials live in a structured block bolted onto the file. JPEG keeps it in an APP11 marker, PNG in a custom chunk, WebP in RIFF chunks. Re-encode the image, whether you're saving from a graphics app, piping it through a converter, or painting the pixels onto a canvas and exporting fresh JPG bytes, and only the pixels survive. The provenance container doesn't ride along, so the new file has no copy of the original manifest.

It's a side effect of re-encoding, not some clever bypass. The same thing happens every time an image gets screenshotted, cropped in a lot of apps, or squeezed through a messaging app that doesn't bother keeping metadata.

How to remove Content Credentials with noc2pa

1. Open noc2pa.com.
2. Use the file picker to select a PNG or WebP file.
3. The image is decoded onto a canvas and re-encoded as JPG, locally in your browser.
4. Click Download as JPG. The output JPG does not carry the original Content Credentials manifest.
5. To confirm, run the output through the C2PA Checker or upload it to the official Content Credentials Verify tool.

What this won't do

• It won't reverse public, distributed provenance. If a Content Credentials manifest points to an externally-stored claim (a "soft binding" or cloud-side record), clearing the embedded manifest from your local copy does nothing to that external record.
• It won't fool every detection method. Some platforms can identify AI-generated images via pixel-level signals (invisible watermarks, statistical fingerprints) independent of any embedded metadata.
• It won't make a re-encoded JPG identical to the original. JPG is lossy. If you need pixel-perfect output, this isn't the right tool.

Removing Content Credentials with other tools

On the command line, re-encoding with ffmpeg, cwebp, or ImageMagick drops C2PA data the same way a browser canvas re-encode does. ExifTool can strip many fields without re-encoding at all, though its C2PA handling is format-specific, so see Can ExifTool remove C2PA metadata? for the messy details.

Frequently asked

Is the file uploaded to your server?

No. It all runs in your browser with FileReader and <canvas>. The bytes never leave your device, and we never see them.

Does this work on AI-generated images?

If an AI-generated image carries Content Credentials in a supported PNG or WebP, the re-encode drops the embedded manifest from the JPG you get back. Just don't use that to misrepresent how the image was made.

Why JPG output specifically?

Because JPG opens everywhere, and a pure-pixel re-encode to JPG is dead simple in a browser. Other targets would work too. We landed on JPG because it's the one format you can count on anywhere.

Will the new JPG ever be detected as having had Content Credentials before?

The JPG itself doesn't carry the original manifest. Whether someone can still infer the image once had Content Credentials comes down to signals outside the file: pixel-level watermarks, hash-matching against a published claim, that sort of thing. This tool only deals with the embedded metadata.

Use the C2PA remover