Where does the label go?

Wherever suits your systems: the file name, the file's own information, the delivery sheet, or all three.

What about mixed images?

We record what was done, for example a photographed product on a generated background.

Provenance labelling for product images

What is image provenance labelling, and why do product images need it?

The short answer

Provenance labelling records how each image was made, photographed, rendered or generated, and keeps that record with the file. It lets your team know what they are publishing, answer questions about it, and meet transparency expectations as more catalogues mix real and generated images.

Why it matters now

Catalogues increasingly mix photography, 3D renders and AI images. Once they are finished to one standard, they can be hard to tell apart, even for the team that commissioned them. A label keeps the facts with the file.

How it is done

Every file we deliver is marked with its source. We agree with you where the label lives so it suits your systems: in the file name, in the file's own information, in the delivery sheet, or in all three.

What we need from you

How your team names and stores files, which systems the images pass through, and whether the label should ever be visible to customers.

Tools record, people verify

Recording the label is routine. Making sure it is right is not: an image may be photographed with a generated background, or rendered and then retouched. An editor records what was actually done.

How ALT FIX helps with this

We label every file we deliver as photographed, rendered or generated, in the place your team will look for it.

Generated and rendered

Questions

Where does the label go?: Wherever suits your systems: the file name, the file's own information, the delivery sheet, or all three.
What about mixed images?: We record what was done, for example a photographed product on a generated background.
Do customers see the label?: Only if you choose to show it.