Runs in your browser
Is this image AI generated?
Sometimes the file itself can tell you. Drop one in and this reads the Content Credential inside it: whether the file declares AI generation or camera capture, and whether that declaration's signature still matches the bytes. Most images carry no credential at all, and for those the honest answer is that there is no way to tell. That is not the same as a no.
Three steps
How to use this checker
Drop an image in, or click to choose one.
It is read in your browser. Nothing uploads.
You get a verdict: AI generation declared, camera capture declared, or not known.
How this actually works
This page has no server route to send your file to. There is no upload endpoint in this app, and no analytics call fires when you check a file. The only network request this page makes is for its own validator, a WebAssembly binary at /c2pa/c2pa.wasm, which is the same file for every visitor and has nothing to do with whatever you check.
Once that file is loaded, everything happens locally: reading your file's bytes, scanning for a Content Credential, verifying its cryptographic signature, and reading EXIF or XMP metadata all run in your browser, in WebAssembly and JavaScript, on your machine. Your file is never turned into a request body.
Do not take that on faith. Open your browser's developer tools, go to the Network tab, and drop a file into the checker below. You will see the page's own assets load once, and nothing else happen when the check runs. There is no server on the other end for your file to reach, so there was never a policy decision to make about storing it.
What this tool cannot tell you
- Whether an image is AI generated. A Content Credential can record a declaration of AI involvement, but that declaration is written by whoever signed the file. An unsigned or undeclared image may still be AI generated, and a declared one is only as honest as its signer.
- Whether a photo is truthful. A valid, trusted signature confirms the file's bytes match what was signed and something about who signed it. It says nothing about whether the scene in front of the camera, or the prompt behind the model, depicted something real.
- Who really made a file. The signer field is the certificate's own claim about its holder, not an identity this tool independently confirms. Even a trusted certificate chain establishes that a specific, recognised party made the signature, not that the name attached to it is the true author of the content.