How to Make a Product Demo Video: Length, Structure, Script and Formats

To make a product demo video, pick one job your product does well and show it in 30 to 60 seconds: a hook, the problem, two or three key moments in the UI, the result and a call to action. Capture clean screens, add camera moves, captions and music that follow the cuts, then export MP4 in 16:9 and 9:16, plus a short GIF. That covers launches, landing pages, social posts and READMEs.

The rest of this guide walks through that process, with the numbers behind each choice.

#How long should a product demo video be?

For most launch and marketing uses, under a minute. Wistia's video data shows that videos under a minute average a 52% engagement rate, which means viewers watch about half of them. Longer videos can work, but only if the viewer already wants the detail.

If your draft runs long, cut a feature. Don't speed the footage up until it's unreadable.

#What structure works for a demo video?

Almost every demo works with the same five beats. The timing below is for a 30-second cut; scale it for longer ones.

1. Hook (0–3 s). The outcome, not the logo. "Find out why customers churn before they cancel."
2. Problem (3–8 s). One line the viewer recognises from their own work.
3. Key moments (8–24 s). Two or three screens, each with one callout. Each moment answers "what do I click and what happens?"
4. Result (24–27 s). The finished state: the report, the shipped page, the number that went up.
5. Call to action (27–30 s). One action and a URL. "Start free at example.com."

Feature tours fail because every screen gets equal weight, so nothing sticks. A demo is a story about one job.

#How do you write a product demo video script?

Write the script before you capture anything. It decides which screens you need.

Plan about two words per second of narration. A 30-second video holds roughly 60 words, and that is less than it sounds. Here is a template to fill in:

HOOK:    [Outcome in under 8 words]
PROBLEM: [The pain, in the viewer's words]
STEP 1:  [Action] → [what they see]
STEP 2:  [Action] → [what they see]
STEP 3:  [Action] → [what they see] (optional)
RESULT:  [The end state, with a concrete detail]
CTA:     [One verb] at [URL]

Read it out loud with a timer. If you run out of breath or time, cut a step. On-screen callouts should be shorter than the narration: three to five words, pointing at the thing being described.

#Should you use screenshots or a screen recording?

Both work. They suit different videos.

• Screen recording is best when the motion itself is the point: drag and drop, a live preview updating, an animation in your UI. The cost is retakes. Every stray cursor movement, loading spinner and typo is in the footage.
• Screenshots are best when the result matters more than the clicks. You control every frame, use clean demo data, and add motion afterwards with camera moves and zooms. For launch videos, screenshots are usually the better starting point.

Either way, prepare the product first: realistic but fake data, a clean browser profile, notifications off, and a window size that matches your export (1920x1080 for 16:9).

#How do you make a product demo video, step by step?

1. Pick the one job. Write it as a sentence: "Pulse shows you which accounts are about to churn."
2. Write the script using the template above and time it.
3. List the screens each line needs. Usually 3–6.
4. Capture screenshots or a short recording of each screen at full resolution.
5. Add motion. Slow camera moves into the area that matters, a zoom on the key element, a callout for each step. Motion should point at something. If it doesn't, it's decoration.
6. Add music and narration. Pick the track first, then time the cuts to it (more on that below). Add an AI or recorded voiceover if the video will play with sound.
7. Add captions. Burn them in for social, and keep an SRT or VTT file for YouTube and LinkedIn uploads.
8. End on the CTA and hold it for 2–3 seconds so people can read the URL.
9. Export each format you need (see below) and watch every one on a phone before posting.

Steps 5 to 8 are where most of the time goes in a traditional editor. This is the part we built Lumora for: you upload screenshots or a recording, pick a look, and it renders the camera moves, callouts, captions and end card, with cuts snapped to the music's beat.

#What music and pacing should a demo video use?

Music sets the pace more than the edit does. A few rules that hold up:

• Choose the track before you cut. Then put scene changes and zooms on the beat. Cuts that land on the beat feel intentional even when the viewer can't say why.
• Put the reveal on the drop. If the track has a build and a drop, the drop is where the result (beat 4) goes.
• Keep music under the voice. If there is narration, music should sit well below it.
• Use licensed audio. Your own track, a library you pay for, or tracks bundled with your tool. Platforms can mute or block videos with unlicensed music.

For pacing, hold each key screen long enough to read its callout twice. That's around 3–5 seconds per screen in a 30-second video.

#Which formats and sizes should you export?

Make one master edit, then export per channel. These cover almost every launch:

YouTube recommends MP4 with H.264 and AAC audio, around 8 Mbps for 1080p at 30 fps. Every other platform's limits are in our demo video sizes and specs cheat sheet, with links to each platform's own docs.

When you reframe 16:9 into 9:16, don't just crop the middle. Move the camera to follow the element being described, or the callout ends up off screen.

#Where should you publish a product demo video?

• Your landing page, above the fold: a muted, looping 10–20 second cut, with the full version one click away.
• Product Hunt: video is a YouTube link plus GIFs in the gallery. See how to make a Product Hunt launch video.
• GitHub README: a short GIF near the top.
• X and LinkedIn: native uploads with burned-in captions, not YouTube links.
• Changelog and release notes: a 10–15 second clip per feature. If you ship often, you can generate changelog videos from Claude Code or Codex.
• Sales and onboarding emails: a thumbnail that links to a share page, so you can see who watched.

#What are the common mistakes?

• Starting with the logo. The first three seconds decide whether anyone stays. Lead with the outcome.
• Showing everything. Three features shown well beat ten shown fast.
• Unreadable UI. If text is smaller than a caption, zoom in or crop.
• No captions. Assume people watch in a feed with the sound off.
• One export for every channel. A 16:9 video in a vertical feed is a small strip with black bars.

If you are looking for a tool to do the editing part, our roundup of Screen Studio alternatives for Windows and the web compares recorders and editors fairly, including ours.