There is now a page at /tools/verify-image that reads how an image is marked and tells you what it found. It needs no account, and it works on anybody's file — yours, a supplier's, a competitor's.
The file is read in your browser. It is not sent to Qamera or to anyone else; there is no upload and no server that receives it. That is a property of how the page is built rather than a promise about how we behave.
The result answers two questions separately, and both every time. Whether the binding is intact — the signature verifies and the content still matches what was signed. And whether the issuer is recognised — whether the certificate behind that signature appears on the public C2PA trust list. A file can have one without the other, so a single tick would be a false statement about it.
Our own exports are exactly that case. They carry a sound signature, and our certificate is not on the public list, so a public verifier shows their credential as Unrecognized. The page says so itself, in the result, rather than letting you discover it somewhere else.
A file with no marking at all is a normal answer, not an error. It is also the most common one, and it does not mean the image was not generated by AI. Marketplaces, messaging apps and social platforms strip metadata as a matter of course — the same image can arrive at a marketplace marked and leave it bare, pixel for pixel unchanged.
The page reads JPEG, PNG, WebP and AVIF. For video it explains what can and cannot be established today and points to external checkers. It does not claim to detect invisible watermarks such as SynthID, because it cannot; it tells you where to check instead.