Product Demo Video
A demo video shows one user achieving one outcome, in a clean environment, at a pace a newcomer can follow.
When to Use
- Announcing a feature or release
- Onboarding or help-centre walkthroughs
- Landing-page hero loops and social clips of the product
- Turning a manual QA flow into a repeatable, re-recordable demo
When NOT to Use
- Pure motion-graphics explainers with no product UI: use
video-production-pipeline
- Bug reproduction videos for engineers: record raw, no editing needed
Workflow
Step 1: Define the Story
Write the outcome as one sentence: "A new user connects Slack and gets their first alert." Then list the minimum clicks to get there. Cut every step that is not on that path (settings tours, alternative routes, edge cases).
Plan the length from the shot list, and split long flows into a series rather than one long video.
Step 2: Prepare a Clean, Safe Demo Environment
- Use seeded demo data. Never record production customer data, real emails, API keys, or internal URLs.
- Use a dedicated demo account with a neutral name and avatar.
- Hide notifications and personal bookmarks; close unrelated tabs and apps.
- Fix the window size to the target resolution (for example 1920×1080) and set browser zoom so text is legible when scaled down.
- Set the UI to a known state (light or dark theme, language, feature flags) and document it, so the demo can be re-recorded after the next UI change.
- Disable animations or loaders that make timing unpredictable, if the app has a setting for it.
Step 3: Record
Pick the recording method by how often the demo will be re-shot.
| Method |
Use when |
Notes |
| macOS Screenshot toolbar (Shift-Command-5) |
One-off, quick recordings on a Mac |
Record the entire screen or a selected portion; saves a .mov |
| OBS Studio |
Cross-platform, multiple sources, webcam overlay |
Free and open source; configure output resolution and frame rate to match the edit |
Playwright recordVideo |
The demo should be reproducible and re-recorded after UI changes |
Scripted, deterministic clicks; no cursor jitter |
Scripted browser recording with Playwright:
import { chromium } from "playwright";
const browser = await chromium.launch();
const context = await browser.newContext({
viewport: { width: 1920, height: 1080 },
recordVideo: { dir: "recordings/", size: { width: 1920, height: 1080 } },
});
const page = await context.newPage();
await page.goto("https://demo.example.com/login");
await page.getByLabel("Email").fill("demo@example.com");
await page.getByRole("button", { name: "Sign in" }).click();
await page.waitForTimeout(800); // deliberate pause so the viewer can read the screen
await page.getByRole("link", { name: "Integrations" }).click();
const videoPath = await page.video()?.path(); // available after the page/context closes
await context.close(); // must await close, or the video is not saved
await browser.close();
console.log(videoPath);
Notes from the Playwright docs: if size is not set, the video is scaled down to fit 800×800, so set it explicitly and match it to the viewport. Re-encode the recording to your edit format (for example H.264 MP4) before editing. Add deliberate pauses: real users need time to see what changed.
Record audio (VO) separately from the screen. It is easier to re-record one line than a whole take.
Step 4: Edit the Recording
Rough cut with FFmpeg (recipes in ffmpeg-post-production):
- Trim dead time at the start and end, and any loading waits (cut, or speed up visibly).
- Join takes with the concat demuxer, re-encoding if takes differ.
- Lay VO over the cut, then normalize loudness.
Pacing: hold on each new screen long enough for a first-time viewer to find what changed. If the VO and the UI disagree, re-time the video to the VO.
Step 5: Add Motion Overlays
Import the edited recording into a composition (Remotion or HyperFrames) for overlays. Use the official framework skill for the code; the design rules are:
| Overlay |
Purpose |
Rule |
| Zoom / punch-in |
Make small UI readable |
Zoom to the element being used; ease in, hold, ease out. One zoom per action |
| Callout / highlight |
Point at the control |
Appears just before the click; disappears after |
| Cursor emphasis |
Track the pointer |
Subtle ring or enlarged cursor; no trails |
| Title card |
Name the feature |
Short, held still, inside safe areas |
| Step labels |
Orient in multi-step flows |
"1 / 3" style counters only if there are real steps |
| Captions |
Sound-off viewing, accessibility |
See captions-and-transcription |
Apply motion-design-principles: one focal point at a time, ease-out entrances, no animation while text is being read, no flashing.
For vertical cuts, do not centre-crop the 16:9 recording. Re-frame around the active UI region per shot, or record a second take at a mobile viewport.
Step 6: Review
Scrub frame by frame around login screens, settings pages, and browser address bars. Sensitive data usually leaks there.
Best Practices
- One outcome per video; split long flows into a series
- Record in a seeded demo environment, never production
- Script the recording (Playwright) when the UI will change and the demo must be re-shot
- Record VO separately and edit picture to the VO
- Zoom to the element in use instead of shipping unreadable full-screen UI
- Re-frame for vertical deliberately; do not auto-crop
- Review every frame for leaked data before publishing
References
1---2name: product-demo-video3description: |4 Workflow for product demo and feature walkthrough videos: preparing a clean demo environment, recording the screen (manually or with scripted Playwright browser recordings), editing the recording, and adding motion overlays such as zooms, callouts, titles, and captions.5 Use this skill when the user wants a product demo, feature announcement video, onboarding walkthrough, changelog video, or a polished screen recording.6 Activate when: product demo, demo video, screen recording, walkthrough video, feature video, changelog video, onboarding video, record my app, Playwright video, recordVideo, zoom in on UI, callouts, cursor highlight.7metadata:8 source: https://skillmd.com/skills/latestaiagents/product-demo-video9---1011# Product Demo Video1213**A demo video shows one user achieving one outcome, in a clean environment, at a pace a newcomer can follow.**1415## When to Use1617- Announcing a feature or release18- Onboarding or help-centre walkthroughs19- Landing-page hero loops and social clips of the product20- Turning a manual QA flow into a repeatable, re-recordable demo2122## When NOT to Use2324- Pure motion-graphics explainers with no product UI: use `video-production-pipeline`25- Bug reproduction videos for engineers: record raw, no editing needed2627## Workflow2829### Step 1: Define the Story3031Write the outcome as one sentence: "A new user connects Slack and gets their first alert." Then list the minimum clicks to get there. Cut every step that is not on that path (settings tours, alternative routes, edge cases).3233Plan the length from the shot list, and split long flows into a series rather than one long video.3435### Step 2: Prepare a Clean, Safe Demo Environment3637- **Use seeded demo data.** Never record production customer data, real emails, API keys, or internal URLs.38- Use a dedicated demo account with a neutral name and avatar.39- Hide notifications and personal bookmarks; close unrelated tabs and apps.40- Fix the window size to the target resolution (for example 1920×1080) and set browser zoom so text is legible when scaled down.41- Set the UI to a known state (light or dark theme, language, feature flags) and document it, so the demo can be re-recorded after the next UI change.42- Disable animations or loaders that make timing unpredictable, if the app has a setting for it.4344### Step 3: Record4546Pick the recording method by how often the demo will be re-shot.4748| Method | Use when | Notes |49|--------|----------|-------|50| macOS Screenshot toolbar (Shift-Command-5) | One-off, quick recordings on a Mac | Record the entire screen or a selected portion; saves a `.mov` |51| OBS Studio | Cross-platform, multiple sources, webcam overlay | Free and open source; configure output resolution and frame rate to match the edit |52| Playwright `recordVideo` | The demo should be reproducible and re-recorded after UI changes | Scripted, deterministic clicks; no cursor jitter |5354Scripted browser recording with Playwright:5556```ts57import { chromium } from "playwright";5859const browser = await chromium.launch();60const context = await browser.newContext({61 viewport: { width: 1920, height: 1080 },62 recordVideo: { dir: "recordings/", size: { width: 1920, height: 1080 } },63});64const page = await context.newPage();6566await page.goto("https://demo.example.com/login");67await page.getByLabel("Email").fill("demo@example.com");68await page.getByRole("button", { name: "Sign in" }).click();69await page.waitForTimeout(800); // deliberate pause so the viewer can read the screen70await page.getByRole("link", { name: "Integrations" }).click();7172const videoPath = await page.video()?.path(); // available after the page/context closes73await context.close(); // must await close, or the video is not saved74await browser.close();75console.log(videoPath);76```7778Notes from the Playwright docs: if `size` is not set, the video is scaled down to fit 800×800, so set it explicitly and match it to the viewport. Re-encode the recording to your edit format (for example H.264 MP4) before editing. Add deliberate pauses: real users need time to see what changed.7980Record audio (VO) separately from the screen. It is easier to re-record one line than a whole take.8182### Step 4: Edit the Recording8384Rough cut with FFmpeg (recipes in `ffmpeg-post-production`):85861. Trim dead time at the start and end, and any loading waits (cut, or speed up visibly).872. Join takes with the concat demuxer, re-encoding if takes differ.883. Lay VO over the cut, then normalize loudness.8990Pacing: hold on each new screen long enough for a first-time viewer to find what changed. If the VO and the UI disagree, re-time the video to the VO.9192### Step 5: Add Motion Overlays9394Import the edited recording into a composition (Remotion or HyperFrames) for overlays. Use the official framework skill for the code; the design rules are:9596| Overlay | Purpose | Rule |97|---------|---------|------|98| Zoom / punch-in | Make small UI readable | Zoom to the element being used; ease in, hold, ease out. One zoom per action |99| Callout / highlight | Point at the control | Appears just before the click; disappears after |100| Cursor emphasis | Track the pointer | Subtle ring or enlarged cursor; no trails |101| Title card | Name the feature | Short, held still, inside safe areas |102| Step labels | Orient in multi-step flows | "1 / 3" style counters only if there are real steps |103| Captions | Sound-off viewing, accessibility | See `captions-and-transcription` |104105Apply `motion-design-principles`: one focal point at a time, ease-out entrances, no animation while text is being read, no flashing.106107For vertical cuts, do not centre-crop the 16:9 recording. Re-frame around the active UI region per shot, or record a second take at a mobile viewport.108109### Step 6: Review110111- [ ] No real customer data, secrets, internal URLs, or personal notifications visible in any frame112- [ ] The outcome sentence from Step 1 is achieved on screen113- [ ] Every click is visible and explained (VO, caption, or callout)114- [ ] UI text legible on a phone for vertical cuts115- [ ] Captions corrected and attached116- [ ] Demo environment state documented, so the video can be re-shot117118Scrub frame by frame around login screens, settings pages, and browser address bars. Sensitive data usually leaks there.119120## Best Practices1211221. One outcome per video; split long flows into a series1232. Record in a seeded demo environment, never production1243. Script the recording (Playwright) when the UI will change and the demo must be re-shot1254. Record VO separately and edit picture to the VO1265. Zoom to the element in use instead of shipping unreadable full-screen UI1276. Re-frame for vertical deliberately; do not auto-crop1287. Review every frame for leaked data before publishing129130## References131132- Playwright videos: https://playwright.dev/docs/videos133- Playwright `browser.newContext` `recordVideo` options: https://playwright.dev/docs/api/class-browser134- Apple Support, take a screenshot or screen recording on Mac: https://support.apple.com/guide/mac-help/take-a-screenshot-or-screen-recording-mh26782/mac135- OBS Studio: https://obsproject.com/136- Remotion agent skills: https://github.com/remotion-dev/skills137- HyperFrames: https://github.com/heygen-com/hyperframes