Starting point · Without a product sample

    How to Make Videos Without a Product Sample

    You need a product image before you need a product video. Generate or rebuild the pack shot first, lock it as a reusable asset, and every clip afterwards inherits it.

    product hasn't shipped yetpre-order with no samplesonly have supplier photosdropshipping product videodigital product with nothing to filmno packaging yet

    The situation

    This constraint is specific to commerce. The product exists as a spec, a render, a supplier photo, or a promise — but there is no unit in your hands to point a camera at. It applies to pre-launch, to pre-order campaigns, to dropshipped catalogues, and to anything digital that has no physical form at all.

    The route is the photo-in class, entered one step earlier than usual. 113 models start from a still you supply, and 38 accept reference images so the same object survives from clip to clip. The missing piece is the still itself, so the first job is producing one you can defend.

    There is also an editorial limit here that does not apply to the other constraints on this hub, and it is worth being blunt about: a generated image of your product is an illustration. It can carry a mood, a use case, or a category. It cannot stand in as evidence of a unit you have never seen.

    What the model catalog says about it

    Every model declares the input it requires, so “what you don’t have” is a filter over the catalog rather than a mood. These are counted from the live snapshot at build time.

    Photo-in models

    113

    animate from a still — which is why the pack shot is the real deliverable

    Reference-capable models

    38

    accept reference images, keeping one object consistent across a set of clips

    Product assets published

    3

    workflow assets typed as a product — the pattern for locking an object into a recipe

    Which route fits you

    Find the line that matches your situation, then read that route.

    The routes that work

    1

    Make the pack shot before you make the video

    Use it when: Nothing visual of the product exists yet.

    1. 01Write the product as a physical description: material, finish, size relative to a hand, label layout, colour. Vagueness here becomes a different product in every clip.
    2. 02Generate the still on a plain background first. A clean isolated object is reusable; an object generated inside a scene is locked to that scene.
    3. 03Fix the label. Generated packaging text is unreliable, so treat readable branding as something you place afterwards rather than something you prompt for.
    4. 04Save the approved still as the reference asset. Everything downstream — clips, thumbnails, variants — starts from this one file.

    Run it here

    2

    One supplier photo, a whole campaign

    Use it when: You have exactly one usable image and need a set of clips from it.

    1. 01Clean the source: cut it out of its background, straighten it, and upscale it before it becomes an input to anything else.
    2. 02Register it as a reference asset so every generation is anchored to the same object rather than a fresh interpretation.
    3. 03Generate the scenes around the object — hands, surfaces, environments — rather than regenerating the object into each scene.
    4. 04Review for drift across the set. When the label, proportion or colour changes between clips, the campaign reads as several different products.

    Run it here

    3

    Sell the outcome, not the object

    Use it when: The product is digital, unphotogenic, or genuinely unavailable — and the change it causes is more interesting than the thing itself.

    1. 01Structure the video as before and after, with the product appearing only at the turn. Two thirds of the runtime never shows it.
    2. 02Make the "before" specific. A generic frustration is skippable; a precise one is the whole hook.
    3. 03Show the product once, clearly, at the moment of change — one clean beat is worth more than product footage throughout.
    4. 04End on the changed state rather than on packaging, which is what the viewer is actually buying.

    Run it here

    What this does not fix

    Routing around a missing input is not the same as not needing it. Three things stay broken.

    • It does not let you demonstrate a result you have not verified. Generated footage of a product working is a depiction, not a test, and presenting it as proof is a claim you cannot support.
    • It does not produce a listing image. Marketplaces that require photographs of the actual item are not satisfied by a generated render, whatever it looks like.
    • It does not settle disclosure. Where an ad shows a generated depiction of a product, say so if the platform or the local advertising rules expect it.

    Frequently asked questions

    Can I advertise a product with generated footage of it?+

    You can illustrate it. What you cannot do is imply the footage is a photograph of the real unit, or demonstrate performance you have not verified. Keep generated product visuals in the role of illustration, follow the disclosure rules of the platform you are advertising on, and reserve claims for things you can substantiate.

    How do I keep the product looking the same across ten clips?+

    Reference assets. Generate one approved still, register it as a reference, and anchor every subsequent generation to it — the catalog's reference-capable models exist for precisely this. Re-prompting the object per clip is the reliable way to end up with ten near-misses.

    What about the packaging text and logo?+

    Do not rely on a model to render them. Generated type is inconsistent at the level of individual characters, so treat branding as something you composite on afterwards, and prompt for a plain or blank label deliberately.

    Is this route different for digital products?+

    Yes — there is no object to reconstruct, so skip the pack shot entirely and use the outcome route. Screen recordings of the real interface plus generated context around them beat any attempt to make software look like a physical thing.

    If that wasn’t your constraint

    People usually arrive here missing one thing and leave realising it was a different one.

    Publishing on a schedule with the same gap?

    A route gets one video made. A format gets the next twenty made — same constraint, decided once.