Content credentials

C2PA metadata checker

Check files for C2PA provenance metadata, content credentials, and manifest presence in the browser.

Signal reportWatermark, provenance, and text-risk signals stay separate.
Post-Check loadingDetector assets load only after a user starts analysis.
No proof claimsUnknown and unsupported states are first-class results.

Run a signal check

No detector model loads until you press Check.

No file selected

Current support

C2PA browser checks are the strongest first MVP signal for supported files when metadata is present.

Supported now

What this checks

  • C2PA checks can run locally after the user presses Check.
  • No manifest is reported as not found, not as human-authored.
  • Supported formats and manifest details should be surfaced in the result.

What this does not prove

  • Many files do not contain C2PA manifests.
  • Metadata may be removed by screenshots, exports, or platforms.
  • A valid manifest describes provenance, not necessarily content quality.

FAQ

  • Can this prove whether content was written by AI?

    No. AI Detect reports signals such as provenance metadata, watermark support status, and statistical text risk. It does not claim legal or authorship proof.

  • Does text leave my browser during a local check?

    Browser-default checks run local text features and provenance checks after you press Check. Server enhanced checks are separate and will be labelled before use.

  • Why can a result be unknown?

    Many providers do not expose public watermark detectors, and metadata can be absent or stripped. Unknown is a valid result when no reliable public signal exists.

Workflow upgrade

Need repeatable reviews?

Move from one-off checks to saved reports, batch review, and API-ready signal records when the workflow needs it.

Related checks