You built a composite by hand. You chose the photographs, cut out the subject, adjusted the light and spent hours making the pieces fit. Then the exported image showed Content Credentials, and you started wondering which part of the work triggered them.
Start with the ingredients, not just the last tool you clicked. A composite can have a recorded history that includes source images as well as your own edits. Reading those separately is much more useful than treating every credential as an AI verdict.
Why a handmade composite can carry a credential
Content Credentials are not reserved for AI-generated images. They can carry attribution and editing history for photographs and other creative work. An ordinary camera image and a generatively edited image can both have credentials, with different information inside.
Adobe's Photoshop tutorial demonstrates a composite whose credential preview includes the original photograph, a Generative Fill layer and a balloon taken from another photo. The record describes ingredients and activity, rather than reducing the whole composition to one creation method.
A social platform's AI label is a separate presentation decision. Adobe's labeling FAQ explains that platforms determine whether and how to display metadata. First establish whether you are seeing a general provenance badge or a specific claim about AI use.
Read source history and editing history separately
In a public Photoshop discussion, replies suggested several different causes, including downloaded assets and editing tools. A later reply attributed the issue to sharpening. Those competing explanations show why a comment thread is a starting point for inspection, not a diagnosis of your file.
For your own composite, make a short ingredient list: the original photo, each downloaded image and any generated elements. Keep the source files and their licensing records together. Inspecting an asset before placing it gives you a useful baseline; inspecting only the finished composite does not tell you what each input contained.
Next, review Photoshop's Content Credentials panel and its Preview view where available. Look at ingredient thumbnails and recorded activity separately. A source image appearing in the history is not, by itself, evidence that it was AI-generated. For the difference between detecting a credential and validating its signature, use our Content Credentials verification guide.
Prepare the sharing copy with FreeAIWiper
Use FreeAIWiper as your final file check. It brings inspection, supported metadata removal and output verification into one browser-local workflow.
- Keep the layered master and original assets. Export a finished JPEG or PNG for sharing. Work on that delivery copy, not your only editable archive.
- Inspect the export. Select it in FreeAIWiper and review the supported Content Credentials, generator information and other provenance it reports. Our image inspection guide explains what to look for.
- Choose the cleanup. Remove the supported AI metadata you do not want in the sharing copy. Review optional private-metadata removal separately, especially when attribution information needs to remain.
- Download the verified result. FreeAIWiper reinspects the rebuilt file before download and preserves the encoded image payload without pixel recompression. Open the downloaded copy and check the composition before selecting it for delivery.
If you replace an ingredient or export again, check the new file. A useful final check belongs to a specific export, not to every future version of the design.