Serum drip, toner pour or cream squeeze: which Sume image Format?
Eight Sume catalog Formats make a single beauty hero image from a packshot. What each one shows, so you can pick one for holiday skincare ads.

Pick by the thing the product does: sume-serum-drip for a droplet, sume-toner-pour for a pour, sume-cream-squeeze for a ribbon of cream, sume-formula-texture-hero for texture, sume-water-splash-hero or sume-sunscreen-splash for water, sume-model-product-portrait for a face with the product, and sume-magazine-cover-campaign for a cover layout. All eight make an image from a packshot, and the shipped examples use ChatGPT Image 2 at 9:16.
What does each Format show?
Read from the Format catalog and the shipped example brief for each slug on 2026-10-01.
| Slug | Shot in the shipped example |
|---|---|
| sume-serum-drip | A glass pipette holding one translucent droplet above the bottle |
| sume-toner-pour | Clear liquid pouring around a glass bottle |
| sume-cream-squeeze | Moisturizer squeezing from a tube in one ribbon, macro |
| sume-formula-texture-hero | The bottle surrounded by gel ribbons and macro texture |
| sume-water-splash-hero | The bottle centred in a clear-water splash |
| sume-sunscreen-splash | An SPF tube with white formula and a water splash in daylight |
| sume-model-product-portrait | A model holding the jar beside her cheek |
| sume-magazine-cover-campaign | A close portrait with room for a masthead |
How do I call one?
They share the same wire contract as any Format on the call page. Send the packshot as an attachment and a one-line brief, and read io.output_kind first with GET /v1/formats/sume/{slug} to confirm you get an image.
curl -X POST https://api.sume.com/v1/formats/sume/sume-serum-drip/runs \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: serum-drip-001" \
-d '{
"instruction": "9:16 macro image of one droplet above the attached serum bottle, warm amber light",
"attachments": [{ "type": "input_image", "image_url": "https://example.com/serum.jpg" }],
"generation_spend_cap_usd": 5
}'Which one suits a holiday gift guide?
Gift guides lean on a calm, shelf-ready image, so the portrait and the editorial product set tend to fit better than a splash. For a gift set, see the Editorial Product Set Format. That is a judgment about style, not a measured result; test two slugs on one hero SKU before you run the line.
How do I test two of them cheaply?
Run two slugs on the same packshot with the same cap, for example sume-serum-drip and sume-formula-texture-hero, and compare them next to each other at thumbnail size, since that is how a feed shows them. Keep the brief short and let the Format carry the style. If you want to compare eight, the bulk endpoint is per Format, so you would run one small batch per slug.
What are the limits?
- These are stills. If the channel wants video, use a video Format such as
sume-product-usage-demoorsume-beauty-studio. - Pack text and logo shapes can drift; check labels against the packshot.
- Water and liquid shots are made for skincare and cosmetics; the catalog does not promise they suit other products.
- Beauty claims shown in an ad still need to be true and properly disclosed.
Sources
Related posts
More in Formats
- What is a Sume Format? Turn an agent thread into one API call
A Sume Format is a saved video recipe your backend calls by handle and slug. One POST runs it in a fresh sandbox and returns media plus optional typed JSON.
- How to embed AI video generation in your product with Sume Formats
To embed AI video generation, your server holds one Sume API key and runs a Format per customer, with a derived Idempotency-Key, spend cap, and webhook.
- Sume Format run lifecycle: statuses, webhooks, and polling
A Sume Format run goes from queued to processing to a terminal status. Learn the outcome from one signed format.run.terminal webhook, by polling, or both.
- Sume Format structured output: typed JSON from a JSON Schema
Bind a JSON Schema as output_schema and a Sume Format run returns output in that shape, with each media URL checked against what the run made.
Written by Sume