Make a Product Demo Video from Screenshots and a Story
Plan a factual 20–90 second product story, edit scenes and export actual MP4s. Keep screenshots, captions, canvas formats and audio aligned with the reviewed project.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Use Product Demo Studio to plan a film from my approved product facts and permitted screenshots. Ask for audience, CTA, length, formats and audio. Read the installed release instructions and propose 3–12 scenes for a 20–90 second story. Review the editor, render into a fresh folder, then watch every MP4 and verify captions, crops and final CTA. Do not treat browser edits as a new video export.
How do I go from a product brief to a video?
Product Demo Studio v1.3.0 includes a local scene editor and an MP4 exporter for landscape, portrait and square. Start with approved product facts, permitted screenshots and a clear next action. This workflow creates authored motion; it does not record a live website or generate narration.
Should I record a screen, animate screenshots or generate footage?
| Method | What it can show | What you still need |
|---|---|---|
| Live screen recording | The actions actually performed in the captured interface | A recorder, a reviewed task and private information removed; Product Demo Studio is not a recorder |
| Screenshot-based motion | Reviewed product screens arranged into a launch story | Permitted screenshots and factual copy; render again after project edits |
| Generative footage | Illustrative scenes that must be labeled and reviewed | A separate generation tool, its access and usage costs; not supplied by this package |
Prepare the story and permitted assets
- Define the audience, final CTA, duration, required formats and audio mode. Plan 3–12 scenes over 20–90 seconds.
- Read references/art-direction.md and references/input.md. Keep permitted image and audio assets inside the input folder, with private information removed.
- Use real screenshots for product evidence and label illustrative diagrams. Never borrow fictional practice metrics as product claims.
Use complementary shots rather than repeated title cards
An illustrative six-shot sequence can introduce a problem, reveal the product, focus on one real detail, explain a workflow, compare documented choices and end with the next action. Pick shot types that support the facts. Inspect screenshot crops in all requested formats; a readable landscape frame may fail in portrait.
Review the editor, then render a new delivery
The installed release requires Python 3.10+, its requirements, local Chromium and FFmpeg. Follow SKILL.md for setup. From the package folder, the following command renders the fictional launch input. For your own film, save edited-project.json beside the editor's assets directory and use that file as the new input.
Read this release’s setup before running the example
Confirm installation and invocation in your host
.venv/bin/python scripts/build-film.py --input examples/launch.json --output ./practice-film --renderWatch each exported MP4 all the way through
- Inspect every scene, transition, crop, text line and final CTA. Compare SRT/VTT captions and storyboard.csv with the approved facts.
- Check duration, aspect ratio, contact sheets, render evidence and manifest hashes; none replaces watching the actual video.
- Listen to the export. Preview is silent; pulse audio is locally authored, and supplied audio must be a permitted local PCM WAV.
Inspect the current example output → — Compare the visible result with the exported files and checks described in this section.
Why did my edits not change the MP4?
Browser edits change the project, not a previously encoded video. Download the reviewed JSON, preserve its assets and rerun the builder into a fresh output folder. Proportional retiming changes timings, not copy; if shorter scenes become unreadable, reauthor the sequence rather than forcing a duration.
Keep video and launch copy aligned — Use the same approved product facts and real CTA destination.