Use case

AI product photos for an online store: models, prompts, cost

Plan AI product photos from $0.014 per 2K request: compare models, adapt prompts, inspect product details and budget a store catalog before scaling.

10 min read
“AI product photos from $0.03 at 2K” — one phone photo in, a full listing set out: a 2K photo from $0.03 per image, drafts at $0.005 per image, 100 products × 5 photos from $15 at 2K; a ceramic mug shown in three glass photo frames

A 2K image-generation request for a product photo costs $0.014 on Nano Banana 2.1 through API Stock, or $7 for 500 requests, at the public catalog rate checked on 30 October 2026. Start with a real product photograph, describe the new setting, and compare the output with the original before using it in a listing. The price buys a generated candidate; it does not guarantee an accurate, approved product photo.

Updated 30 October 2026. Rechecked the public catalog: at 2K, Nano Banana 2 is now $0.020, Nano Banana Pro $0.029 and Seedream Pro $0.079 per request. We corrected the store budgets, added an eight-request pilot and clarified how to retrieve the finished image. The cover retains its 28 September prices; the workflow graphic also shows historical prices. This is a prompt recipe and cost calculation, not a controlled product-preservation benchmark.

What can AI do for your product photos?

Reference-based editing lets you ask for a different background, lighting or setting around a product you have already photographed. Useful jobs to try include a packshot on white, a lifestyle scene, a seasonal banner and a feature card. The important distinction is between requesting the same product and proving that the output still represents it accurately.

Photograph every side that a customer needs to see. A generated view of an unseen back panel is not evidence of the real product's construction. Likewise, a realistic new label, seam or fastener can make a beautiful image unsuitable for your listing.

If the product itself must remain unchanged, keep the original product cutout as a separate layer and generate only the setting. Composite them in an editor and check the shadow and edges. Use full-image generative editing when you can inspect the result and accept the changes it makes. Our image-editing guide explains reference-based workflows.

Which AI model should you try for product photos?

Start with the output size and the budget you need, then test your actual product. The table below compares public tariffs and supported request options; it does not rank image quality. Prices are USD per generated image, checked against the live API Stock catalog on 30 October 2026, with one reference image per request. These are public usage tariffs; account-specific prices may differ.

ModelPrice per generated imageWhen it is worth tryingWhat to check
Nano Banana 2.1$0.014 at 1K, 2K or 4KA low-cost first candidate at 2K or 4KProduct details, crop and actual downloaded dimensions
Nano Banana 2$0.018 at 1K, $0.020 at 2K, $0.026 at 4KKeeping an existing workflow while comparing a new optionWhether switching models improves your own accepted results
Nano Banana Pro$0.029 at 1K or 2K, $0.043 at 4KA second candidate for the same editing briefLogo, material, colour and geometry against the original
GPT Image 2.5 Sunburst$0.01 at 1K, $0.035 at 2K, $0.05 at 4KTrying a layout or short text as part of an imageEvery word and number; add exact typography separately when needed
Seedream 5.0 Lite$0.03325 at 2K, 3K or 4KComparing a second model at a flat resolution priceConsistency across your own references and scenes
Seedream 5.0 Pro$0.040 at 1K, $0.079 at 2KTrying a composition guided by multiple references$0.004 for each reference after the first; maximum output tier is 2K
Nano Banana 2 Lite$0.005 per requestSketching a composition with a 1K requestA draft on this model does not predict another model's output

For a first 2K attempt, open Nano Banana 2.1 because its listed request price is lower than the other 2K options in this table. That is a budget-based starting point, not a finding that it preserves every product best. Keep an existing model if it already produces assets you accept; the cheapest request can become expensive if it needs many rejected attempts.

How do you turn one phone photo into a listing set?

Begin with one product and one background edit. Agree on what counts as usable before preparing a batch:

  1. Prepare the reference. Photograph the whole item in focus, with its important label and details visible. Use the real colourway and angle you intend to show.
  2. Write a narrow brief. State what should change and which details must remain. Choose the aspect ratio for the actual listing placement.
  3. Generate one candidate. Supply the original photograph each time you try a new scene. Reusing an earlier generated image can carry its changes into the next edit.
  4. Compare before publishing. Inspect the shape, material, colour, lettering, small parts and framing. Reject a candidate that changes something the customer would receive.
  5. Expand only after acceptance. Try the remaining scenes on that product, then a small selection of other products before scaling to the whole catalog.
