About noc2pa.com

noc2pa.com started from a small irritation. More and more images now travel with a hidden record of where they came from, who made them, and what was done to them along the way. C2PA calls that record "provenance." Sometimes it's genuinely useful. A lot of the time it's just one more thing riding along inside a file. Our tool converts a PNG or WebP to a JPG right there in your browser, and the C2PA data gets left behind in the process. Nothing is uploaded, and there's no account to make. Around it we keep a few plain-English explainers and a small checker so you can see what's actually inside an image.

Why this site exists

To be fair, C2PA exists for good reasons. A verifiable trail of who made an image and how it's been edited genuinely helps newsrooms, and it gives creators a way to prove a piece is theirs. We're not going to pretend that doesn't matter.

But the same machinery cuts the other way. People share images every day without thinking about how much information is tucked inside the file, and provenance is one more layer of it. Stripping metadata before you post something isn't shady. Photographers and privacy-minded people have done it for years.

So this site sits in the middle of that. It's here for privacy and for plain format conversion. It is not here to help anyone pass off someone else's work or dodge a disclosure they're genuinely required to make, and our Acceptable Use Policy spells out where we draw that line.

How the tool works

When you pick an image, your browser reads it, paints the pixels onto a <canvas>, and re-encodes that as a JPG. Because the new file is built from raw pixels instead of copied from the original, the embedded containers (the C2PA manifest, EXIF, and the rest) simply don't come along. The picture never leaves your device. There's no server in the loop at all.

What we don't claim

• This isn't a magic "C2PA bypass," and we'd be lying if we sold it as one. It re-encodes an image. That's the whole trick.
• The C2PA Checker is a quick scanner, not a real validator. When you need a definitive answer, the official Content Credentials Verify tool is the one that counts.
• Re-encoding only ever removes. It can't put back metadata that's already gone, so keep an untouched original if provenance might matter to you later.

Contact

Found a bug, or something here that's just wrong? Corrections are genuinely welcome through the contact page.