ProvenanceGuard
← Go back

← All guides

A Provenance Workflow for Small Teams Publishing AI Images Daily

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

The short answer

Keep it to four agreements: one named owner for sealing, sealing at export as a non-optional step, exhibit IDs recorded in one shared sheet beside the asset links, and published copies checked through the registry when a post matters. Add paid depth, survival checks, evidence packs and bulk verification, when the team's volume or clientele makes the questions arrive faster than the free routine answers them.

Seal an image free → Recover a reposted image Pricing

Small teams do not fail at provenance because the tooling is hard; they fail because everyone assumed someone else sealed it.

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 team provenance workflow? the agreed routine by which a team inspects, seals, labels, records and verifies its AI images, with named ownership, one home for exhibit IDs, and checks placed at export and at publication.

Why small-team workflow matters

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.

Checking a copy is the mirror image of sealing one. On an asset's verification page, uploading a candidate copy runs the same byte inspection on it and compares it against the record: its SHA-256 against the original and sealed hashes, whether a ProvenanceGuard assertion is present and its signature valid, and the perceptual distance between the copy and the registered fingerprint, with a match at a Hamming distance of ten or under on the average hash, or an exact hash match. The result states which of those held and which did not, separately, instead of collapsing them into one vague verdict.

How the record is built

For libraries rather than single files, bulk verification is a paid API feature: submit up to a hundred SHA-256 hashes in one call and get back, per hash, whether it is registered, its exhibit ID, its public verification URL and its registration time. That shape suits the questions teams actually ask at scale: whether everything in a delivered campaign folder was sealed, whether a partner's asset library overlaps the registry, or whether a month of published images all carry records. Single lookups stay free and public through the verification page and the single-hash API.

The registry is the part that survives distribution. At sealing, the asset's SHA-256, its sealed copy's SHA-256, and its perceptual fingerprints are stored against a public exhibit ID. Anyone with that ID, or with the file's hash, can open the public verification page or query the verification API and confirm that this exact file, or a near copy of it, was registered, when, and with what declared creator and disclosure. Verification pages are public by design: a record only a vendor can check would not settle disputes.

Where it meets the real world

Two kinds of fingerprint do two kinds of work. The SHA-256 is exact: change one byte and it changes completely, which makes it perfect for proving a copy is bit-for-bit the registered file and useless for recognising a resized repost. The perceptual fingerprints, computed from the pixels rather than the bytes, are approximate on purpose: they stay close when a copy is resized, re-encoded or lightly edited, and drift as edits accumulate. A good registry stores both and is honest about which kind of match it is reporting.

The registry model also disciplines what a match means. A fingerprint match says this image is the registered image or a close descendant of it; it does not say the person showing it to you owns it, and it does not say the disclosure attached to it was correct. Those judgements stay human. What the registry removes is the argument about identity and timing: which file, registered when, carrying which declaration. Most real disputes shrink considerably once those three facts stop being contestable.

Putting it into practice

Provenance is the record of where a piece of content came from and what has happened to it since: who or what created it, when it was registered, and which copies descend from the original. For an AI-generated image that record matters because the file itself is easy to copy, rename, crop and re-upload, and none of those actions leaves a reliable trace inside a filename. A provenance record kept outside the file, in a registry keyed to the file's fingerprints, survives exactly the handling that erases the signals embedded in the file.

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. Name one owner and one backup, in writing
  2. Put the exhibit sheet where the team already keeps links
  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 four-person studio publishing daily AI content

The studio's sheet reached 300 exhibit rows in a quarter with one owner and a backup; a client's spot audit sampled 15 rows, all resolved, and the routine's total cost stayed under one hour a week.

Notice what made the difference: not a better argument, but a record created before it was needed, carrying dates and hashes a stranger could check. That is the whole pattern this guide recommends, applied at the scale of one team and one deadline.

FAQ

When does a small team need Team over Pro?

By the product's shape, Team at $79 extends the Pro depth at $29 for teams working at greater scale, with the same features' team licensing. Choose by how many people seal and how regulated the clients are, and let the pricing page's plan details arbitrate.

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 →