Start here
Make your first product video with Opus 5.5
Finish one 18-second product film with a usable source project.
The first film is a production exercise, not a test of how many effects a model can invent. We will work with one feature, two real screenshots and a three-part story. Each review has a concrete deliverable so you can correct a weak idea before it becomes a long render.
What to know before you begin
Start with a deliverable
Choose one product feature and one audience. For a first attempt, our suggested scope is 15–20 seconds with three beats: the problem, a real product action and an end card. Collect the exact logo, two screenshots and the final call to action before asking for code.
Choose the authoring environment
Use the official Remotion skills if you already work in React. HyperFrames is an alternative for HTML compositions. Ask the agent to inspect the installed tool’s current documentation and create a minimal project. A model writes the scene; the renderer produces the video file.
Review before scaling up
Approve three still frames before a five-second test render. If the type or product screenshot is wrong, fix it at this stage. Then export the full clip and watch it at normal speed, with and without audio. Check that the file opens outside the preview app.
THE COMPLETE WALKTHROUGH
From input to delivery, step by step
01Collect a tiny production kit
Make a folder containing the logo, before and after screens, approved headline and one action. Use stable filenames. Note the intended audience and placement in a brief. A launch for an existing user can start inside the product; a new visitor needs the problem established first.
02Draw the film before animating it
Ask for opening, product proof and end-card stills at the final aspect ratio. Read each at phone size. If the product screenshot is too dense, select a meaningful crop. A transition cannot rescue a frame that lacks a clear visual hierarchy.
03Keep the proof on screen
The product action deserves the largest share of the film. Let the viewer see what changed, not merely that a card moved. Use a short caption to connect input and result. If you need a voiceover to explain every frame, simplify the visual sequence.
04Give the first render a narrow job
A five-second test should prove typography, asset loading and basic motion at the output resolution. Do not judge the whole story from it. Fix technical failures here, then extend the same project rather than starting a disconnected second draft.
05Package what the next revision needs
Deliver the source, final MP4, a poster and a note containing dimensions, frame rate, asset sources and unresolved issues. Keep the final copy outside the animation logic. When the headline changes next week, the next editor should not need to rediscover the production decisions.
An 18-second example plan
Use this editorial plan as an editable working document, adapting it to the actual assets and placement.
| Beat | Input | Review goal |
|---|---|---|
| 0–4 s · Problem | Before screenshot + one sentence | Context is clear without audio |
| 4–13 s · Proof | A real interaction and its result | The product does what the caption claims |
| 13–18 s · Action | After screenshot, logo and one CTA | The viewer knows what to do next |
A complete request to adapt
This is an original example for this tutorial. Replace the placeholders with your task and retain the preparation, review and delivery requirements. Ask the agent to identify missing inputs before production.
Build an 18-second film for [one product feature] using these real assets: [files]. Audience: [audience]. Placement: [channel]. Format: [dimensions], 30 fps. Use problem → product proof → one action. First give a shot list and three still frames. After review, render a five-second test, then the complete file. Keep copy and assets editable. Do not invent UI, metrics or testimonials. Deliver the source, MP4, poster and review notes.Where the process can get stuck
The film looks generic
Replace abstract benefits with a recognizable product action. Use your actual typography and one repeated graphic motif instead of adding several unrelated effects.
The model keeps changing approved scenes
Name the files and scene boundaries to preserve. Ask for a targeted change and compare representative frames before accepting the revision.
Should I add music immediately?
First make the story readable without sound. Then select permitted audio and align meaningful changes with it. A strong beat cannot make missing product evidence visible.
APPLY IT TO YOUR PROJECT
Finish one small, reviewable output
Walk through the process with your own inputs. Save the first output and specific review notes: what works, what needs changing and how to reproduce it. Once the small test passes, extend the duration, complexity and delivery variants.
References & editorial notes
Consult the original projects for current capabilities, eligibility and setup. Exercises, timings, sample requests and review advice are Hermes editorial work. Creator outputs and teaching illustrations are labeled where shown.