Let’s Seal

Prove photos and video are real — Content Credentials

Photographs, video, and creative work sealed with C2PA Content Credentials and anchored on Bitcoin — provenance that stands up against deepfakes and doctored images. This is real, this is who made it, this is unedited since capture.

For photographers, newsrooms, publishers, artists, and film teams.

Open the app Developer docs
What a seal proves

Four guarantees, in media, journalism & creative

Real, not a deepfake

The image or video carries a signed manifest over its exact pixels. Re-render it, splice it, or synthesise it and the credential no longer matches.

Attributed to the maker

Every asset names the photographer, newsroom, or studio that sealed it, chaining to a published root — provenance you can point to.

Captured at a fixed time

A Bitcoin timestamp pins when the asset existed — decisive for breaking news, first-publication, and licensing disputes.

Readable in any C2PA tool

The Content Credentials verify in the standard ecosystem — Adobe's verifier, c2patool, any C2PA-aware viewer — not just on Let's Seal.

How it works

From your file to a proof anyone can check

The same pipeline every time — the seal and the timestamp travel with the file, so the proof is self-contained.

Your file
Your image or video
Seal
Signed over every byte · C2PA
Anchor
Bitcoin timestamp + public transparency log
Proof page
A permanent /d/… link travels with the file
Anyone verifies
Free, public, offline-capable — for anyone
The proof travels inside the file. Verification stands on the published root, the transparency log, and the Bitcoin ledger — so a court, a bank, or a counterparty can check it independently, forever.
Step by step · the web app

Seal it in the app — no setup

  1. 1

    Sign in as your studio or newsroom

    Open app.letsseal.org and sign in. Your organisation gets its own certificate authority for signing media.

  2. 2

    Upload the image or video

    Drop in the file. Let's Seal embeds a C2PA Content Credentials manifest, signed with your certificate over the media's exact contents.

  3. 3

    Anchored and logged automatically

    The fingerprint is timestamped on Bitcoin and recorded in the public transparency log. You get back the same file with credentials embedded.

  4. 4

    Publish with provenance attached

    The credential travels inside the file. Anyone can open it in a C2PA viewer or at the proof link to confirm it's real, unedited, and yours.

Step by step · the CLI

Automate it from your terminal or CI

The sealbot CLI does the same thing, scriptably — one command per file, straight into your pipeline.

# Seal a photo with C2PA Content Credentials
$ sealbot seal frontline-2026-06-30.jpg --org examples
sealed   frontline-2026-06-30.jpg  (C2PA Content Credentials embedded)
  proof  https://letsseal.org/d/8f4c21…a70d
  anchored to Bitcoin · recorded in the transparency log

# Anyone confirms the provenance — stock C2PA tooling
$ c2patool frontline-2026-06-30.jpg
  validated · signed by Let's Seal Examples · manifest intact

$ sealbot verify frontline-2026-06-30.jpg
✓ authentic · unedited · sealed by Let's Seal Examples

Images and video are sealed as C2PA Content Credentials — the same standard Adobe, camera makers, and newsrooms are adopting. It verifies in any C2PA viewer, chained to your own published root.

Full CLI & API reference
See it in action

What a proof looks like, and what you can seal

Issuer verified — controls letsseal.org
Authentic & unaltered
Asset
A photo with Content Credentials
Issuer
Let’s Seal Examplesletsseal.org
SHA-256
64-hex fingerprint ✓

Anchored on Bitcoin

Recorded in the public transparency log

Public and free to verify — by anyone, with standard tools.
Open the live proof

A single use case, many documents. Each of these is sealed the same way:

  • A photo with Content Credentials

    Live proof

    Open the proof page the way a picture editor would: it shows the image is authentic, unedited since capture, signed by the named maker, and timestamped on Bitcoin — the provenance a deepfake can't fake.

  • Video and audio footage

    Seal raw footage on capture so a broadcaster or fact-checker can confirm it's the untouched original — the same C2PA manifest, verifiable in standard tooling.

  • A press or agency image

    Wire photos sealed at source, so a newsroom downstream can prove a picture is the photographer's genuine, unedited frame before it runs.

  • Brand assets and creative sign-offs

    Master files and approved creative sealed and dated, so a client or agency can confirm the asset they received is the version that was signed off.

Live proofs are real documents sealed under the “Let’s Seal Examples” organisation.

Common documents

What you’ll seal

  • Photos & video
  • Published articles
  • Master files
  • Brand assets
  • Creative sign-offs
  • Press images
Questions

Straight answers

Is this the same C2PA / Content Credentials as Adobe's?
Yes. Let's Seal embeds a standard C2PA manifest that verifies in the whole Content Credentials ecosystem — Adobe's verifier, c2patool, any C2PA-aware viewer — chained to your own published root.
Does editing break the credential?
Any change to the pixels breaks the match — that's the point. Re-export, splice, or AI-regenerate the image and it no longer verifies as the sealed original, which is exactly how you catch a doctored or synthetic version.
Video and audio too?
Yes — C2PA covers images, video, and audio. The signed manifest travels inside the file and verifies with the same standard tooling.
What does the timestamp add?
It pins when the asset existed on a public ledger — independent evidence of first capture or publication, which settles who had the shot first in a licensing or breaking-news dispute.

Start sealing media, journalism & creative documents

Free and open. Seal in the app, automate from the CLI, and hand anyone a proof they can verify themselves.

Open the app All use cases