Sume product commercial vs cinematic studio vs beauty studio
Three Sume catalog Formats make premium 9:16 product films: product-commercial, cinematic-studio-commercial and beauty-studio. How to call each.

Choose sume-product-commercial for a single object on a dark set with one slow camera move, sume-cinematic-studio-commercial for hard-surface products such as devices with macro detail and an orbit, and sume-beauty-studio when a model should appear beside a skincare product. All three are catalog Formats at the sume handle that take a packshot and return a 9:16 video.
How the catalog frames them
The comparison comes from the example brief each Format carries in the Sume repo. The briefs are examples of intent, and your own instruction takes precedence where the two disagree.
| Format | Example subject | Look in the example | Motion in the example |
|---|---|---|---|
sume-product-commercial | Matte black fragrance bottle on dark stone | Narrow rim light, tactile condensation | One slow push-in |
sume-cinematic-studio-commercial | Titanium smartphone | Crisp edge lighting, macro material detail, black reflective set | One precise orbit |
sume-beauty-studio | Serum bottle with a model | Soft editorial lighting, clean skin, polished vanity set | Subtle model and camera movement |
How they are called
All three use the same wire contract as any Format: POST /v1/formats/sume/{slug}/runs, a key with formats:write, an Idempotency-Key and your packshot in attachments. No fork is needed, and the run, its media and its spend belong to the key that called it.
If you want a variation of the look, fork the Format in the library and call your copy at {your_handle}/{slug}. The shared catalog Format itself stays unowned.
To choose between the three, run the same packshot through each with the same cap, and compare the receipts. The Format is a recipe, so the difference you see is the recipe, and that is the quickest way to learn which one fits your product category.
Bind the deliverable
For a pipeline, give the run an output_schema with a SumeMediaFile field and set primary_output_key to it. The run then returns a checked media URL under a name you control, and primary_output_url points at it. Without a schema, the default shape is text, images[], videos[], audio[] and files[].
Budget it
Set a cap you can live with at the call. The Format's cap applies if you send nothing, and the platform default is $400, which is far more than most single videos need. Send an explicit generation_spend_cap_usd per run and compare it to usage.billable_amount_usd_micros on the receipt after a few trial runs.
Sources
Related posts
More in Formats
- Previously on: add a recap to a YouTube Shorts series episode
Open a Shorts episode with a Previously on recap: build it with Timeline 1.0 audio.parts and see what it costs per minute.
- Put your 16 strongest hooks first: Sume bulk queues start in order
A bulk queue returns 202 with the first `concurrency` items already running, up to 16. Order your 100 weekly ads so the best hooks are the first ones you see.
- Recreate a winning ad's structure for your product with Sume
sume-recreate keeps a reference video's scene order, beat timing and caption rhythm, casts a new presenter and generates every shot fresh. How to call it.
- Render a Short and wait for it in one request? Timeline sync mode
Timeline 1.0 can answer a Short render in one request when mode is sync and the job finishes within 30 seconds. Otherwise it returns 202 and you poll.
Written by Sume