Skip to content
MediaPure

How to Remove C2PA Content Credentials from an Image

C2PA Content Credentials are signed provenance information that can describe an image's origin or editing history. This guide explains what the credentials do, why removing them has trade-offs and how to make a clean copy while preserving your original.

What C2PA Content Credentials are

C2PA is an open technical standard for attaching verifiable provenance information to media. A Content Credential can record claims about where an asset came from, what tools handled it or how it was edited. The credential is cryptographically signed, so compatible software can check whether the recorded manifest has been altered.

Credentials are not the same as a visible watermark, and not every image has one. They may be embedded in the file or represented through a linked manifest, depending on the workflow. Other metadata such as prompts, author fields and camera data is separate, even when a creator or platform places several types of information in one file.

Consider the trade-offs before removing a credential

A credential can help viewers understand an asset's provenance and may be expected by a client, publisher or platform. Removing it can break the associated verification chain or discard useful evidence about the source and editing history. If authenticity, attribution or auditability matters, retain the credentialed original and check the applicable requirements before making another copy.

There are also privacy reasons to limit what travels with a file, and a credential may disclose a tool or process. The right choice depends on your purpose and obligations. Do not present a file as having a verified history after removing or invalidating its provenance, and do not use metadata removal to evade a platform's AI disclosure rules.

Know what metadata removal changes

A cleaner can remove an embedded C2PA manifest and other readable metadata without changing image pixels. It does not remove a visible label added to the picture itself, an invisible watermark encoded into pixels, or a separate record maintained by a platform. It also cannot guarantee that viewers or detection systems will not infer how an image was made.

Removing an embedded credential affects the information available for provenance verification. Some workflows may restore or reattach credentials when a file is exported later. For these reasons, preserve the untouched source and identify the cleaned output accurately; treat it as a separate version rather than a replacement for the original.

Make a separate copy before cleaning

Start by locating the original and checking whether it contains a Content Credential. If the file is important for an audit, client handoff or creative record, archive it securely before proceeding. Create a duplicate to use for sharing, and confirm that you are authorized to modify the copy and that removal does not conflict with a contract or publishing policy.

A broader metadata report can also show whether the image contains EXIF, GPS, XMP, IPTC, prompts or creator fields in addition to C2PA. Review these findings before removing anything. You may decide to retain some information, such as copyright attribution, while removing coordinates or unrelated personal details.

Remove embedded C2PA information from the copy

For a supported JPG, PNG or WebP file, open a metadata remover, select the duplicate and review the scan. Confirm that Content Credentials or C2PA is listed, then download the cleaned result. A lossless workflow removes metadata blocks while preserving the encoded image data and should verify the image before making it available.

MediaPure is an online service, so the chosen copy is uploaded for processing. Read its privacy and retention information before sending confidential or contract-restricted material. For offline requirements, choose a trusted local utility whose documentation explicitly covers C2PA for your file type, and verify its output with compatible software.

Verify both image integrity and credential status

Open the output and check that it displays correctly, retains the expected dimensions and has no unexpected visual changes. Use a metadata reader to check whether the embedded manifest remains. A normal photo viewer may not expose credentials, so use a compatible Content Credentials inspector when verification matters.

Keep the credentialed original and the cleaned copy clearly named. Document which copy has provenance data and which one does not, especially in a team workflow. If credentials reappear after another export, inspect the new export rather than assuming the earlier cleanup carried through every stage.

Handle AI labels and disclosure responsibly

Removing file metadata is not the same as changing what an image depicts, and it does not establish that an image is camera-made. An AI-generated image can still contain visible characteristics, embedded watermarks or records held by the service that created it. A missing credential should never be described as proof of an image's origin.

Follow the policies of the site where you publish and the terms agreed with clients or collaborators. Some rules require disclosure independent of file metadata. If transparency is important to your audience, preserve the credential or add a clear explanation through an appropriate channel rather than relying on the presence or absence of one file field.

Choose a workflow that fits your purpose

For ordinary privacy cleanup, make a copy, scan all fields and remove only what you do not need to share. For evidence, journalism, regulated work or provenance-sensitive creative projects, preserve the original and consult the relevant policy before altering credentials. Store originals securely and record which version you publish.

The safest workflow is transparent about what changed. Check the destination requirements, avoid overwriting the only source, and verify the exported copy. Metadata removal can reduce incidental disclosure, but it cannot erase every form of attribution, watermark or history associated with an image.

Frequently asked questions

Does removing C2PA make an AI image undetectable?

No. It removes embedded credential data when supported, but does not remove visible or invisible image watermarks, external records or signals in the pixels.

Should I keep the original Content Credential?

Keep the credentialed original when provenance, attribution or auditability may matter. Clean a separate copy only when appropriate for your sharing purpose.

Does removing C2PA change image quality?

Removing metadata does not require changing pixels. Use a lossless process, retain the original and verify the cleaned output.

Ready to clean a photo?

Scan a copy for EXIF, GPS and other embedded fields with our free photo metadata remover.

Remove metadata from a photoRemove metadata from video