How to make a product demo video that people watch

Most product demos aren't bad because of the camera or the software. They lose people because they start slowly, show too much and leave the viewer to work out why any of it matters. The good news is that the fixes are mostly about planning. This guide walks through the process from first idea to published video: what to show, how long to make it, how to script and record it, and how to edit it so people keep watching.

Start with one viewer and one outcome

Before you open a recorder, write down two things:

Who is watching. A first-time visitor on your homepage, a trial user stuck on setup, or a buyer comparing you with a competitor. Each needs a different video.
What they should be able to do or believe afterwards. "They understand that importing a CSV takes ten seconds." "They know where the export button is." One outcome per video.

If you can't write the outcome in one sentence, you probably have two videos. That's fine. Two short, focused videos beat one long one that tries to do everything.

How long should it be?

There is no magic number, but the data points the same way: shorter holds attention better.

Wistia analysed over 13 million videos uploaded to its platform and found that videos under a minute average a 52% engagement rate. Engagement "naturally declines after the five-minute mark".
An earlier Wistia study of audience retention looked at the first 2% of a video. On average, 4.9% of viewers left in that opening stretch for videos of 1 to 2 minutes, against 17.3% for videos of 5 to 10 minutes.

Use this as a rough guide, not a rule:

Video type	Where it lives	Sensible length
Teaser or social clip	X, LinkedIn, Product Hunt	15 to 45 seconds
Homepage overview	Landing page hero	60 to 90 seconds
Feature walkthrough	Docs, changelog, onboarding email	1 to 3 minutes
Full tutorial	YouTube, help center	As long as the task needs, split into chapters

If a walkthrough runs past three minutes, check whether it really is one task. Long videos are fine when people need them, like a setup tutorial someone follows step by step. They aren't fine when the length comes from hesitation and detours.

Structure: problem, action, result

A simple structure works for almost every demo:

The problem (5 to 10 seconds). Name the pain in the viewer's words. "Turning a spreadsheet into an invoice usually takes twenty minutes of copy and paste."
The action (most of the video). Show the shortest real path through your product. One flow, start to finish, no tour of the settings page.
The result (5 to 10 seconds). Show the finished thing: the sent invoice, the published page, the dashboard with data in it. End on the result, not on a logo.
The next step (optional, a few seconds). One call to action that matches where the video lives: "Try it free", "Read the docs", "Book a call".

Skip the long intro. Viewers don't need your company history or a spinning logo before they see the product. Get to the screen fast, then explain as you go.

Write a script, even a short one

Unscripted demos tend to wander. A script doesn't have to be formal. A two-column table is enough:

What's on screen	What you say
Empty dashboard	"Here's a new workspace. Let's get some data in."
Click Import, choose CSV	"Click Import, pick your file..."
Table fills in	"...and every row is already mapped to the right field."

Tips that make scripts easier to record:

Write for speaking. Short sentences. Read it aloud once; anything you trip over, rewrite.
Describe the why, not the click. The viewer can see you click "Import". Tell them why it matters.
Cut every "simply" and "just". If it were simple, you wouldn't need a video.
Record voice separately if it helps. Many people find it easier to record the screen first and narrate afterwards, or the other way round. Use whichever gives you a calmer result.

Prepare the recording setup

Most of the difference between an amateur and a professional-looking demo happens before you hit record.

Clean the stage

Use a demo account with realistic, believable data. Empty states and "test test 123" make products look unfinished.
Hide anything personal or sensitive: real customer names, emails, API keys, private bookmarks.
Close unrelated apps, turn on Do Not Disturb and hide desktop clutter.
Log in beforehand so the video doesn't start with a password field.

Get the size right

Record at a window size that will be readable after export. A huge 5K display shrunk into a 1080p video makes text tiny. Either record a smaller window or plan to zoom in.
Increase the browser or app zoom level a little if your UI uses small text.
Pick one aspect ratio up front. 16:9 for websites and YouTube; consider square or vertical for social feeds.

Sound