Editorial workflow illustration: one reference leads to a packshot, lifestyle scene, detail view and feature card; the graphic labels the intended edit as keeping the product unchanged.
Editorial workflow illustration: one reference leads to a packshot, lifestyle scene, detail view and feature card; the graphic labels the intended edit as keeping the product unchanged.

This is the original editorial illustration, generated with GPT Image 2.5 Sunburst. Its source photo is synthetic, and the four scenes illustrate intended edits rather than measured model outputs. “Keep the product unchanged” is an instruction to check against each result. The graphic's $0.04 each and $0.16 for four Nano Banana Pro requests are historical; at the 30 October 2K tariff, four requests cost 4 times $0.029 = $0.116 before further attempts.

Use a separate close-up reference for a detail view. Cropping or generating a larger image cannot establish a texture or marking that is absent from the source.

Which prompts can you adapt for product photos?

These are starting recipes, not outputs tested in this article. Replace the mug with your own product and compare every candidate with its reference.

Packshot on white:

text
Place the mug from the reference photo on a seamless white background,
centred and fully visible, with a soft natural shadow. Keep the same viewing
angle. Preserve its shape, colour, glaze, handle and label. Do not add another
object, new lettering or decorations.

Check the handle opening, rim, label and shadow. If any product detail changes, do not treat a stronger preservation sentence as a guarantee; try a different edit or composite the original cutout.

Lifestyle scene:

text
Place the mug from the reference photo on a light oak breakfast table beside
a window, with soft morning light from the left. Keep the full mug visible.
Preserve its shape, colour, glaze, handle and label. Keep background props
away from the mug and add no text.

Choose a setting that leaves the important product details visible. Review how the light and contact shadow fit the scene.

Seasonal banner:

text
Place the mug from the reference photo on a wooden surface with autumn
leaves in the background. Use a wide 16:9 composition with empty space on
the left for a headline added later. Preserve the mug's shape, colour,
handle and label. No text and no extra product.

Check that the eventual crop leaves the whole product in frame. Add the headline in your design tool when position and spelling must be exact.

Feature card:

text
Create a 3:4 product feature card. Place the mug from the reference photo on
the right against a plain beige background. On the left, add three short
labels: "Dishwasher safe", "350 ml", "Handmade ceramic". Use clean sans-serif
type. Preserve the mug's appearance and add no other claims.

Use those labels only if they are true of your product. You can try this brief on the text-capable image options in the table, but this recipe does not establish a winner for typography. Proofread every letter and digit, or generate a text-free composition and add the labels in an editor.

For a series, reuse the same scene instruction and vary only the reference. Compare the series together: repeated wording does not guarantee identical lighting, framing or product appearance across independent requests.

What should you try before a whole-store batch?

Use one product to plan four placements: a white-background image, a lifestyle scene, a banner and a feature card. Prepare a separate close-up photograph if you also need a detail view. Begin with the white-background prompt above in the Nano Banana 2.1 playground, explicitly select 2K and check the $0.014 request quote before generating.

If you allow two candidates for each of the four placements, the pilot is eight separate requests. At the 30 October 2026 public catalog tariff, with one reference per 2K request, its generation budget is 8 times $0.014 = $0.112, or $0.11 rounded for display. Two candidates is a spending allowance, not a prediction that either one will pass.

Accept an image only if its product shape, colour and visible markings match the source, its crop fits the placement, and any added text is correct. Record each task ID, scene, request price and rejection reason. If a second candidate repeats a changed handle or invented label, stop buying variations of that brief: simplify the edit, use a clearer reference, or composite the original cutout into a generated background.

If the eight paid attempts produce four images you accept, the cost per accepted image is $0.112 divided by 4 = $0.028. If only two pass, it is $0.056 each; if none pass, there is no accepted image to price. These are conditional calculations, not results of a test. Keep every paid attempt in the total, including attempts on another model, before deciding whether to expand to more products.

How much does AI product photography cost for a whole store?

For 100 products with five image requests each, the generation count is 500. The following calculations use the 30 October 2026 public catalog tariffs in USD, 2K requests and one reference image per request. They exclude extra references and additional attempts. Totals are rounded to cents for display.

ModelCatalog tariff per 2K requestCalculation for 500 requestsTotal
Nano Banana 2.1$0.014500 × $0.014$7.00
Nano Banana 2$0.020500 × $0.020$10.00
Nano Banana Pro$0.029500 × $0.029$14.50
Seedream 5.0 Lite$0.03325500 × $0.03325$16.63
GPT Image 2.5 Sunburst$0.035500 × $0.035$17.50
Seedream 5.0 Pro$0.079500 × $0.079$39.50

