ChronoVerify

ChronoVerify joins the Content Authenticity Initiative

A note from ChronoVerify, built and maintained by a veteran intelligence analyst.

ChronoVerify is now a member of the Content Authenticity Initiative (CAI), the community advancing content provenance and the C2PA Content Credentials standard. We build directly on that standard: ChronoVerify validates Content Credentials against the official C2PA and CAI trust lists and issues a signed, timestamped, reproducible audit record. Joining the CAI puts us, formally, in the ecosystem whose work our product depends on.

Member of the Content Authenticity Initiative

ChronoVerify is a member of the Content Authenticity Initiative. The CAI is the Adobe-founded community behind C2PA Content Credentials and open content provenance.

What the Content Authenticity Initiative is

The Content Authenticity Initiative was announced by Adobe in 2019, in partnership with Twitter and the New York Times. It is now a cross-industry community of creators, technologists, journalists, and organizations working on a shared, open approach to media transparency: a way to record and check where a piece of content came from and how it was changed. The technical foundation is C2PA, the standard that defines Content Credentials, the tamper-evident, cryptographically signed record that travels with a file. The CAI promotes adoption of that standard; the C2PA defines it.

What membership means for ChronoVerify

Membership formalizes something that was already true: ChronoVerify is built on open content provenance. In practical terms it gives us a public listing in the CAI member community, access to implementer resources and the people maintaining the standard, and the ability to keep our validation current as the trust lists and specification evolve. It also means a buyer evaluating us can see that we are a participant in the standard our product reads, rather than a tool bolted on from the outside.

What membership does not mean

Why this matters for the people who rely on provenance

The shift underway is from arguing about a detection score to confirming a signature. As more cameras and tools sign their output, and as the EU AI Act's Article 50 transparency duties take effect on August 2, 2026, reading and validating Content Credentials becomes a routine step rather than a special case. Being a member of the initiative driving that shift means our validation is built on, and keeps pace with, the same open standard our customers are standardizing on. The defensible part of what we offer is unchanged and concrete: cryptographic C2PA validation against the official trust lists, a graceful fallback to EXIF and XMP when an image is unsigned, one deterministic verdict, and a signed, timestamped audit record anyone can verify with our published key.

See cryptographic Content Credentials validation on a real image, signed or not.

Try the free verifier

Common questions

Does CAI membership mean ChronoVerify is C2PA conformant?

CAI membership on its own is participation in a community advancing content provenance, and it is separate from conformance. The conformance claim we do make is on the C2PA Conforming Products List: ChronoVerify is a C2PA Conformant Validator, record 019f8a20-6452-7a43-b11b-59d0b0e4a84a, covering validation of JPEG, PNG, WebP and AVIF under specification 2.2. There is still no Article 50 certification for any product, and we do not claim one.

What is the difference between the CAI and C2PA?

The C2PA is the standards body that defines the technical specification for Content Credentials. The Content Authenticity Initiative is the community, founded by Adobe in 2019, that promotes adoption of that provenance standard. ChronoVerify implements and validates the C2PA standard and is a member of the CAI community.

Is ChronoVerify C2PA conformant?

Yes. ChronoVerify is a C2PA Conformant Validator on the C2PA Conforming Products List, record 019f8a20-6452-7a43-b11b-59d0b0e4a84a, covering validation of JPEG, PNG, WebP and AVIF under C2PA specification 2.2. The list is public, so you can check the record yourself. It covers validation rather than generation: ChronoVerify reads and validates Content Credentials, it does not sign them.

Sources and further reading: Content Authenticity Initiative; Coalition for Content Provenance and Authenticity (C2PA); C2PA Specifications; EU AI Act Article 50.