The Free Pre-Publish Provenance Check: Five Minutes Before You Post
By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read
The short answer
Five steps, all free: inspect the final export, seal it with accurate creator and disclosure declarations, download the sealed and labelled copies, publish the labelled copy, and file the verification URL with the post. The check runs on the export you will actually publish, not an earlier master, because transforms after sealing are exactly what the record cannot see.
Provenance has a timing property that no budget can fix later: it is nearly free before publication and partly impossible after it.
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.
What is a pre-publish check? the short routine run on the final export of an image before publication: inspect its existing signals, seal it, obtain the labelled copy, and file its verification URL, all before the asset leaves your hands.
The free pre-publish check: the plain-English version
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 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.
Reading the result properly
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.
Mistakes that quietly break the record
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.
When free is enough and when paid depth earns its place
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.
ProvenanceGuard is built around those layers, and its wording is deliberately narrow. The free job inspects one JPEG or PNG, embeds a signed ProvenanceGuard assertion in XMP, produces a visibly labelled copy, registers the SHA-256 and perceptual fingerprints, and gives the asset a public verification page. The assertion is HMAC-signed and labelled accurately everywhere as ProvenanceGuard's own assertion; it is not a C2PA manifest and is never described as one.
Five actions to take
- Attach the check to an existing habit, like writing the caption
- Seal the export, never the working file
- Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it
- Seal the final export of the asset, with the creator and disclosure declared in your own accurate words
- Download and keep both copies the seal produces: the sealed copy as the record, the labelled copy for publication
A worked example: A solo creator adding the check to a daily posting habit
After 30 days the routine took under 4 minutes per image including filing the URL; when a platform questioned one post's AI status, the answer was a link sent within the hour, and the check paid for its month in one reply.
File the pattern, not just the outcome: a dated record, a measured match, and wording that never claimed more than the record holds. Repeated across a catalogue, that pattern is what turns provenance from a feature into a reputation.
FAQ
Is the free tier limited to one asset?
The free job does the complete job on an asset: inspection, signed assertion, labelled copy, registration and public verification. The product describes free as one seal's complete workflow, with paid plans buying survival depth and evidence, not basic sealing dignity.
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.