ProvenanceGuard
← Go back

← All guides

Provenance for Creators: Sealing an AI Portfolio Before Clients Repost It

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

The short answer

Seal each finished piece at export, while the file and its story are in front of you. Publish the labelled copy, keep the exhibit ID with the client delivery, and let the registry be the quiet part of your terms: if the work travels uncredited, recovery can match the travelling copy to a record that predates it. The free tier does this complete job on an asset.

Seal an image free → Recover a reposted image Pricing

Portfolio work is advertising that other people redistribute for you; that is the dream and the risk in the same sentence, and provenance prices the risk at five minutes per piece.

What sealing does not do is just as clearly bounded. It does not certify that a disclosure statement is legally sufficient, it does not turn the assertion into a C2PA manifest, and it does not store the uploaded original: the registry keeps the sealed and labelled copies and the record, so verification and downloads keep working, while the original bytes are not retained. The seal is evidence of a declaration made at a time, about a specific file, and that precision is what makes it useful later.

What is creator portfolio provenance? a creator's habit of sealing each finished AI work at export, registering its fingerprints, and publishing labelled copies, so later uncredited circulation can be matched back to a dated record.

The problem behind provenance for creators

Sealing is the moment a record is created. ProvenanceGuard takes the creator and disclosure the uploader declares, the SHA-256 of the original bytes, and the registration time, and signs that assertion with HMAC-SHA256 under the product signing key. The signed assertion is embedded into the file as XMP, producing the sealed copy. Because the signature covers the assertion's contents, altering the creator, the disclosure or the hash inside the file afterwards invalidates the signature, and the verification page shows that plainly.

Alongside the sealed copy, sealing produces a visibly labelled copy: the same image with a parchment custody strip in the pixels naming it as AI-generated content whose provenance is registered with ProvenanceGuard. The distinction matters. Embedded assertions are machine-readable and fragile in transport; a visible label is human-readable and survives anything that keeps the strip in frame, including a screenshot. Publishing the labelled copy where the audience actually sees the image, and keeping the sealed copy as the record, uses each layer for what it is good at.

How ProvenanceGuard handles it

The honesty of the method is in its stated limits. This is fingerprint-only soft binding: ProvenanceGuard embeds no invisible watermark, so recovery can only find images that were registered before they travelled, and only while their pixels stay within threshold of the original. Heavy cropping, collage, or aggressive filtering can push a copy beyond matching, and the lookup then says so rather than forcing a nearest guess. A tool that always found something would be manufacturing provenance, which is the opposite of the point.

Recovery exists for the copy that comes back to you with nothing attached: no metadata, a new filename, dimensions changed by two platform hops. The Recovery Registry lookup fingerprints the uploaded copy perceptually, using aHash, dHash and pHash together, and searches the registry for a record within the stated threshold: a combined distance of at most 36 differing bits out of 192 compared, or 12 out of 64 for older records that carry only the legacy average hash. A match returns the original exhibit, its creator and disclosure declarations, and its registration time.

What survives distribution, and what does not

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.

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.

A routine that survives busy weeks

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.

The practical problem is distribution. An image is rarely published once, in one place, in its original form. It is uploaded to platforms that resize and re-encode it, forwarded by partners, saved and reposted by audiences, and archived by people who strip whatever context surrounded it. Each step is normal and usually innocent, yet together they separate the image from anything that said how it was made. Planning for that separation, rather than hoping it will not happen, is the whole discipline this guide is about.

Five actions to take

  1. Seal at export, in the same session as the final render
  2. Deliver exhibit IDs to clients in writing, with the files
  3. Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it
  4. Seal the final export of the asset, with the creator and disclosure declared in your own accurate words
  5. Download and keep both copies the seal produces: the sealed copy as the record, the labelled copy for publication

A worked example: A creator whose AI poster series was reposted by a large account

The repost reached an audience 40 times hers without credit; the recovery match and its registration date were the substance of her message to the account, which added credit and linked her verification page the same day.

The lesson generalises beyond this case. Records made at publication time are cheap, calm and complete; records reconstructed under pressure are expensive, partial and contested. Everything in this guide is in service of moving work from the second category into the first.

FAQ

Does sealing a portfolio piece limit how I can sell it?

No. The registry records registration, not rights transfers; it does not publish your original file, and the original bytes are not stored. It evidences when the work was registered and what you declared, which supports, and never replaces, your contracts.

Can anyone verify a record, or only the owner?

Anyone. Verification pages are public by design, the single-hash lookup is a public API, and an exhibit ID or a file hash is enough. A record only its owner could check would not settle a dispute with a stranger.

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.

Seal an image free →