No upload — runs in your browser
Drop a photo and this page reads the C2PA content credentials stored inside the file — a signed record of who made it, whether AI was declared, and every edit made since. You will see the signer, whether the signature is intact, and whether the pixels have been changed since signing. The image never leaves your device.
This page only reads the credentials attached to a file. Everything it reports describes that file alone — the same picture saved or sent again is a different file. It does not analyse the picture. No credentials does not mean AI, and credentials do not mean genuine.
Drop an image here to read its credentials
JPG, PNG, WebP, AVIF, HEIC, TIFF or RAW — one image at a time, up to 50.00 MB. Nothing is uploaded.
Loading the verification engine — about 8.6 MB the first time. Your image never leaves this device.
File SHA-256
Computed here from every byte of the file, credentials included. Every finding above describes this one file, not the picture in general: save or send the same picture again and you get a different file, a different value, and possibly no credentials at all. Compare it only against the exact same file.
AI-generated pictures are now common enough that the eye is no longer a reliable test. Some files carry content credentials — a signed record of who made the image, with what tool, and what was changed afterwards. This page reads that record and tells you what it establishes.
The limit is worth stating plainly: credentials are evidence when they are present, and silence when they are absent. A screenshot, a re-save, a messaging app or a social platform will strip them, so "no credentials found" is not the same as "made by AI". This tool gives you evidence, not a verdict.
| Before you finish | Go to |
|---|---|
| Add a visible mark of your own | Content credentials are invisible. A watermark is the mark a person can actually see. |
| Bring the file back under a limit | Re-saving to shrink a file can drop its credentials — check again afterwards if the record matters. |
Only if the file itself carries a signed record. When the creator declared AI generation inside the credentials, this page shows it plainly. With no credentials the honest answer is "unknown" — an unmarked image may be a photograph, a screenshot, or output from a model that does not sign its work. This page reports which of those it can see, and refuses to guess at the rest.
No. The credential is parsed, the signature is checked and the hash is recomputed by WebAssembly running in your own browser tab. There is no upload step and no copy of your file anywhere but your device. You can open your browser developer tools and confirm that no request carries the image.
A small signed record embedded in a file that describes its origin: which tool made it, whether AI was involved, and every edit made since. The signature is cryptographic, so any change to the record or to the pixels after signing can be detected.
Most images have none. Credentials are stripped by screenshots, re-saving, messaging apps and most social platforms, and cameras only started adding them recently. No credentials means no evidence either way.
No. An AI detector guesses from pixels and returns a probability. This page reads a signed statement and reports evidence. Those are different claims, and only one of them can be checked. A picture made by an open-source model running on their own machine carries no credentials, and this page will say exactly that — it will never call it a real photograph, and it will never call it AI either.
The signature is mathematically valid, but the certificate behind it is not on the official trust list that names manufacturers and software makers allowed to sign. That can mean a self-built test certificate, an internal tool, or a signer that has not applied for inclusion yet.
Yes, trivially — a screenshot removes them, and so does most re-saving. This is a known limit of the format rather than a flaw in this page. The one thing that cannot be faked is an intact signature: if credentials are present and verify, the claims in them were made by the signer.
JPEG, PNG, WebP and AVIF. Credentials can also live in video and PDF, but this page reads images only.
Yes — free, with no sign-up and no limit on how many images you check.
Shrink photos to an exact target size — right in your browser.
Resize images by percent, longest edge or exact box.
Open iPhone HEIC photos anywhere — convert them to JPG.
Turn WebP images into JPGs that open everywhere.
Convert JPGs to WebP for smaller, faster-loading files.
Render SVGs to crisp PNGs at exactly the size you need.
Turn AVIF images into JPGs that open everywhere.
Turn PNGs into smaller WebP files with transparency intact.
Render SVGs to JPGs at the right size, flattened onto white.
Join several images into one long picture, stacked or side by side.
Stamp your name on photos — one corner or tiled across the image.
Pick a colour, read its HEX, RGB and HSL codes.
Turn one image into a full favicon package.
Turn image sequences or video segments into an animated GIF — in your browser.
Pull the audio out of a video — MP3, WAV, WebM or M4A, right in your browser.
Mermaid flowcharts in, editable Word shapes out — not a screenshot. PDF and SVG too.