Which product image belongs in a feed, gallery or ad?

Define the image role before choosing the file

Imagine a desk lamp with three approved assets: a plain product view, a room scene, and a launch image with a promotional headline. All three may accurately show the same lamp. That does not make them interchangeable. The first helps identify the item, the second illustrates context, and the third communicates a campaign message. Choosing by aesthetic preference alone can place an offer graphic into a product feed or an unhelpfully plain image into a contextual story.

Write the role beside the filename in your own worksheet. Include the exact SKU and physical edition so a promotional image from last year is not accidentally approved for a revised lamp. Keep creative approval separate from destination approval; the latter depends on where and how the image will appear.

A role decision precedes file compliance. First ask whether the placement identifies the sale item, explains a detail or promotes an offer. Then check the applicable field and account requirements. Do not classify a picture by its filename alone: “hero-final” could contain a previous finish, an expired price or a prop that is not supplied.

Build a small asset-to-placement matrix

Use a separate row for each actual placement, not merely each platform. A store collection card, product gallery and campaign banner can use different crops on the same website. Record the destination owner, upload location and approval date. This is a merchant planning document, not an CartVisual synchronization feature.

Treat a feed image as data as well as artwork

The Google Merchant Center image_link specification, checked October 21, 2026, identifies image_link as the main product image. It separates alternative angles or details into additional_image_link and identifies lifestyle_image_link for in-context representations. Its main-image requirements prohibit promotional overlays and require the exact sale item. The field name and applicable requirements must travel with the selected file.

Do not infer that a rejected main-image poster becomes acceptable by moving it to another Google image field. Nor should Google’s feed rules be treated as the rules of every store gallery or advertising placement. Review the actual destination. Keep detailed file, metadata and public delivery checks in the separate Shopping image preflight; this article decides which asset goes to that check.

Shopify’s Product media types guidance also explains that themes display different sizes of an image in different locations. A correct product-detail view therefore does not settle the collection-card crop. Make a separate row for each relevant slot, even within one store.

Create candidates with a stated destination role

In Product images, upload the exact product references and describe the intended role in the requirements. A white-background candidate should prioritize unobstructed identification. A scene candidate can explain context without implying that every background object is included. Keep promotional wording out of a clean identification request when it has no useful role there.

Download and review the candidate before assigning it to your worksheet. If one image supports two roles, approve each separately. Do not regenerate an already accurate product merely to create a different file name; a controlled external crop may be enough when the new framing keeps the important evidence intact.

Use the cross-channel preflight after role assignment. For exact packaging or small text, a reviewed photograph or externally prepared crop may preserve evidence better than a new generation. The creative request is a brief, not a platform validator or an automatic feed submission.

Release by placement and revisit changed destinations

Fictional lamp exercise, not a submitted feed or ad: file A shows the current black lamp alone; file B shows that lamp on a desk with a notebook not included; file C adds a launch price. For the black-lamp feed main image, evaluate A against that field’s current rules. B may be useful for an appropriate contextual placement only after inclusion and scale review. C needs the intended promotional slot, current offer and landing-page review; it is not the clean feed candidate.

A fourth file shows the white finish. It may be attractive and otherwise accurate, but attaching it to the black option creates a variant mismatch. Correct the mapping rather than grading sharpness again. If the collection card crops out the base, create and review a suitable derivative for that slot; do not mark the full product-gallery image invalid everywhere.

After the authorized publisher uploads a selected file, inspect the actual option, crop, accompanying text and loading route. Separate “uploaded,” “visible in the preview” and “reported accepted by the destination.” A save in My assets establishes none of those external states. Keep the file-to-placement relationship in your asset lineage record.

One file-to-placement decision record

Copy this external record for one actual candidate and placement. Fill the observations from the real exported file and destination; leave unknown checks pending. No example outcome is pre-approved.