Use an external or headset microphone if you have one. Built-in laptop mics pick up room echo and keyboard noise.
Record in a small, soft room. Curtains and a sofa help more than expensive gear.
Do a 10-second test recording and listen back with headphones before the real take.

Record in short takes

You don't need a perfect single take. Record each step of the script as its own short take, then cut them together. If you fumble, pause, wait a second, and repeat the sentence. The pause gives you a clean edit point.

Move the mouse deliberately. Fast, jittery cursor movement is the most common thing that makes demos hard to follow. Move to the target, pause briefly, click. If your recorder captures the cursor separately and smooths it afterwards, it helps a lot, but calm movement during recording still gives the best result.

Zoom where the action is

On a full-screen recording, the button you click may be a few pixels wide in the final video, especially on mobile. Zooming in on the area of interest solves this.

Zoom in when the viewer needs to read or see a detail: a form field, a menu item, a small chart label.
Zoom out when context matters: switching pages, showing the overall layout, or before a big change on screen.
Don't zoom on every click. Constant zooming is tiring. Group a few nearby clicks into one zoom and hold it.
Keep motion smooth. Gentle, eased zooms feel like a camera move. Sudden jumps feel like a glitch.

Several recorders can add zooms automatically from your clicks and let you adjust them afterwards. We explain how that works in Auto zoom screen recording explained.

Edit for pace

Editing is where a 4-minute raw recording becomes a 90-second video. Go through it in this order:

Cut dead time. Loading spinners, typing long text, waiting for an upload. Cut them or speed them up.
Cut repetition. If you show the same action twice, keep the better one.
Tighten the start. The first few seconds matter most, as the retention numbers above show. Start on the problem or the first meaningful screen.
Speed up the boring middle. A 2x speed-up on a routine step keeps the flow without hiding it.
Watch it once at normal speed as a stranger would. Anywhere you feel the urge to skip, so will the viewer.

Background music is optional. If you use it, keep it low under the voice and make sure you have the right to use the track.

Add captions

Captions help viewers who are deaf or hard of hearing, and people who process written information better than audio. In practice they also help anyone watching with the sound off in an office or on a train, and many social feeds autoplay without sound.

Generate captions automatically, then correct product names and technical terms by hand. Speech recognition often gets brand names wrong.
Keep lines short so they don't cover the part of the screen you're showing.
If you upload to YouTube or a video host, upload a caption file rather than burning captions into the video, so viewers can turn them on or off.

Make a thumbnail

The thumbnail decides whether someone presses play when the video doesn't autoplay.

Show the result or the most interesting screen, not your logo.
Add a few words of large text if the screen alone isn't clear: "CSV to invoice in 10 s".
For YouTube, follow its thumbnail guidelines: a 16:9 image, at least 640 pixels wide, as JPG or PNG. YouTube recommends 3840 x 2160 for videos.
Check how it looks small. Most people see thumbnails at a fraction of full size.

Where to post it

Match each version to where it will be watched:

Your homepage or landing page: the short overview, muted autoplay with captions or a clear play button. Keep the file small so the page stays fast.
Docs and help center: feature walkthroughs next to the written steps they illustrate.
Onboarding emails and in-app tips: a short clip that shows the next step the user should take.
YouTube: full tutorials, with chapters and a searchable title that matches how people describe the problem.
Social (X, LinkedIn, Product Hunt): the teaser, ideally native upload rather than a link, with captions on.
Sales: a version tailored to the questions buyers ask, which reps can send after a call.

Record once with this in mind and you can cut several versions from the same raw footage.

A quick checklist

One viewer, one outcome, written down.
Script in two columns: screen and voice.
Demo account with real-looking data, notifications off.
Readable window size, chosen aspect ratio.
Short takes, calm mouse movement.
Zooms on details, not on every click.
Dead time cut, opening tightened.
Captions checked by hand.
Thumbnail that shows the result.
A version for each place it will be posted.

If you're on a Mac and want auto zoom, a smooth cursor and a clean background without a subscription, you can download Dolly and try it for free. Any of the tools in our comparison will also do the job; the steps above matter more than the tool.