Nano Banana 2 product images: reference brief and acceptance checklist

A product campaign needs more than an attractive image: the product must remain identifiable and the crop must fit its destination. This workflow uses nano-banana2 as an example and adds a brief, reference manifest and review gate to the existing image specification guide. It contains no measured quality or consistency claims.

Write a brief that can be reviewed

Separate product facts that must remain unchanged from creative choices that can vary. For a ceramic cup, use this worksheet:

Part of the brief	Example	Acceptance check
Product identity	One cream cup with a round handle	Same handle shape, rim and proportions
Surface	Glossy cream glaze, no lettering	No invented logo, pattern or text
Creative change	Pale blue studio background	Background changes without changing the cup
Composition	Square card with space above the product	Entire handle visible; intended crop remains usable
Delivery	Opaque photographic image	Inspect returned dimensions and file format

These are instructions and review criteria, not guarantees that generation will satisfy them. For packaging text or exact brand artwork, plan a separate deterministic layout step using approved source artwork instead of relying on a generated approximation.

Prepare a reference manifest

Keep the original authorized asset, its version, intended role and crop together. A clean product photograph and a mood board serve different purposes; state which image controls identity and which only informs style. Start with one product reference so a reviewer can identify the source of a mismatch.

Use asset URLs reachable by the generation service for the needed processing window. Do not use a local file path, a login-only page or a URL containing account credentials. Keep signed URLs out of public logs. Check the current model schema before adding more references; a different Nano Banana variant may have different limits.

Build the task input

As checked against repository contracts on 2026-11-03, the following fields are used by the Nano Banana 2 task integration. Before a paid submission, verify the full request_schema from GET /v1/media-models and current access. The URL below is a placeholder: replace it with your own authorized asset.

{
  "model": "nano-banana2",
  "input": {
    "prompt": "Use the reference cup as the product identity. Preserve its cream glaze, round handle, rim and proportions. Place one cup on a pale blue studio background with soft side lighting. Show the complete handle and leave open space above the cup. Do not add lettering, logos or other products.",
    "images": ["https://assets.example.com/approved-cup.jpg"],
    "resolution": "1k",
    "aspect_ratio": "1:1",
    "output_format": "jpeg"
  }
}

Send this body to POST /v1/tasks with server-side Bearer authentication as described in the Nano Banana 2 API guide. Persist the returned task ID and poll that task. If submission times out without an ID, investigate the existing request before resubmitting; the task may already exist.

The Google image generation documentation is a reference for native image-generation concepts, checked 2026-11-03. Its native request format is different from the platform task envelope above. Do not copy native configuration fields into input unless the platform schema accepts them.

Review identity before making variants

Compare the output beside the original at a useful zoom level. Check handle attachment, rim, product count, silhouette, material, invented text and shadows. Then preview the actual destination crop. Reject a visually pleasing result if it changes a product fact. Do not publish an inaccurate product image just because the task status is succeeded.

Record each attempt as brief version → reference version → parameters → task ID → review decision. A creative correction is a new paid attempt, not a network retry. Change one dimension at a time: first background, then composition, then the delivery resolution when necessary. Keep the original product reference available so repeated edits do not silently replace the source of truth.

Expand only after a review gate

For a campaign batch, approve one composition and a maximum number of attempts before creating variants. Track cost per accepted deliverable, including rejected attempts, using the batch budget guide. Check the model calculator for the selected specification rather than assuming a price or a discount. Archive the final image with the approved brief and review decision so the next campaign can reproduce the workflow.