Hover over a Limbo image to see where it came from

Images on the web arrive without a history. A photo can be cropped, color adjusted, generated, or exported several times before it reaches a reader, and nothing on the page tells that reader who made it or what happened to it along the way.

Limbo images now carry that history with them. Wherever a verified Limbo image appears, a small Content Credentials badge sits in the corner, and hovering over it opens a card that explains the image to the reader in plain language.

What the reader sees

The card opens with a summary of twenty words or fewer that says who signed the image, when they signed it, and what was done to it. Below the summary is a clear verdict on whether the signature matches the file and whether the signer is on the trust list.

A provenance chain follows, showing every version of the image from the original to the one on screen, each with its own thumbnail, signer, tool, and recorded actions. Readers who want more detail can open the identity claims, the technical details, or the full manifest as JSON.

Verified in the browser

The check runs in the reader's browser using a WebAssembly verifier, so the file is validated against its own embedded signature without a request to a Limbo server and without an API key on the page. If a file has been altered after it was signed, the card reports that it does not verify, so the badge never claims more than the file can support.

Adding it to a site

Adding the badge to a Webflow site takes one script tag and one attribute on each image you want verified. Images that carry no credentials are left alone, so the badge only appears where there is something to verify.

To see Content Credentials on your own images, talk to the Limbo team.