How to make a product demo video in 7 steps

Before you record: decide who the demo is for

Write one sentence before anything else: "After watching this, a [viewer] can [do one thing]." A trial user who signed up yesterday needs a different video from a buyer comparing you with two competitors, and both need something different from an existing customer hearing about a new feature.

That sentence settles most of the arguments that come later. Should the settings page be in it? Only if the viewer needs settings to do the one thing. Should the founder appear on camera? Only if this viewer cares who built it. When a team can't agree on the sentence, it usually means they're trying to make two videos at once.

• Name the viewer by situation, not by persona: "an ops lead who has just imported their first CSV" beats "mid-market buyer".
• Pick the job they came for, then the shortest path through your product that gets it done.
• Decide where it will play (landing page, Product Hunt, a sales email, the help center), because that sets the length and the shape of the frame.

How to make a product demo video, step by step

Here is the full sequence. The table after it shows roughly where the time goes, so you can see why skipping the script is a false saving.

1. Set the goal: one viewer, one job, one place it will be watched.
2. Write the script as two columns, what the viewer hears and what they see, one row per screen. Read it out loud and time it.
3. Prepare the product: a clean account, realistic sample data, no personal or customer details, notifications off, a consistent window size.
4. Capture the screens. Record the screen in short takes, one per script row, or build the screens from your code so they can be changed later.
5. Add the voice: your own recording, a hired voice actor or an AI voice. Then time every cut to the narration rather than the other way round.
6. Finish it: captions, zooms on the click that matters, your logo and one call to action at the end.
7. Export and publish: a 16:9 master plus 9:16 and 1:1 cuts, a thumbnail, and a title and description written for where it lives.

Writing the script and preparing sample data

A demo script is short. At a normal speaking pace of about 140 to 160 words a minute, a 75-second demo has room for roughly 180 to 200 words of narration, and a lot of that should be pauses while the screen does the talking. If your draft is 400 words, you have two videos.

Open with the problem in the viewer's words, show the task being done, and end on the result. The product demo script template lays this out scene by scene if you want a starting point.

Recording the screen vs building it from code

Step four is where the methods split. A screen recording captures exactly what is on your monitor. It's quick for a one-off, and tools like Loom or the built-in recorders on Mac and Windows do the job (our guide to screen recording with audio covers the settings). The cost shows up later: when a button moves or a label changes, the recording is wrong and you record it again.

The other route is to build the screens rather than film them. DemoVexa reads the app's code, recreates the real screens as animation and times each scene to the voiceover, so changing a label or a sentence of the script means rebuilding a scene, not reshooting the whole video. It suits products that ship often. It's overkill for a two-minute internal clip you'll never reuse. The comparison of demo video tools by starting point lays out where each approach wins.

Voiceover, captions and the final cut

Record or generate the narration before you lock the picture. Then cut each scene to the sentence that describes it. Viewers forgive a plain screen far more readily than a voice that talks about a button that hasn't appeared yet.

Add captions to every version. Plenty of people watch social video with the sound off, and captions for prerecorded video are a Level A requirement in the W3C's WCAG 2.2, so anything that plays on your own site should have them anyway. Our guide on how to add subtitles to a video covers burned-in captions versus SRT and VTT files.

• Zoom on the one click or field that matters in each scene, not on every click.
• Keep music under the voice and drop it entirely in tutorials.
• End with one call to action. "Start a free trial" or "Book a call", not both.

Length, formats and where to publish

Shorter usually wins for a first look. Wistia's analysis of millions of hosted videos found that viewers watch about half of a typical video under a minute long, and that people tend to drop off around the middle of longer ones, so put the key moment early (Wistia, 2025). Tutorials can run longer because the viewer arrived wanting the answer. We cover lengths by video type in how long should a demo video be.

Export a 1920×1080 (16:9) master in H.264 MP4, then make native 1080×1920 (9:16) and 1080×1080 (1:1) versions for Reels, Shorts, TikTok and the LinkedIn feed. Recompose those rather than cropping the master, or the sidebar and half your buttons fall off the edge. The Instagram Reels resizing guide explains the safe zones.

Then put the video where the decision happens: above the fold on the landing page, in the first onboarding email, in the help article for that task. A demo nobody finds is the most common failure of all, and no amount of editing fixes it.

Questions