How to check a Puzzitive picture
Every picture Puzzitive makes is generated by AI, and every file we produce carries that fact inside it. Here is how to read it for yourself.
What we put in the file
Two pieces of information, both in the file's metadata. The pixels are left alone - we add no visible watermark. The first is a standard metadata field marking the picture as made by a generative model, which any metadata viewer can read. The second is a Content Credentials signature: a cryptographic signature carrying a time stamp from an independent authority, recording both that the picture was made by AI and that the file has not been altered since.
The model provider's own signature
The model that draws the picture signs its own original, and we keep that signature untouched. On the full-size copy we make from it, the original signature is nested inside ours, so a verifier shows the whole chain: created by AI at our provider, then resized by Puzzitive.
Checking a picture
Anyone can do this, with no account and nothing to install.
- Get the picture as a file - download it from the app or from a link we gave you. A screenshot will not work.
- Open verify.contentauthenticity.org.
- Drag the file onto the page, or pick it from your device.
- The page shows who signed the picture, when, and what it was made with.
The service accepts most common image formats, WebP, JPEG, PNG and TIFF among them. It reads Content Credentials only; a metadata viewer such as ExifTool shows the first mark as well.
Two things that look alarming and are not
- “Unrecognised” beside the publisher. It means our certificate is not on the verification service's list of known issuers. Ours is self-signed, and so is our provider's. It says nothing about the signature itself, which is intact, covers an unaltered file, and carries a date confirmed by an independent authority.
- Nothing to show at all. If the file has been through a social network, a messenger or a screenshot, the marking is already gone - the next section explains why.
Why the marking sometimes disappears
Both marks live in the file's metadata, and almost everything that re-encodes an image discards metadata. Social networks and messengers do it when you post or send a photo, and a screenshot never carries any to begin with. We cannot prevent that, and once it has happened we cannot restore it. Some platforms do read the marking as you upload and label the post themselves, even though the file they pass on no longer carries it.
Sharing a picture so the marking survives
Send the file as a file rather than as a photo: as a document or an attachment, by email, by AirDrop, or as a direct download from the app. That is also how to give a picture to somebody who wants to verify it.
If something does not check out
If a picture will not verify and you believe it should, write to draw.without.borders@gmail.com and tell us where the file came from.