ItemlumeAssets & tasks / DECISION CHECK
Does AI image metadata survive my store’s CDN and export pipeline?
Check both the approved master and the exact image served at the feed URL. Editing, compression and CDN rendition can change metadata. Do not assume provenance survives because the picture looks identical, and do not remove required AI information to avoid a disclosure.
Map the delivery chain
Write down the creation method, editing application, exported master, uploaded asset and feed rendition. Keep the original generation record with the asset. Google’s current guidance requires appropriate IPTC DigitalSourceType information for AI-generated product images. Which value describes an image depends on how it was created; a partly edited photograph should not be randomly labeled as an entirely generated image.
A public seller question reports concerns about metadata and storefront processing. It is evidence that this question exists, not proof that every Shopify CDN removes the same fields or that the author’s rejection was correctly diagnosed. Inspect your own delivered files rather than adopting a comment as a technical finding.
Compare bytes at each stage
| Stage | Inspection record | Release decision |
|---|---|---|
| Generation master | Creation method and provenance field | Keep original evidence |
| Edited export | Actual IPTC/XMP value after saving | Repair missing or incorrect provenance |
| Store original | Downloaded file and field inspection | Check upload behavior |
| Feed rendition | Exact response and provenance value | Approve only the delivered version |
Use a metadata inspector that can read the actual IPTC/XMP field. A filename containing “AI” or a generic EXIF date is not the same evidence. Preserve the inspection output privately alongside the versioned asset; do not publish unrelated location or device metadata.
Repair the last failing stage
For an illustrative generated perfume scene, the master can be correct while a resized derivative loses its provenance. Correct the export or delivery configuration at that stage, then inspect a fresh response. Do not repeatedly add a tag to the master if the next transformation discards it. Ask the hosting provider how to preserve the necessary field on the specific supported rendition.
Keep provenance and approval separate
A truthful source-type field does not prove that the bottle label, product variant or marketing claims are accurate. Review those against the real product too. This guide is a manual delivery review; Itemlume does not certify metadata on a third-party CDN. Record an unresolved field as unresolved and consult the destination’s current guidance before submitting the asset.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Can I remove all metadata for privacy?
Review private metadata selectively while preserving required AI provenance.
Does a visible AI badge replace the required field?
Do not assume a visible label substitutes for the documented metadata attribute.
Has every Shopify CDN been confirmed to strip it?
No. The cited user report is a question, not a universal verified diagnosis.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits