Masonry Logo

Shoot your whole catalog, not just your bestseller

A studio shoot prices you out of your long tail: the hero SKUs get photographed and the other two hundred get a phone snap on a desk. Generating shots per SKU changes that arithmetic. Upload each product once, restage it into listing and lifestyle shots, and keep one visual language across the entire store.

Cents

Model cost per image, not hundreds per SKU

Minutes

Turnaround instead of a week of scheduling

Every SKU

The long tail, not just the hero products

One look

A consistent visual language across the store

How it works

From a catalog of phone photos to a finished storefront

The workflow that scales past a handful of products.

  1. 01

    Lock a recipe on one product

    Pick a representative SKU, find the model and scene that hold it best, and treat that pairing as your house recipe.

  2. 02

    Reuse the recipe across the catalog

    Run the rest of the SKUs through the same scene brief so the whole store shares one light, surface, and mood.

  3. 03

    Cull hard on fidelity

    Keep only the images where the product is unmistakably itself. Judge accuracy before beauty, especially on labels.

  4. 04

    Export to spec

    Ship square, high-resolution files that satisfy the marketplace you are listing on, and keep one honest photo per product.

Marketplace specs

What each marketplace actually requires

Verified against Shopify and Amazon seller documentation. Getting these wrong is the most common reason a good image still fails on a listing.

  • Shopify: 2048 x 2048, squareShopify recommends 2048 x 2048 px at a 1:1 ratio. Images need to exceed 800 x 800 px for zoom to work, and staying under roughly 300 KB per file keeps pages fast.
  • Amazon: pure white main imageThe main image must sit on pure white (RGB 255, 255, 255) with the product filling at least 85% of the frame. Minimum 500 px on the longest side, and 1600 px or more to enable zoom.
  • Lifestyle and secondary slotsSecondary images are where scenes, scale cues, and detail crops belong. Marketplaces are far stricter about the main image than the rest of the carousel.
  • Paid social and emailDifferent crops again, usually square and vertical. Generating the scene once and re-framing it beats reshooting per channel.
For business

Where stores actually use this

Long-tail SKUs

The products that never justified a studio booking, brought up to the standard of your hero listings.

Seasonal refreshes

Restage an existing catalog for autumn, gifting, or a sale without reshooting a single item.

Marketplace expansion

Re-cut the same product into the specs a new channel demands rather than commissioning a second shoot.

New product launches

Get listing images ready from a sample photo while the production run is still in transit.

A/B testing creative

Generate several scenes for one product and let conversion data pick the hero instead of taste.

Agencies and dropshippers

Give many small clients or many suppliers a coherent look without a photographer per account.

Commercial use

Listing these safely

Renders are high-resolution and licensed for commercial use, so they can go straight onto product pages and marketplace listings. Two rules keep you out of trouble at catalog scale: never ship a generated label as final artwork when it carries regulated copy such as ingredients, volumes, or safety text, and always keep at least one honest photo of the real product on the listing. A scene that oversells what arrives converts once and then comes back as a return.

FAQ

AI product photography for ecommerce

What store owners ask before running this across a catalog.

Can I keep a consistent look across hundreds of SKUs?

Yes, and it is mostly a process question rather than a model one. Lock a recipe first: pick one representative product, settle on the model and the scene brief that hold it best, then reuse that same brief across the catalog. Consistency comes from reusing the scene description and the model, not from generating each product from scratch with a fresh idea.

Will these images meet Shopify and Amazon requirements?

They can, but the specs are on you to hit. Shopify recommends 2048 x 2048 px square images, needs more than 800 x 800 px for zoom, and rewards files under about 300 KB. Amazon requires the main image on pure white (RGB 255, 255, 255) with the product filling at least 85% of the frame, at least 500 px on the longest side and 1600 px or more for zoom. Generate at high resolution, then crop and export to the target spec.

Will it keep my exact product?

Yes, and this is the part that matters most. You upload a clean photo of your real product, and the models restyle the scene around it, so the label text, shape, color, and finish stay yours instead of being reinvented. Different models hold fidelity differently on the hard cases (frosted glass, small printed labels, reflective metal), which is exactly why comparing several on your actual product beats trusting one pipeline. Upload the clearest, best-lit shot you have for the most faithful result.

Is this actually cheaper than a studio shoot?

For everything below the flagship tier, by a wide margin. A studio product shoot runs a few hundred dollars per SKU and takes a week to schedule, shoot, and retouch. Model calls cost roughly cents to a couple of dollars per image and return in minutes. The real saving is not on your bestseller, which probably still deserves a photographer, it is on the long tail that currently has no proper photography at all.

Which model should I use across a catalog?

There is no single best model, and that is the point. Different models win at different briefs, so Masonry gives you all of them in one workspace and lets you compare results side by side. For an ecommerce catalog, Nano Banana Pro is the best all-rounder for photoreal results with faithful layout, Seedream is fast and detailed for exploring options, FLUX gives the most control for a consistent style, and GPT Image is great for precise edits. You pick the winner for each shot instead of being locked into one engine.

Do I have to disclose AI product images?

Rules vary by marketplace and region, and they are moving, so check the policy of each channel you sell on rather than assuming. Independent of policy, shoppers are increasingly sceptical of imagery they suspect is synthetic, so the practical stance is the same either way: keep the product itself faithful, keep a real photo on the listing, and use generated scenes for context and mood rather than to imply something the buyer will not receive.

Give every product a proper photo

Start with one SKU, find the recipe that holds it, then run the rest of your catalog through it.