How Do You Make a Product Demo Video With an AI Agent?

A demo video usually dies at the first product change. The button moves, the screen recording is wrong and nobody wants to record again. A film drawn from code can be rebuilt.

TL;DR
Ask a coding agent to build the video from your product's own interface. The open-source product-film skill does this. The agent copies your screens into one HTML page, animates them on a timeline and renders every frame with Playwright. Then ffmpeg cuts the film. It does not record your screen and it does not use a video model. It needs a computer with a shell, Node and ffmpeg. It suits teams that have a front end in code and want to recut videos often.

A demo video usually dies at the first product change. The button moves, the screen recording is wrong and nobody wants to record again. A film drawn from code can be rebuilt.


1) Three ways to make a demo video

MethodYou getWeak point
Screen recorderA recording of your real screenA UI change or a mistake means a new take
AI video generatorA clip from a modelThe model invents the interface. The screens may not match your product
Video from code (product-film)A render of your real componentsNeeds a local shell. Setup takes a developer's time

This post covers the third method.


2) What product-film is

product-film is an open-source agent skill. It is under the MIT license, and the source is at github.com/display-dev/product-film. We made it. Display made it for its own films, then published it. Version 0.2.0 was current when we checked on 14 October 2026.

Install it with this command in your agent's terminal:

npx skills add display-dev/product-film --skill product-film

Then describe the film. For example: "Make a 30-second launch film for the new share dialog."

The docs say it works in Claude Code, Cursor, Codex, OpenCode, Hermes and Pi.


3) How it works

A film here is a function of time. One HTML page holds the whole film. The call window.seek(t) draws frame t from scratch.

  1. Timeline page. The agent copies your components from your production code, or captures live screens from your running app. Your API answers with fictional data. The page also holds a camera, a pointer and captions.
  2. Every frame. Playwright opens the page headless and screenshots each frame.
  3. Encode and cut. ffmpeg encodes the frames. It joins the beats and writes a master file, a web file, a review file, a poster and a contact sheet.
  4. Review. The agent publishes one review page to Display. Each new cut is a new version of that page. You comment on the page, and the agent answers in each thread.

Because the film is code, three things hold:

  • Text stays sharp when the camera pushes in. It is real text rendered at 2x or 3x.
  • A recut re-renders only the beat that changed.
  • Feedback maps to numbers. "Hold the comment longer" changes one number.

4) What you need

The skill renders on the machine where your agent runs. That machine needs:

  • Node 18 or later with npm. Playwright installs into each film folder. Chromium downloads once per machine and takes about 100 MB.
  • ffmpeg with libx264.
  • Python 3, for the paper-collage route only.

A hosted chat app with no local shell can read the skill and plan a film. It cannot render one.


5) Four routes

RouteGood forTypical length
A: cinematic with footageWebsite hero loops with people in them30 s loop
B: cinematic, product onlyLanding sections and launch teasers20 to 25 s
B: reelLaunches that show several capabilities25 to 35 s
C: kinetic walkthrough (default)Store-listing promos and feature launches35 to 40 s
D: paper collageSocial cuts and explainers45 to 60 s

For a demo, Route C is the default. A pointer drives one story through isolated UI at close range. You name a length and the agent follows it.


6) What it does not do

  • It does not record your screen. Every frame comes from code.
  • It does not generate video, images or audio with models. The default cost is nothing beyond your agent's usage.
  • It makes silent films unless you supply a music track. It does not compose music or record voice.
  • It cannot judge sound. An agent cannot hear. The skill measures levels and tells you that your ears must check the rest.
  • It needs your front end. If you have no components or running app to capture, there is nothing to draw.
  • It leaves taste to you. You choose looks and license any footage. The agent publishes only the review page, and only when you ask.

7) How it compares

We checked each tool on its own site on 14 October 2026.

ToolApproachCost and licenseBest for
product-filmHTML timeline, Playwright frames, ffmpeg. Built for product UIMIT, freeTeams that rebuild demos often
HyperFramesHTML compositions rendered by seeking each frame in headless Chrome, then ffmpegApache 2.0, no per-render fees. Needs Node 22 or later and ffmpegGeneral video from HTML, for agents
Remotion with its agent skillsVideo written as React code. Skills install with npx skills add remotion-dev/skillsFree for individuals and companies of up to 3 people. Companies of 4 or more need a license. Creators plan: $25 per month per seatTeams that already write React and want a large ecosystem
Screen recorderRecords your real screenMany options and pricesOne-off demos where polish matters little

How to choose:

  • Pick product-film if your goal is a film of your own product UI, with a review loop on Display built in.
  • Pick HyperFrames if you want a general HTML-to-video engine for any subject.
  • Pick Remotion if your team lives in React and wants its component model for video.
  • Pick a screen recorder for a quick demo that you will not recut.

We built product-film, so weigh our view. The other tools do things product-film does not.


8) A first film in practice

  1. Run the install command above.
  2. Ask your agent for one short film. Name the feature and the length.
  3. The agent asks what it cannot infer: the story in one line, the route, the length and the sources for every claim.
  4. It builds beats one at a time and checks each on a contact sheet.
  5. It publishes a review page to Display. Your team opens it with the Google or Microsoft account they already use and comments on the cut.
  6. The agent answers each thread and publishes the next cut as a new version of the same page.

Display is the docs workspace for agents and people. Any agent publishes docs and files to a link. Your team opens the link with the account they already use. They comment and edit in-line. Any agent or teammate can publish the next version to the same link.


9) Limits to plan for

  • Setup takes longer and needs more steps than a screen recorder.
  • Your first film needs fictional data for any screen that shows people or companies. The skill supports this, but you must supply or approve the story.
  • Outside guests can view a review page you share. They cannot comment on it yet.

For a website loop, read how to make a hero video from your product UI.


We checked product-film in its docs on 14 October 2026, HyperFrames on its GitHub page, and Remotion on its skills and license pages. Versions, prices and license thresholds change. Check each vendor before you decide.


FAQ

What is the best product demo video maker for developers?+

For a film of your own UI that you will recut, product-film or HyperFrames. For React teams, Remotion. For a one-off, a screen recorder.

Can an AI agent make a demo video?+

Yes. A coding agent can write the HTML timeline, render the frames and cut the film. It cannot judge taste or sound.

Does product-film record my screen?+

No. It draws every frame from code, using your components or live screens answered with fictional data.

Is product-film free?+

It is MIT-licensed and uses no paid models by default. Footage and music you license are your own cost.

Which agents does it work with?+

The docs list Claude Code, Cursor, Codex, OpenCode, Hermes and Pi.

Does it work in ChatGPT or Claude on the web?+

Those apps can plan a film. They cannot render one without a local shell.

Is it only for Display users?+

No. The skill works on any product. Review pages publish to Display when you ask. Without an account, a preview lasts 30 days and you can claim it.

Publish your first artifact in 15 seconds.

Free tier. No credit card. One-time password auth for viewers on free, Google + Microsoft SSO on Pro (€49/month flat).

Get started free →See pricing