Share with your team and clients
Invite people by email and give each one a role.
product-film is an open-source agent skill. Your agent rebuilds your product's screens from your code and animates them on an HTML timeline.
The demo shows an agent publishing a doc to Display from a chat, then a teammate opening its URL, selecting Edit, changing a number on the page and saving v2, a colleague commenting on v2, the agent publishing v3 at the same URL and resolving the comment, and the doc being shared with someone outside the company.
Used by top teams at


Answer
product-film is an agent skill that makes short product films from your product's real interface. It works in Claude Code, Cursor, Codex, OpenCode, Hermes and Pi. The agent copies your components into one HTML page and animates them on a timeline. Playwright screenshots every frame. ffmpeg encodes the frames and cuts the film.
It does not record your screen, and it does not use a video model. The skill is free under the MIT license. Display made it for its own product films, then published the source. Version 0.2.0 was current on GitHub on 16 October 2026.
Ask your agent for a film in one sentence. For example: "Make a 30-second launch film for the new share dialog." In Claude Code, you can also type /product-film and the subject.
The agent copies your components from your production code, or captures screens from your running app with fictional data. One HTML page holds the whole film.
Playwright opens the page in a headless browser and screenshots each frame. The page draws each frame from the time value alone, so a render gives the same frames every time.
ffmpeg encodes the frames and joins the beats. The skill writes a master file, a web file, a review file and a poster.
The agent publishes a review page to Display. Each new cut becomes a new version of the same page. You comment on the page, and the agent answers each thread.
| Route | What it makes | Good for |
|---|---|---|
| A: with footage | Licensed live-action footage cut against product beats, with a moving camera | Website hero loops |
| B: product only | Product beats on a 3D plate, or a reel cut to the beat of a music track | Landing sections, launch teasers and launch reels |
| C: walkthrough | A pointer drives the product through one story, with captions at close range | Store-listing promos and feature launches |
| D: paper collage | A cut-paper cast tells a story over real product screenshots | Social cuts and explainers |
Each route has a working template with a fictional example product called Tidewell. The first render works before you change a file. You then replace the brand values, the components and the copy with your own.
Ask your agent to install the product-film skill from display-dev/product-film. The README on GitHub has the install command.
The machine where your agent runs needs:
A chat app with no local shell can read the skill and plan a film. It cannot render one.
Teams with a front end in code. The skill draws your components or captures your running app. If you have no UI code, it has nothing to draw.
Teams that recut often. A product change means a new render, not a new screen recording.
Teams that review in comments. Each cut gets a review page on Display. Your team comments on the page, and the agent answers.
It does not suit a one-off video that nobody will recut. Setup takes longer and needs more steps than a screen recorder.
| Tool | Approach | License and cost | Best for |
|---|---|---|---|
| product-film | HTML timeline, Playwright frames, ffmpeg. Built for product UI, with a review page on Display | MIT. Free | Films of your own product that you recut often |
| HyperFrames | Plain HTML compositions. Headless Chrome seeks each frame, then FFmpeg encodes. Installs as an agent skill | Apache 2.0. Needs Node 22 or later and FFmpeg | General HTML-to-video work for agents |
| Remotion agent skills | Video written as React components. Installs as an agent skill | Free for individuals and companies of up to 3 employees. Larger companies need a license, for example $25 a month per seat on the Creators plan | Teams that write React and want a large ecosystem |
| Screen recorder | Records your real screen | Many options and prices | A quick demo that you will not recut |
Pick HyperFrames if you want a general HTML-to-video engine for any subject. Pick Remotion if your team works in React. Pick product-film if the film is about your own product UI and your team reviews each cut. We made product-film, so weigh our view. *Checked 16 October 2026 on the HyperFrames GitHub page, the Remotion license page and the Remotion skills page. Versions, prices and license limits can change.*
The public docs show five frames from the example film of the kinetic walkthrough template. The film is about Tidewell, the fictional shared-docs product in the templates. Playwright screenshotted each frame from one HTML page. Nothing in it is a screen recording. See the frames in the docs.
Two guides use the skill:
The agent publishes one review page for each film. Each new cut is a new version at the same link. Your team opens the link with the Google or Microsoft account they already use and comments on the cut. The agent reads the comments and answers each thread.
Without a Display account, the first publish is a preview that stays for 30 days. You can claim it. To get notes from outside your company, invite people by email with a role, for example Commenter.
Display is the AI docs workspace that's open to all 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.
Invite people by email and give each one a role.
Each publish and each edit saves a version. The link stays the same.
Spaces and folders for each team and each client.
You and your agents search every doc you can open.
Each doc shows who opened it, and when.
Private betaInternal apps that get data from your sourcesConnectors for the tools your team uses
Add Display once. Then ask your agent to publish.
Ask your agent to install product-film from GitHub · Ask your agent for a short film of one feature · Review each cut on a Display page with your team
Yes. product-film is an open-source Claude Code video skill for product films. Other skills exist for general video work, for example HyperFrames and the Remotion agent skills.
Yes. Its README lists Claude Code, Cursor, Codex, OpenCode, Hermes and Pi.
Yes. It is under the MIT license and uses no paid models by default. Footage and music that you license are your own cost.
For product films, yes. Both render HTML to video with a headless browser and ffmpeg. HyperFrames is a general engine. product-film adds templates, camera and pointer rules, checks and a review loop for product UI.
It does a different job. Remotion writes video as React code and has a license for larger companies. product-film draws your product UI on an HTML timeline under the MIT license.
No. The skill works on any product. Review pages publish to Display. Without an account, a review page is a 30-day preview that you can claim.
Yes. The paper-collage route renders 16:9, 9:16 and 4:5 at once. Routes A and B make a 9:16 cut as a separate pass.
Yes. An Owner adds the domains of those services to the domain allowlist in Settings. Your published HTML pages can then get data from those domains and send data to them, for example from a form to a webhook. The other service must also accept the request. Display does not add a login or an API key, so keep secrets out of the page. The Business plan includes the domain allowlist.