Black Friday image set: 8 products, 4 ratios, 4K for $6.40

Eight products in four aspect ratios at 4K is 32 images. On Nano Banana 2.1 that bills $6.40 on Sume, and $2.40 at 1K. Per-ratio plan and the 202 note.

5 min readSume
All posts

A Black Friday set of 8 products in 4 aspect ratios is 32 images, and at 4K on Nano Banana 2.1 that bills $6.40 on Sume (32 x $0.20). The same set at 1K costs $3.20.

Campaign sets multiply fast: each product needs a square for feeds, a portrait for stories or Reels, a landscape for ads and a wide banner for the site. The cost is small; what needs planning is the list of ratios and the order of work.

The four formats

The Image API docs say Nano Banana 2.1 and Nano Banana Pro include 4:5 in their aspect ratios, which is the Instagram portrait shape (1080 x 1350). A common set is 1:1, 4:5, 9:16 and 16:9. Read the descriptor from GET /v1/images/models to confirm each value before you send it, since an unlisted value returns 400 unsupported_parameter.

Cost of 8 products x 4 ratios on Nano Banana 2.1 by tier (read 2026-10-07)
TierBilled per image32 imagesPer product (4 ratios)
1K$0.10$3.20$0.40
2K$0.15$4.80$0.60
4K$0.20$6.40$0.80

Order of work

Do not start at 4K. Generate the 32 images at 1K first ($3.20), review them, and re-render only the ones that pass at 4K. If 20 pass, the second step costs $4.00 and the whole job $7.20, against $6.40 for 32 images straight to 4K. The two-step route costs more when most pass, so use it when you expect to reject many.

The product photo itself should be a reference, not a text description. Nano Banana models take reference images in the catalog, up to ten, so each prompt can pass the product shot and ask for a new setting.

Naming and handing off the files

A 32-file set is easy to mix up. Use one naming rule, product id then ratio then tier, and write a small manifest with the prompt, billed cost and URL for each file. The manifest doubles as your cost record: sum the cost column and compare it with the planned total before the campaign launches.

Different platforms crop differently. Keep the important subject inside the central 80% of each frame, so a platform that trims the edges does not cut a price tag or a logo. For the wide banner, leave empty space on one side where your layout will put the headline.

Time and delivery

The Sume docs list 4K as a slow setting that can fall back to a 202 job after the 30 second wait. For a 32-image set, send the requests with mode: "async" or a webhook, collect the job results, and write each file under a name that carries the product and ratio, such as sku12-9x16.png.

Why four ratios, not one

Re-cropping a single 1:1 render into 9:16 loses most of the frame, so it is better to ask for each ratio directly and let the model compose for it. The cost is the same per image, and the composition is better.

Check before launch

  • Look at every image at the size it will be shown, not only the 4K original.
  • Keep prices and offer text out of the generated image. Add them in your design tool, so a wrong number does not require a new render.
  • Log usage.cost per image and total it. The set should come to $6.40 if all 32 render once at 4K.
  • Keep the originals; platforms recompress uploads.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume