Skip to content
Delete Image Metadata

Remove C2PA Content Credentials

Content credentials are a signed record of how a file was made and edited. See whether your image carries one, and remove it if you choose to.

  • .jpg
  • .jpeg
  • .png
  • .webp
Free
No account, no limit on files
0
Files uploaded — processing is local
4 formats
Lossless — pixels never re-encoded
Processed in your browser
Ready

What content credentials actually contain

C2PA — the standard behind the Content Authenticity Initiative — attaches a manifest to a file describing its history. A typical manifest records which application produced the image, which actions were applied, whether generative tools were involved, and sometimes the identity of the signer. It is cryptographically signed, so tampering with it is detectable.

Physically it is a JUMBF box: an APP11 marker segment in a JPEG, or a caBX chunk in a PNG. It is metadata, stored alongside the picture, and like all metadata it can be removed.

What removal does — and what it advertises

Removing the manifest means the file no longer carries its own account of how it was made. Downstream tools that read content credentials will show nothing rather than showing a history.

It is worth understanding the design intent: C2PA is built so that *absence* is meaningful. A verifier cannot recover a removed manifest, but it can report that a file has no credentials, and in workflows that expect them, that absence is itself informative. Removing credentials is not the same as making a file look untouched.

Where the original file was published with credentials attached, that published copy still has them. Removal affects your copy only.

Legitimate reasons to remove them

There are ordinary reasons a creator strips a manifest, and they are mostly the same reasons people strip EXIF.

  • The manifest names an individual, an account, or a client that should not be published
  • It records the internal tools and edit history of commercial work
  • It records a workflow the creator considers proprietary
  • The file is being reused in a context where its editing history is irrelevant and its identifiers are not

Where this crosses a line

Removing provenance data to pass off someone else's work as your own, or to present a manipulated image as an unedited one, is a misuse of any tool that can do it — including this one. The technical capability is neutral; using it to deceive is not, and the terms of this site say so.

What this tool does

  • Detects and removes JUMBF/C2PA boxes in JPEG APP11 and PNG caBX
  • Removes XMP digital-source-type declarations alongside the manifest
  • Verifies afterwards that no credential block remains in the output

What it does not do

  • Cannot alter credentials on copies already published elsewhere
  • Cannot forge or edit a manifest — removal is all this does
  • Does not affect pixel-encoded watermarks or visual classifiers

Remove C2PA Content Credentials

Content credentials are a signed record of how a file was made and edited. See whether your image carries one, and remove it if you choose to.

Open the tool

Reviewed and updated . Behaviour described on this page is covered by the project’s automated tests.

Frequently asked questions

What are content credentials?

A signed metadata manifest, promoted by the Content Authenticity Initiative, recording how a file was created and edited. Adobe Firefly, recent Photoshop versions and several cameras attach one.

Is removing C2PA data detectable?

The removal itself is not reversible or traceable in the file, but the absence of credentials is visible to any verifier that looks for them. The standard is designed so that a missing manifest is a meaningful signal.

Does removing metadata remove content credentials?

Yes — running any image through the metadata remover on this site drops the JUMBF box along with EXIF, XMP and IPTC. This page exists to explain what that block is, not to do something different.

Which tools add content credentials?

Adobe Firefly and recent Creative Cloud applications, some Leica and Nikon camera models, and a growing number of AI services. Support changes quickly, so checking a specific file is more reliable than assuming.

Does removing credentials break the file?

No. The manifest is an optional block; removing it leaves a perfectly valid image.

Can credentials be added back later?

Only by re-signing with a valid certificate, which requires the signing tool. This tool removes, it does not sign.

Do cameras add content credentials?

Some recent Leica and Nikon models do, and the list is growing. Most cameras still do not.

Will removing them affect how platforms treat my image?

Possibly, in either direction — some services surface credentials when present. No specific outcome can be promised, because each platform decides its own behaviour.

Keep going

Related tools

Back to the main metadata remover