ProvenanceGuard
← Go back

← All guides

Video Thumbnails and Keyframes: Sealing the Still Image Around a Video

By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read

The short answer

ProvenanceGuard works on JPEG and PNG stills, and a video's surrounding stills are exactly that. Seal the thumbnail and poster frame before upload, register keyframes you publish as stills, and the part of the video that travels as an image, into articles, embeds and screenshots galleries, carries a record. The video file itself is outside the tool's formats, and the guide does not pretend otherwise.

Seal an image free → Recover a reposted image Pricing

Ask where a video gets judged and the answer is usually a still: the thumbnail in a feed, the poster in an article, the frame in a screenshot.

Provenance works when it is a step in the publishing workflow rather than a rescue operation afterwards. The working pattern is short: inspect the final export, seal it, download the sealed and labelled copies, publish the labelled copy, and file the verification URL with the asset's record wherever the team already keeps campaign or client information. Five minutes per asset at publication is the entire cost; reconstructing a record weeks later, from an unsealed original that may no longer exist, is the expensive alternative.

What is a keyframe asset? a still image representing a video, its thumbnail, poster frame or a selected keyframe, which circulates independently as an image and can carry its own provenance record.

What goes wrong without a plan for provenance for video stills

Roles matter more than tools at team scale. One named person owns sealing for a campaign, the registry exhibit IDs are recorded next to the deliverables rather than in a personal downloads folder, and clients or partners receive the verification link as part of handover, not on request after a dispute. Paid plans exist for the depth around that routine: survival re-checks before publication, evidence packs when a jurisdiction's wording is needed, and bulk verification when the library, not the single image, is the unit of work. Pro is $29 a month and Team is $79 a month; the free tier does the complete sealing job on an asset without either.

Survival re-checks, a Pro feature, answer the question publishing actually raises: after this platform does what it does to uploads, what is left of my marking? The check runs local simulations of documented platform transforms on the sealed and labelled copies: resize to the platform's maximum width, JPEG re-encode at its quality setting, and metadata stripped. The result is reported per platform for Instagram, TikTok, YouTube thumbnails, X and LinkedIn, and every row is labelled as a simulation, because that is what it is, not an actual upload.

What the inspection, seal and registry each contribute

The pattern the simulations reveal is consistent and worth internalising. Embedded metadata, including the signed assertion and any C2PA manifest, does not survive the transforms. The visible label generally does, as long as it stays in frame and legible at the reduced size. The perceptual fingerprint still matches the registry record after the transform, within the match threshold, and the registry lookup therefore survives even when everything inside the file is gone. Distribution-proof provenance is the registry plus the label; the embedded assertion is the record of origin.

Running the check before a campaign, rather than after a takedown or a complaint, turns those findings into decisions. If the label fails at a platform's width, the artwork changes. If a format conversion in the pipeline strips everything before publication, the seal is applied after that conversion instead of before it. The simulations are cheap and repeatable, so they belong in the pre-publish routine for any asset that matters, not in the post-mortem.

The honest limits

A visible label does the communicating that metadata cannot. Most people who see an image will never open its properties, and most platforms will never show them a credentials panel. A label in the pixels, naming the content as AI-generated, is read by exactly the audience the disclosure rules exist for, on exactly the surface where they encounter it. ProvenanceGuard's labelled copy carries that strip as part of the image, so the disclosure travels with the pixels instead of depending on a caption that can be separated from them.

Labels have their own failure modes, and a serious workflow plans for them. A label placed along an edge can be cropped out; a label rendered too small becomes illegible after a platform resize; a screenshot of the centre of an image may exclude it entirely. That is why the visible label is one layer among several: the survival re-checks specifically test whether the label remains detectable after simulated platform transforms, and the registry fingerprint remains as the fallback when the label is gone.

Decisions to make before you publish

There is also a tone question. A custody strip that looks like part of the work's presentation, clearly worded and consistently used, reads as professionalism rather than apology. Teams that label every AI asset the same way, from the first post rather than after a complaint, find the label becomes part of their brand's trust signal. The creators who struggle are usually the ones who labelled inconsistently, so that an unlabelled repost looks like concealment next to their labelled originals.

No single layer does this job alone, and honest tooling says so. Embedded metadata can be stripped. A visible label can be cropped. A fingerprint can drift if an image is edited heavily. A registry entry proves registration, not authorship in a legal sense. Used together, though, the layers cover each other's failures: when the metadata is gone the fingerprint can still find the registry record, and when a copy is too altered to match, the labelled version and the evidence pack still tell the story.

Five actions to take

  1. Inventory the stills around each video and seal them as assets
  2. Label AI-generated thumbnails as you would any AI image
  3. Seal the final export of the asset, with the creator and disclosure declared in your own accurate words
  4. Download and keep both copies the seal produces: the sealed copy as the record, the labelled copy for publication
  5. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records

A worked example: A documentary channel publishing AI-assisted explainers

It sealed thumbnails and poster frames for 26 videos; a poster frame reused in a blog without context was matched through recovery, and the channel's comment, with the verification link, became the blog's correction note.

What the case really shows is timing. Every artefact used, the registry entry, the fingerprint match, the pack, existed because someone spent a few minutes at publication. The same team, equally honest, starting from memory a month later would have had a much harder week.

FAQ

Does sealing a keyframe say anything about the whole video?

Only what you declare: the record covers the still and your declaration about it. If the video itself is AI-generated, declare that in the still's disclosure wording and the video's own description; precision about scope is the record's strength.

Is ProvenanceGuard's assertion a C2PA manifest?

No. It is ProvenanceGuard's own signed assertion, embedded as XMP and HMAC-signed, and labelled that way everywhere. The inspection detects genuine C2PA markers when a file carries them, but the two records are never conflated.

What formats and sizes are supported?

JPEG and PNG, up to 25 MB per file. Those are the formats the inspection, XMP embedding and fingerprinting are built and tested against; other formats are refused rather than approximated.

What does the free tier actually do?

The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.

Seal an image free →