Video templates

Turn a template into a video by giving it a duration and FPS in Settings, then use the Timeline panel to add video/audio elements and animation. Audio can be an uploaded track, a video's own soundtrack, or a voice-over Studio generates from a templated script. Studio's canvas is what actually gets rendered, so what you see is what you get.

Updated July 28, 2026

Any Studio template can become a video template. The difference between an image template and a video template comes down to one thing: whether the template has a duration. Once it does, video and audio elements become usable, a Timeline panel appears, and your animation effects can actually play.

Enabling video mode#

Video mode is a per-template setting, found in the Settings panel:

  1. Open the template's Settings panel (docked on the right by default).
  2. Find the Video setting and turn it on (a +/Remove-style toggle).
  3. Set the duration (up to a maximum of 30 seconds) and choose an FPS (frames per second) of 24, 25, 30, or 60.

Once duration is set above zero, the template is a video template: the Timeline panel appears at the bottom of the editor, and the Video and Audio tools on the canvas toolbar become meaningful (they exist either way, but only do something once there's a timeline for them to sit on).

Duration and FPS are template-wide settings, not per size — a template with several sizes renders every size as a video (at the same duration and frame rate), or none of them. You can't enable video for one size and leave another as a still image. See Sizes and formats for what does and doesn't vary by size.

The Timeline panel#

The Timeline panel runs along the bottom of the editor, once your template has a duration. It shows every element as a track, with its animation effects placed on that track as blocks you can drag to reposition or resize (changing when an effect starts and how long it plays).

Use the Timeline to:

  • See at a glance which elements are animated and when they play relative to each other.
  • Line up entrances and exits so elements don't compete for attention at the same moment.
  • Scrub through the video to preview it at any point in time, not just the start.

For a full explanation of tracks, start/end frames, and easing, see Effects and animation overview.

Adding video and audio elements#

Once video mode is on, you can add:

  • Video elements, via the Video tool on the canvas toolbar.
  • Audio elements, via the Audio tool. Audio elements have no visual presence on the canvas — they only show up in the Elements tree and on the Timeline. In some places in the product, an audio element is labeled "Voice over" rather than "Audio."

An audio element's sound can come from three places:

  • A generated voice-over from a script. Give the audio element a binding — the same product-data binding you'd put on a text or image element — and Studio generates a spoken track from it with text-to-speech at render time, in your catalog's language. No audio file needed. The usual way to do this is a Voice script placeholder: AI-written, per-product pitch copy read aloud, so every product's video gets its own voice-over from its own data. Write the scripts with a prompt, then add a Voice script placeholder to the audio element (see Available placeholders). When an audio element is bound this way, its source shows as bound to product data and the upload controls are hidden.
  • An uploaded audio file — background music or a pre-recorded voice-over. Use Upload audio on the element (MP3, WAV, AAC, or OGG). You can trim it with Clip start / Clip end, change its Speed, and set its Volume.
  • The soundtrack of a video element — if you add a video that already has sound, that audio plays as part of the video; adjust it with the video element's Volume.

There's no separate "generate a music track" button — background music is always an uploaded file. It's only the spoken voice-over that Studio can generate for you, from a Voice script.

Once video mode is on, you can also ask Aimée to generate an AI image or video directly into the template — a backdrop, a product shot, or a full hero video. See Working with Aimée for how that works and its cost trade-offs, and AI image and video generation for the separate, per-product prompt-based path.

The canvas is what actually renders#

It's worth trusting what you see in Studio: the canvas and the Preview section use the same components as the renderer that produces your real, at-scale product videos and images for channels and ads. This isn't a simplified mock-up that approximates the final output — it's a live instance of the same rendering pipeline. If a video looks right in Studio, at the frame rate and duration you've set, it will look the same way when it's rendered for real across your whole catalog.

That guarantee is also why it's worth using Preview with a real product before publishing a video template — automations and placeholder bindings can change what's visible at any given moment, and Preview is the fastest way to confirm the final result product-by-product.

Where to go next#