AiMetaOff
☰
PRIVATE BY DESIGN

C2PA Remover

Remove C2PA Metadata.
Keep control of your files.

Inspect and remove supported embedded C2PA Content Credentials from eligible JPEG, static PNG and static WebP images in your browser.

Review the credential first. Select only C2PA in Cleanup scope to keep other metadata categories.

Drop your files here

JPG, PNG, WebP, AVIF, HEIC (limited), PDFMax 15 MB/file · Up to 30 files · No GIF
Files processed in browser, never uploadedNo trackingNo account

Supported variants & limits

File limits: 15 MB per file, up to 30 files, 40 megapixels per image, 200 pages per PDF, and a 20-second processing limit per operation.

Compatibility: Some complex or unsupported file variants may be rejected. Not every metadata field can be removed from every format.

HEIC (limited): Support covers eligible single-image files. Grids, sequences, depth and thumbnail items are outside this scope. Supported EXIF, XMP and C2PA containers can be removed without converting the image. Completed and unchanged copies can be included in ZIP, including unchanged HEIC copies. Changed HEIC copies have limited verification and are available as individual downloads. Preview availability depends on your browser.

Important: Removing metadata does not remove visible watermarks or guarantee that social platforms won't identify AI-generated content.

Clear all files?

This removes all files, previews and processing results from your current workspace. Files on your device and previously downloaded copies will not be affected.

  1. 1Add an image
  2. 2Review C2PA details
  3. 3Clean and check the copy

How to remove embedded C2PA metadata

Add the image and open View technical details to review the C2PA findings. In Cleanup scope, clear every category except C2PA. Select the file, click Clean selected, then use Download new copy. Your original file stays unchanged.

The cleanup checks the new copy for supported C2PA containers. Add the downloaded copy again and compare its C2PA findings with the original.

C2PA checks and removal limits

When AiMetaOff can read an embedded manifest, it reports available checks for the claim signature, assertion hashes, file binding and certificate validity separately. A detected container alone cannot establish authenticity. Signer trust remains unverified. AiMetaOff does not fetch remote manifests or check certificate revocation online.

Unsupported structures can remain or prevent cleanup. Removing the embedded manifest also removes its signed claim from the copy. If a credential remains and cleanup changes bytes covered by it, the file-binding check can fail. Remote records, watermarks and platform AI labels are outside the scope of file cleanup.

Review Content Credentials

Understand Content CredentialsInspect a fileVerify metadata removal