REMOVE C2PA CONTENT CREDENTIALS: UNLIMITED, NOTHING UPLOADED
Drag & drop your files, or click to browse. Everything is processed in your browser. No uploads to external servers.
Remove C2PA Metadata
Strip C2PA content credentials from JPEG, PNG, WebP, and HEIC images in your browser. Unlimited files, no signup, nothing uploaded.
#Remove C2PA Metadata
Strip C2PA content credentials from JPEG, PNG, WebP, and HEIC images in your browser. Unlimited files, no signup, nothing uploaded.
##A signed record attached to your file
C2PA (Coalition for Content Provenance and Authenticity) content credentials are a cryptographically signed manifest embedded in an image. It records what produced the file, which tool edited it, when, and whether AI was involved. Adobe markets it as Content Credentials.
⚠ The manifest travels with the file, so anyone who receives it can read your tool, timestamps, and edit history.
##It is metadata, not pixels
The manifest sits in the file's metadata container, alongside the image rather than inside it. That is what makes it removable without touching a single pixel. Your image comes out visually identical, just without the provenance record attached.
⚠ Re-saving in another app can also drop it, but that usually recompresses and costs you quality.
##Including JPEG and HEIC
C2PA binds differently in each format, which is why many tools only handle one or two. MetaStrip reads all four bindings: APP11 JUMBF segments in JPEG, the caBX chunk in PNG, the C2PA RIFF chunk in WebP, and the uuid box in HEIC, the format every iPhone shoots by default.
⚠ A tool that only supports PNG and WebP leaves your camera photos and iPhone shots untouched.
##Pixel watermarks are a separate layer
Removing the C2PA manifest removes the metadata layer. It does not remove an invisible pixel watermark such as Google's SynthID, which is woven into the image data itself. No metadata tool can, and any tool claiming otherwise is overstating what is possible.
⚠ Know which layer you are dealing with before assuming an image carries no markers at all.
##What's hidden in your files
| Category | Field | Example value |
|---|---|---|
| C2PA Manifest | c2pa.claim_generator | Adobe Firefly 3.0 |
| c2pa.action | c2pa.created | |
| c2pa.ai_generated | true | |
| instance_id | xmp:iid:9f3b2a41... | |
| Signature & Provenance | signature.issuer | Adobe Inc. |
| signature.alg | ps256 | |
| c2pa.digest | sha256:a4f2e8... | |
| claim.created | 2026-02-28T22:14:08Z | |
| XMP Provenance Block | xmp:CreatorTool | Adobe Firefly |
| Iptc4xmpExt:DigitalSourceType | trainedAlgorithmicMedia | |
| dcterms:provenance | c2pa manifest store | |
| Capture Credentials | c2pa.capture_device | Google Pixel 10 |
| exif:Make | ||
| c2pa.hash.data | signed at capture |
##Supported formats
##How to remove C2PA metadata from an image
Drop an image into the tool above. MetaStrip reads the C2PA manifest directly in your browser, shows you exactly what provenance data is embedded, and removes it when you confirm. The cleaned file downloads straight back to you. Nothing is uploaded to a server at any point, which matters when the whole reason you are stripping provenance is that you would rather not share it.
C2PA content credentials are embedded automatically by a growing list of sources: Adobe Firefly, Photoshop and Lightroom exports, OpenAI's DALL-E and Sora, Google Gemini and Imagen, and at the hardware level by cameras from Sony, Nikon and Leica, plus the Google Pixel, which signs every photo it takes. If your image came from any of those, it very likely carries a manifest whether you knew about it or not.
Because the manifest lives in the file's metadata container rather than in the pixels, removing it leaves the image visually identical. MetaStrip strips the C2PA manifest along with the EXIF, XMP and IPTC data sitting beside it, so you are not left with your camera model and GPS coordinates after clearing the provenance record.
One honest limit: removing the C2PA manifest removes the metadata-based marker. It does not remove a pixel-level watermark such as SynthID, which is embedded in the image data itself and cannot be stripped by any metadata tool. Most automated checks read the manifest, so removal is usually sufficient, but it is worth knowing the difference.