The balance debit retains fractional cents. The Seedream Lite total uses the full $0.03325 tariff: $16.625 before display rounding. Multiplying a shortened $0.033 label would give a different answer. For Seedream Pro, a second reference on every request adds 500 times $0.004 = $2.00, bringing its 2K total to $41.50.

These are request budgets, not promises of 500 usable photos. If you choose to budget three paid candidates per desired image, 500 accepted images would mean 1,500 requests and $21 on Nano Banana 2.1, assuming one of each three candidates is accepted. That acceptance rate is an example assumption, not a measured result.

For an actual run, divide the total generation spend by the number of images that pass your acceptance criteria. Twenty $0.005 draft requests would add $0.10; they only save money if the drafts help you avoid unnecessary later attempts. Technically failed generations are refunded; completed images that fail your visual review still count as paid requests.

The dated pricing record links the catalog snapshot and calculation assumptions. Check current pricing before a larger run; a generation budget is separate from the amount you choose to top up.

What should you check before publishing a product image?

Compare the candidate with the original at a useful zoom level. Check the silhouette, proportions, colour, texture, logo, label, number of parts, shadows and crop. A plausible-looking change can still misrepresent the item.

For colour-critical variants, photograph each actual colourway. For fine print, use a real close-up or place verified text separately. If repeated edits alter the product, keep the original cutout and change the background as a separate layer.

Check the current image requirements of the destination marketplace or store before uploading. This workflow does not establish that a platform will accept an image. A completed API task confirms that a file was generated, not that it passed your commercial review.

Can you automate it for the whole catalog?

Yes. Once a small sample meets your criteria, a script can create one task per product and scene, track each task ID and send completed outputs to review. First try the workflow in the Nano Banana 2.1 playground.

This request uses parameters checked against the current public schema. Replace the example reference URL with your own accessible image and set API_STOCK_KEY in your environment. It is an integration example, not a test run reported by this article.

sh
curl -X POST 'https://api.api-stock.com/api/v1/generation/create' \
-H "Authorization: Bearer $API_STOCK_KEY" \
-H 'Content-Type: application/json' \
-d '{
"model": "nano-banana-2.1",
"input": {
"prompt": "Place the mug from the reference photo on a white background with a soft shadow. Preserve the mug, handle and label. No extra objects or text.",
"urls": ["https://your-domain.example/product.jpg"],
"size": "1:1",
"resolution": "2K"
}
}'

Read data.taskId from the create response, set TASK_ID to that value and poll the same task:

sh
curl "https://api.api-stock.com/api/v1/task/status/$TASK_ID" \
-H "Authorization: Bearer $API_STOCK_KEY"

Wait with increasing delays while data.status is not_started or processing. On finished, download the image from data.files[0].fileUrl. On failed, inspect data.errorMessage; the generation charge is refunded. Repeating the create call starts another paid candidate, so retain the original task ID while waiting. You can instead provide a top-level webhook URL for completion delivery.

If a reference cannot be fetched, check that its image URL works without a login and remains available until the task finishes. The urls field contains image addresses, not a local filename or an image ID from another service. Create a separate task for each candidate; do not add a batch-count parameter.

See the task documentation for status and webhook handling, the image model reference for supported inputs, and the image-generation guide for the broader workflow.

FAQ

How much does an AI product photo cost?

A Nano Banana 2.1 image-generation request costs $0.014 at 2K on API Stock, as checked on 30 October 2026. Five hundred requests cost $7 before additional attempts. The cost per usable photo depends on how many outputs pass your review.

Which AI model is best for product photos?

This article does not establish a quality winner. Start with a model whose resolution and price fit your task, then compare actual outputs with your product photograph. Nano Banana 2.1 is the lowest-priced 2K option among the models in the table.

Can AI keep the product exactly unchanged?

A preservation instruction does not guarantee identical product details. When the product must stay unchanged, keep the original cutout as a separate layer and generate the background around it in your editing workflow.

Can I use AI-edited photos on a marketplace?

Check that marketplace's current rules and inspect whether the image accurately represents your item. A successful API generation does not establish marketplace acceptance.

Do I need to know how to code?

No. Open the model playground, supply a reference, choose the output format and try a prompt. Code becomes useful when you need to submit many tasks and organize their review.

  • ecommerce
  • image
  • product-photos
  • seedream

Try it with your own key

Choose a model in the API Stock catalog, check its price and try it in your browser or through the API.

Read next