What image sizes work best for the character, scene, and product?

Use clean, high-resolution sources (e.g., 1024–2048 px on the long side). Keep similar scales across inputs so the model can align them more naturally. Transparent PNGs for products help with clean placement.

How do I keep brand details (logos, patterns) accurate in the composite?

Start with a clear, front-facing product image and call out constraints in the brief (e.g., “preserve logo and pattern”). If the GeminiImage2Node exposes style/strength controls, reduce the style strength to favor fidelity.

How can I generate multiple looks on the same setup?

Create several brief variants in PrimitiveStringMultiline or, if available, increase the variation/batch setting in GeminiImage2Node. BatchImagesNode will tile the resulting frames into a single contact sheet for fast comparison.

Where are the outputs saved and in what format?

SaveImage controls filename prefix and format (PNG/JPG). Files are written to your ComfyUI output directory. Set a unique prefix per run to keep iterations organized.

Step 1: Contact Sheet Workflow

This ComfyUI workflow builds a fast, repeatable contact sheet for fashion editorial concepts by compositing three inputs—your character, a scene/background, and a product—into cohesive images. Three LoadImage nodes bring in your assets, a PrimitiveStringMultiline node holds your creative brief, and a GeminiImage2Node uses the "Nano Banana Pro" model to integrate the images according to your instructions (lighting, mood, styling, composition). Because the model conditions on all three sources plus text, it can harmonize color and lighting while preserving key identity and product details.

Once the GeminiImage2Node produces one or more variations, a BatchImagesNode assembles them into a multi-tile contact sheet for quick side-by-side review. Finally, SaveImage writes the resulting grid (and/or individual frames, depending on how the graph is wired) to your output folder. The result is a practical, iteration-friendly tool: feed it new characters, scenes, or products and quickly compare editorial directions without rebuilding the pipeline.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

template_contact_sheet-step_1.app.json

Fetching workflow JSON…

Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

// Install (beta)
npm i @comfyorg/sdk

// Run "Step 1: Contact Sheet Workflow" (TypeScript)
import { Comfy } from "@comfyorg/sdk";

const client = new Comfy({ apiKey: "comfyui-..." });

// This workflow, exported in API format (see note below)
const wf = await client.workflows.fromFile("template_contact_sheet-step_1.app_api.json");

const asset = client.assets.fromFile("input.png");
wf.setInput("1", "image", asset);  // LoadImage

const job = await client.run(wf);
await job.getOutputs("4")[0].toFile("output.png");  // SaveImage

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).

Comfy Cloud API access requires a plan with an API key.

SDK docs Get an API key

FAQ

Frequently Asked Questions