What is actually being asked for when a client raises this?

Usually an account of where an asset came from that survives being questioned later. That can be a record on the file, a licence, an audit trail on your side, or all three. Establishing which is meant is worth doing early, because the three have different costs and only one of them travels with the image.

Does the absence of a record mean something?

Almost nothing, and reading it as evidence is the common error. Most material in circulation has never carried one, and ordinary handling removes it from material that did. A missing record is uninformative in both directions, which limits how much any check on it can conclude.

Is there a text equivalent?

Citation, approximately, and the difference matters. References attach to a claim rather than travelling with a file, so a requirement written for images does not transfer cleanly to documents. Where both are in scope it is usually clearer to state them separately than to write one rule covering media.

Glossary

Content provenance

Content provenance is a record attached to a file describing how it was made and changed, so its history can be inspected rather than guessed at from the content itself.

In plain terms

A history attached to the file. Made here, with this, edited there. It rides along with the image or document rather than being visible in it, so anybody with the right software can look up where the thing came from instead of judging by eye. It works when the file is passed along intact and stops working the moment something strips it.

Why it matters

Because the question is being asked commercially before it is being asked legally. Agencies field it from clients, review processes ask where an asset came from, and the answer needs to be more than a recollection. One generator in this guide is positioned on exactly that basis: licensed training material, indemnification, and provenance a legal team can trace, sold together as a compliance answer.

How it works

The record is metadata rather than anything visible in the content. That is its strength and its weakness in the same property: it can carry detail no mark could, and it is separable from the file in a way a mark is not. Nothing about the picture changes when the history is attached, and nothing about the picture changes when it is removed.

It survives handling that preserves the file and not handling that remakes it. Passing an asset between professional tools tends to carry the record along. Screenshotting it, re-encoding it for a social platform, or pasting it into a document that rebuilds the image will usually not, and none of those is unusual behaviour by anyone involved.

Adjacent to it is the consent record, which answers a different question about the same asset. An avatar video platform in this guide builds consent into the process of creating a likeness, which establishes that a person agreed rather than how the file was made. Buyers frequently want both and ask for them under one heading.

For text the equivalent is citation rather than embedded metadata, and the distinction matters when a requirement is written loosely. Tools that answer from sources attach references to the claim, which is where a document's material came from, but that is a property of the answer rather than a record travelling with a file. A requirement written for images rarely transfers cleanly.

What the record can and cannot settle

The asymmetry between these columns explains why the subject is more useful to a production team than to anybody trying to assess material arriving from outside. Within a workflow you control, where assets move between professional tools and the steps are known, the record is genuinely informative: it survives, it carries detail, and it answers the questions a client or a reviewer actually asks. Outside that, almost every ordinary thing a person does to an image removes it, so the absence of a record carries no signal and the presence of one only tells you about the last piece of software that respected it. The practical consequence is that provenance is worth building into how your own material is produced and handled, and is worth very little as a test applied to material you did not make.

Seen in the wild

A generator positioned on licensed training material, available indemnification and provenance a legal team can trace, sold together as the compliance answer.
Adobe Firefly
An avatar platform building consent into the creation of a likeness, which records that a person agreed rather than how the file was produced.
Synthesia
Grounded briefings handed on as raw material with citations attached, which is the text equivalent and behaves quite differently.
NotebookLM

Common misconceptions

People assume

It proves an image is genuine.

In fact

It records what the attaching software asserted about how the file was made. That is useful and it is a claim rather than a proof, and the absence of a record proves nothing at all, since most files in circulation have never carried one.

People assume

Once attached it stays attached.

In fact

It survives some journeys and not others. Ordinary steps such as taking a screenshot or letting a platform re-encode an upload will commonly drop it, so a workflow relying on it needs to know which of its own steps preserve the record and which quietly discard it.

Telling them apart

Content provenance vs Watermarking

Content provenance

A record attached to the file, carrying detail, easily stripped.

Watermarking

A mark in the content itself, carrying little, harder to remove.

One is separable and informative; the other is durable and thin. They are complements, and a requirement naming only one usually meant both.

Questions

What is actually being asked for when a client raises this?: Usually an account of where an asset came from that survives being questioned later. That can be a record on the file, a licence, an audit trail on your side, or all three. Establishing which is meant is worth doing early, because the three have different costs and only one of them travels with the image.
Does the absence of a record mean something?: Almost nothing, and reading it as evidence is the common error. Most material in circulation has never carried one, and ordinary handling removes it from material that did. A missing record is uninformative in both directions, which limits how much any check on it can conclude.
Is there a text equivalent?: Citation, approximately, and the difference matters. References attach to a claim rather than travelling with a file, so a requirement written for images does not transfer cleanly to documents. Where both are in scope it is usually clearer to state them separately than to write one rule covering media.

Key takeaways

Metadata attached to the file, not a mark in the content.
Survives professional handling; screenshots and re-encoding commonly strip it.
It records a claim about how a file was made, and never proves authenticity.
An absent record is uninformative, because most files never had one.
The consent record answers a different question and is often asked for together.

Tools that use this

Adobe Firefly
Licensed training, indemnification and traceable provenance sold together.
Synthesia
Consent recorded as part of creating a likeness.
NotebookLM
Citations attached to grounded briefings, the text equivalent.