ProvenanceGuard
← Go back

← All guides

PNG Text Chunks: A Quiet Place Provenance Signals Hide

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

The short answer

Many generators write their disclosures, software names and parameters into PNG text chunks, which makes the chunk list one of the most informative stops in an inspection of a PNG that never passed through a converter. The same chunks are silently dropped by most conversions and re-encodes, so a chunk-based disclosure is real evidence in the file at rest and no evidence at all after distribution.

Seal an image free → Recover a reposted image Pricing

Half the provenance surprises in a PNG archive are sitting in plain sight in chunks nobody thought to read.

Format details decide more provenance outcomes than policy documents do. JPEG carries XMP in application segments that re-encoding discards; PNG carries text chunks that many converters drop silently; EXIF, written by cameras, is routinely stripped by platforms and says little about AI generation in any case. ProvenanceGuard works with JPEG and PNG because their structures are where its inspection, XMP embedding and fingerprinting are defined and tested, and it inspects all three metadata territories, XMP, EXIF and PNG chunks, rather than assuming any one of them is where the truth lives.

What is PNG text chunks? named text fields inside a PNG file's chunk structure, where tools write descriptions, software credits, disclosures and generation parameters, readable on inspection and dropped by most format conversions.

Why PNG text chunks matters

Pipelines break provenance in boring places: a design tool exporting without metadata, a CDN recompressing on the fly, a social scheduler re-encoding before upload, an archive converting everything to one format. Each is a transform, and each transform is testable. The lineage tool's local transforms and the vault battery's transforms exist precisely so a team can run its own pipeline's steps against a sealed sample and watch which step removes what, instead of discovering it from a published asset that no longer verifies.

Inspection comes before sealing, because an asset may already carry signals. ProvenanceGuard reads the actual bytes of an uploaded JPEG or PNG and reports what is really there: C2PA and JUMBF markers, an XMP packet, EXIF data, PNG text chunks, any AI disclosure already present in the metadata, and any prior ProvenanceGuard assertion, including whether that assertion's signature still verifies. Nothing is inferred from the filename or the uploader's claims; every field on the inspection result is derived from the file itself.

How the record is built

That byte-level honesty changes decisions. A file that arrives with a valid C2PA manifest needs different handling from a file whose metadata was already stripped by an earlier platform hop, and both differ from a file that was never marked at all. Checking first stops a common mistake: sealing and republishing an image while assuming its original manifest is intact, when in fact the copy in hand lost it two uploads ago. The inspection result becomes the baseline the rest of the record is built on.

Inspection also has limits worth stating. A marker being present says the bytes contain it; it does not say the claims inside it are true, and a signature check says whether a ProvenanceGuard assertion was altered, not whether the disclosure text a creator typed was accurate. Provenance records what was declared and when it was registered. Treating it as more than that, in either direction, is how teams end up both over-trusting and under-using the records they have.

Where it meets the real world

Only JPEG and PNG files are supported, up to 25 MB, because those are the formats whose byte structures the inspection, embedding and fingerprinting are built and tested against. A file in another format is refused rather than guessed at. That refusal is a feature: a provenance tool that silently approximated on formats it does not understand would produce records that look solid and are not, which is worse than no record at all.

That is why a registry layer exists alongside embedded marking rather than instead of it. ProvenanceGuard detects C2PA markers during inspection and reports them truthfully, and its survival simulations show whether a C2PA manifest present in a sealed file survives a platform-style transform; in the simulated transforms it does not, while the registry fingerprint match does. The lesson is not that C2PA is useless, but that an embedded manifest alone cannot be the whole compliance plan for content that will be distributed.

Putting it into practice

C2PA is a technical specification for attaching a manifest to media: a structured, signed bundle of assertions about how the content was created and edited, typically carried in a JUMBF box inside the file. When a camera, generator or editor that implements the specification writes a manifest, and the file reaches a viewer unaltered, supporting software can read the manifest and show the content's credentials. The idea is sound and increasingly widely implemented across cameras, tools and platforms.

The weakness is transport, not design. The manifest lives inside the file, and the everyday machinery of the web rewrites files. Platforms resize and re-encode uploads, messaging apps compress them, and screenshots discard the file entirely. When the bytes are rewritten, an embedded manifest is commonly dropped, and the image that arrives at the next viewer carries no credentials even though it was properly marked at creation. Compliant at creation and non-compliant at distribution is the normal outcome, not an edge case.

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.

Five actions to take

  1. Include chunk contents in your inspection routine for PNGs
  2. Screenshot nothing; export the chunk findings into the asset record
  3. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
  4. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  5. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned

A worked example: A reviewer sampling a dataset of contributed AI images

Chunk inspection on 90 PNGs found generator disclosures in 63, nothing in 20 that had been converted and back, and unrelated text in 7; the dataset's documentation was rewritten around those measured categories.

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

Do chunks carry signed assertions?

Chunks carry what tools write into them, usually unsigned text. A signed ProvenanceGuard assertion is embedded as XMP with its namespace and signature; the two territories are inspected separately and should never be conflated.

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.

What do Pro and Team cost?

Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.

Are my uploaded originals stored?

No. The registry keeps the sealed and labelled copies derived at sealing time and the registry record, so downloads and verification keep working, while the uploaded original bytes are not retained.

Seal an image free →