ChronoVerify's C2PA conformance record

The record, one command to check it against the C2PA's own register, and every validator product currently on the list. Updated July 29, 2026

ChronoVerify is a C2PA Conformant Validator, listed on the C2PA Conforming Products List under record 019f8a20-6452-7a43-b11b-59d0b0e4a84a. The Conforming Products List is the C2PA's public register of Generator Products and Validator Products that have been through its conformance program. Certification Authorities consult it before issuing C2PA claim signing certificates, which is what makes it the ecosystem's reference for who actually implements the specification.

This page exists because the register itself has no per-record pages. The list ships as one JSON file with no vendor links in it, so there is nowhere to point when someone asks you to prove a conformance claim. Below is our record, the command that checks it, and the surrounding context most people want next.

Check it yourself

Do not take a badge as evidence. The list is a plain file on GitHub, served without a login, and one command answers the question:

curl -s https://raw.githubusercontent.com/c2pa-org/conformance-public/main/conforming-products/conforming-products-list.json \
  | jq '.[] | select(.recordId=="019f8a20-6452-7a43-b11b-59d0b0e4a84a")'

Or read it by hand: the raw list and the C2PA's own conformance explorer. Search either for the record id. If the register ever stops matching what this site says, the register wins.

Where this sits on the list

All counts below are derived from the raw list on July 29, 2026. The file is re-synced several times a day, so a number here is a snapshot with a date on it, not a standing claim. Go read the source if it matters to you.

• 144 records in total.
• 124 generator products: the cameras, editors, and signing services that create Content Credentials.
• 20 validator products, from 18 distinct vendors. That is the entire reading side of the ecosystem.
• 9 validator products declare AVIF. ChronoVerify is one of them.
• 7 validator records declare US as the country in their product Distinguished Name, and 6 of those validate images. ChronoVerify is the 6th, both by conformance date and by earliest public disclosure date.

The asymmetry is the part worth sitting with. Well over a hundred products can produce a Content Credential. Twenty have been recorded as able to check one. Everything downstream of generated media, the moderation queue, the newsroom inbox, the claims file, sits on the short side of that ratio.

US-based validator products that validate images

"US-based" here means one specific, checkable thing: the record's product Distinguished Name carries C=US. Ordered by conformance date, which happens to give the same order as public disclosure date.

A seventh US validator record exists and is deliberately not in that table: Sound Patrol Unified Detection declares audio and no image types, so counting it would make "US image validators" mean something other than what it says.

Every validator product on the list

The full reading side of the C2PA ecosystem, ordered by conformance date. Rows shaded light carry C=US.

Vendors appear more than once when they list several products. Counting distinct applicants instead of records gives 18 vendors across 20 validator products.

What the listing does not mean

Conformance is a narrow, specific thing, and the value of saying so plainly is that the narrow thing is actually true.

• It is not a certification. The C2PA operates a conformance program and certifies nobody. It is also not an independent audit, a security evaluation, or an endorsement of any verdict ChronoVerify returns.
• It is not an EU AI Act certification. No such thing exists for a product. No conformity assessment body issues an Article 50 mark, so any vendor offering you one is offering you a logo.
• It covers four image types and nothing else. Not GIF, TIFF, HEIC or HEIF. Not audio, video or documents.
• It says nothing about pixel forensics. ChronoVerify reports capture-time and manipulation signals alongside a credential check. Those signals are outside the conformance scope, and they do not detect AI generation.
• A conformant read is not a clean bill of health. A correctly validated credential can state that an image came out of a generative model. Most images carry no credential at all, which is where an investigation starts rather than ends.

Sources: the C2PA Conforming Products List (raw JSON, the source every count on this page is derived from); the C2PA conformance explorer; C2PA specifications; ChronoVerify and Article 50; the method and its limits.