C2PA Content Credentials
Reads embedded content credentials and manifest data.
- Upload an image to start automatic analysis.
Free AI image detector
Upload a photo to check if it was AI-generated, then review trusted C2PA provenance, a pixel-based AI probability, deepfake signals, and metadata.
Analysis starts automatically after upload. The browser reads C2PA first; only images without verified AI provenance send a resized, metadata-free WebP copy to Hive.
Preparing a privacy-reduced analysis copy…
AI likelihood and all signal details appear when analysis is complete.
Upload an image to calculate a probability
Deepfake is a separate face-manipulation signal; it does not by itself mean the whole image is AI-generated.
Results are an aggregation of signals, not a legal or factual final verdict. Compression, screenshots, reposting, and edits can remove watermarks or metadata.
Reads embedded content credentials and manifest data.
Confirms AI provenance only when a valid credential explicitly declares generative AI use.
Uses Hive pixel analysis to estimate the probability that the image is AI-generated.
Separately checks for face-swap or deepfake signals.
Records format, size, dimensions, and cache hash evidence.
The workflow starts with the strongest deterministic signals before using heavier model-based checks. It is designed for reviewers who need a fast first pass, not a final legal ruling.
Last updated: July 20, 2026
The browser reads embedded Content Credentials before upload. A valid credential can identify the signer, claim generator, edit history, and whether an AI tool was declared in the media record.
After local provenance review, Hive analyzes a resized, metadata-free copy and returns an AI-generation probability. This is a model estimate, not a watermark or factual proof.
A separate score checks face-swap or deepfake risk. It does not mean the entire image was generated by AI, so the interface never merges it into the general AI probability.
AI image detection is most reliable when the tool separates cryptographic provenance, pixel-model estimates, deepfake risk, and ordinary metadata. This page uses that hierarchy so a missing signal does not get mistaken for proof that an image is human-made.
A valid C2PA credential that explicitly declares generative AI is the strongest result because it provides signed provenance rather than a visual guess.
A Hive AI probability of 90% or higher is reported as likely AI-generated, but remains a probabilistic model result rather than verified provenance.
Scores between 30% and 90% remain inconclusive. The tool exposes the score instead of forcing a binary answer from ambiguous evidence.
A score of 30% or lower means the current model found no strong AI signal. It does not prove the image is authentic, human-made, or unedited.
Use the detector for a fast first pass, then follow a repeatable verification workflow or compare tools for higher-risk reviews.
The tool reports every channel separately because different AI image generators leave different traces. Provenance, a pixel-based probability, and face manipulation evidence answer different questions.
Checks for signed provenance data embedded in the file. When present, it can describe origin, edits, ingredients, and claim generator information.
Requires a Trusted or Valid C2PA manifest plus an explicit generative-AI assertion before confirming AI provenance. A provider name alone is not enough.
Hive evaluates visual patterns and returns a probability from 0% to 100%. The likely-AI threshold is deliberately conservative at 90%.
Checks for face swaps or AI-manipulated faces separately. A high deepfake score does not prove that the rest of the image is synthetic.
When available, the model surfaces up to three likely generator families. These are supporting scores, not attribution proof.
Records file type, size, and dimensions. A private hash supports cache lookup but is not exposed in the public response.
AI image detection is a signal aggregation problem. Screenshots, cropped images, social media recompression, format conversion, and manual retouching can remove metadata or weaken invisible watermarks.
Model-based detectors also have false positives and false negatives. A polished illustration, 3D render, stock photo, or heavily edited camera image can resemble generated media even when it is not.
Use high-confidence signals to support review decisions, and keep inconclusive results in a human review workflow when the image has legal, brand safety, editorial, or moderation consequences.
Browser-side C2PA detection runs against the original before server analysis. Only after the user chooses full analysis is a resized, metadata-free WebP copy sent to the site API and Hive.
The upload limit is intentionally set to 10 MB even though Cloudflare plan limits can be higher. This keeps memory usage predictable and reduces risk when the Worker has to inspect binary image data.
The API uses a private SHA-256 digest for 30-day cache lookup. Repeated checks reuse the result without another paid model call, and the digest is not returned publicly.
If your review is specifically about AI watermark evidence, these focused pages separate Google SynthID, C2PA, and general watermark intent from broader AI image detection.
These references explain the standards and platform constraints behind the detector design.
Official overview of the provenance standard used for Content Credentials.
Explains how provenance travels with media and why credentials can be lost.
Official description of invisible watermarking for generated media.
Platform limits that inform upload size, memory, and backend processing choices.
Practical limits and privacy details for image verification.
No detector can prove that in every case. This tool separates validated provenance, a pixel-based AI probability, deepfake signals, and metadata so reviewers can make a better decision with context.
C2PA Content Credentials are signed provenance records embedded in media files. When present, they can show the tool, signer, and process used to create or edit an image.
Screenshots, compression, social platform reposting, and manual editing can strip metadata or damage invisible watermarks. Some generators also do not publish detectable provenance.
The browser reads C2PA from the original locally first. Full analysis sends a resized, metadata-free WebP copy to the site API and Hive for pixel analysis.