How to Record a Product Demo Video (With Script Template)

To record a product demo, first decide which job the video has, because a muted landing-page loop, a launch video, a sales follow-up and an onboarding clip each need a different length. Then write a script around one outcome (60–90 seconds for a launch or homepage demo), seed a demo account with realistic data, turn notifications off, and record at 1080p or higher with a real microphone. In the edit, cut dead air, zoom in on every action and add captions for people watching on mute. Export an H.264 MP4 sized for where it will live.

Everything here works with any recorder, including the one built into your operating system. Where we name ZoomCap, the steps come from our own product; details about other tools come from their own sites, checked in September 2026, and we say so.

TL;DR

• Length follows the job: 10–30 seconds for a muted hero loop, 60–90 for a launch demo, 2–5 minutes for a sales follow-up, one task per onboarding clip.
• Structure a 60–90 second demo in five beats: hook, outcome, three steps, proof, call to action.
• Write the script before you record. The template below takes about 20 minutes to fill in.
• Prep beats gear: demo data, notifications off, a smaller window, a bigger cursor.
• Three edits change the result: cut dead air, zoom on the action, burn in captions.
• Export H.264 MP4. Product Hunt only takes YouTube links, and a landing-page loop needs muted and playsinline to autoplay on iPhone.

Who this is for

Founders and product managers recording a launch or homepage demo, salespeople recording a follow-up after a call, support and success teams building onboarding clips, and developers who shipped a feature and need a clip for the changelog. If you want a clickable, self-guided product tour rather than a video, skip to when an interactive demo is better.

How to record a product demo: the process in eight steps

1. Pick the job: hero loop, launch video, sales follow-up or onboarding clip. This sets the length and whether it has sound.
2. Choose one outcome the viewer should believe after watching. One, not five.
3. Write the script in two columns: what is on screen, what you say.
4. Prep the stage: demo account, clean desktop, notifications off, window sized for video.
5. Record at 1080p or higher, 30 or 60 fps, with a USB or headset mic. Redo fumbled steps as you go.
6. Edit: cut dead air, zoom on each action, add captions and, if there is no voice, a music bed.
7. Export an H.264 MP4 master, then a copy per destination.
8. Distribute: muted loop on the landing page, native uploads on social, a YouTube link for Product Hunt.

Match the demo to its job (and length)

A product demo is not one video. The muted loop in your landing-page hero, the 90-second launch video, the five-minute follow-up after a sales call and the 40-second help-centre clip have different viewers, different sound situations and different lengths. Decide which one you are making before you write a word, because most weak demos are trying to be all four at once.

How long should a product demo video be?

As short as its job allows: 10–30 seconds for a silent hero loop, 60–90 seconds for a launch or homepage demo, 2–5 minutes for a sales follow-up, and one task per onboarding clip. If a launch demo runs past two minutes, it is usually two videos. The number that matters more than total length is how fast the product appears: aim for the first useful frame inside five seconds.

The 60–90 second demo structure

A 60–90 second demo has five beats: a hook that names the problem, the outcome shown up front, three steps of the core workflow, one proof moment, and a call to action. The workflow gets most of the time. The intro gets almost none, and there is no logo sting.

Three steps is not a style rule. It is about as much as anyone holds from a video they did not plan to watch. If your product does ten things, the demo shows the one that sells it; the other nine get their own short clips. And show the result early. Viewers forgive a lot of how once they have seen the what.

A copy-paste demo script, with a worked example

Write the script in two columns, what is on screen and what you say, then read it aloud with a timer. If it takes longer than 90 seconds at a relaxed pace, cut words rather than talking faster. Here is the template:

PRODUCT DEMO SCRIPT: [Product], target [60-90] s

Viewer:      [who is watching, e.g. "agency owner chasing late invoices"]
One outcome: [the single thing they should believe after watching]
CTA:         [one action, e.g. "Start free at example.com"]

[0:00] HOOK
  Screen: [the pain, or the finished result]
  Say:    "[The problem, in the words your customers use.]"

[0:05] OUTCOME
  Screen: [end state of the workflow]
  Say:    "[Product] [does X] so you [benefit]."

[0:12] STEP 1: [setup]
  Screen: [action]            Zoom: [what to zoom on]
  Say:    "[What you're doing and why it matters.]"

[0:30] STEP 2: [the core action]
  Screen: [action]            Zoom: [what to zoom on]
  Say:    "[...]"

[0:45] STEP 3: [the result]
  Screen: [action]            Zoom: [what to zoom on]
  Say:    "[...]"

[1:00] PROOF
  Screen: [the moment it works]
  Say:    "[Before vs after, time saved, the number that changed.]"

[1:15] CTA
  Screen: [product name + URL]
  Say:    "[One next step.]"

Worked example: Quillcrest (a made-up invoicing tool)

Quillcrest is fictional. It chases unpaid invoices for freelancers. Here is the same template filled in for a 70-second launch video:

PRODUCT DEMO SCRIPT: Quillcrest, target 70 s

Viewer:      freelance designer with three overdue invoices
One outcome: Quillcrest chases late invoices so you don't have to
CTA:         "Try it free at quillcrest.example"

[0:00] HOOK
  Screen: inbox search for "invoice overdue", 14 results
  Say:    "If you've ever typed 'just following up on this invoice'
           three times in one week, this is for you."

[0:05] OUTCOME
  Screen: Quillcrest dashboard, three invoices flip from Overdue to Paid
  Say:    "Quillcrest sends the follow-ups for you, politely and on
           a schedule, and tells you when you've been paid."

[0:12] STEP 1: connect
  Screen: click Import, choose the invoicing app, 12 invoices appear
  Zoom:   the Import button, then the list
  Say:    "Connect the tool you already invoice from. Open invoices
           come in on their own."

[0:28] STEP 2: set the tone
  Screen: pick the "Friendly" schedule, edit one line of the email
  Zoom:   the schedule picker, then the email text
  Say:    "Pick how firm you want to be. Friendly nudges at 3, 7 and
           14 days, and every message is yours to edit."

[0:44] STEP 3: turn it on
  Screen: switch Auto-chase on for all overdue invoices
  Zoom:   the toggle
  Say:    "Switch it on once. That's the whole setup."

[0:52] PROOF
  Screen: activity feed: reminder sent Mon, opened Tue, paid Wed
  Say:    "Reminder on Monday, paid on Wednesday, and you didn't
           write a single email."

[1:02] CTA
  Screen: logo + quillcrest.example
  Say:    "Quillcrest. Try it free at quillcrest.example."

Notice what the voiceover never says: "now I'm going to click". The screen already shows the click. The voice explains why it matters. That one habit separates demos people finish from demos people scrub through.

The hero loop needs a shot list, not a script

A muted 10–30 second loop has no voiceover, so plan it as shots:

1. Open on the most recognisable screen of your product, never a login page.
2. Perform the one action that produces the core outcome.
3. Let the outcome land and hold it for about two seconds.
4. Return to the starting screen, so the loop restarts without a visible jump.

Prep checklist before you hit record

Most of what makes a demo look professional happens before recording: realistic demo data, a clean desktop, notifications off, a browser window sized for video, and a cursor people can actually see. Ten minutes of prep saves an hour of editing.

Desktop and browser

• Hide desktop icons and quit every app that is not in the demo.
• Use a separate browser profile for demos: no bookmarks bar, no extension icons, and no personal history in the address-bar autocomplete.
• Log in beforehand. Dismiss cookie banners, product tours, "what's new" modals and chat widgets.
• Close other tabs. The tab strip shows up in most recordings.

Demo data

• Seed a dedicated demo account with believable names, amounts and dates. "Test Test" and "asdf" read as unfinished.
• Never use real customer data, even blurred. Blur is easy to get wrong for a single frame.
• Pre-create the state you need, so you are not waiting for an import or a build on camera.
• Use plausible numbers: $4,280 outstanding looks real; $1,000,000 or $0 does not.

Notifications and privacy

• Turn on Do Not Disturb. On a Mac, click Control Center in the menu bar, then the Focus section (Apple's steps).
• Quit Slack, mail and messaging apps. A preview banner can leak a customer name.
• Close anything with secrets: .env files, terminals with tokens, cloud consoles, password-manager pop-ups.

Window size, resolution and cursor

• Do not record a large high-resolution display full-screen; the UI text ends up tiny in a phone-sized player. Record one window at roughly 1280×800 to 1440×900, or raise the browser zoom to 110–125%. We explain the maths in why screen recordings look bad.
• If your recorder captures the system cursor, make it bigger first. On a Mac that is the Pointer section of Accessibility → Display in System Settings (Apple's guide).
• ZoomCap's CLI hides the system cursor and redraws it, so on those recordings you can resize it (0.5–3×) and change its style after the fact.
• Rehearse once, then record a 10-second test and listen back to the mic level.

Recording settings

Record at 1080p or higher, at 30 fps (60 fps if you scroll a lot), with a USB or headset microphone close to your mouth. Capture one window rather than a whole high-resolution display. When you fumble a step, pause, redo it, and cut the mistake later instead of starting over.

With ZoomCap's paid plans, npx zoomcap record starts a recording from the terminal at 60 fps by default (--fps lowers it). On macOS 15 and later it captures system audio and your microphone; on Linux (X11) it records video only. On Windows, or if you would rather not open a terminal, the browser recorder captures a screen, window or tab and works best in Chrome or Edge. Our guide to recording your screen on a Mac covers the built-in options too.

One honest workflow note: ZoomCap edits one recording at a time. It does not combine separate takes or lay a separately recorded voiceover over the screen. If you prefer to record the screen silently and narrate afterwards, which gives cleaner audio for some people, finish in a general video editor.

The best way to record product demos: which recorder

The steps above matter more than the tool, but the tool decides how long the edit takes. We recommend ZoomCap, and we make it, so weigh this accordingly.

Why ZoomCap

The slow part of a demo is the edit, and ZoomCap does most of it for you. Record with npx zoomcap record on a Mac or Linux and every click and typing burst becomes a zoom you can re-aim or delete, under a redrawn cursor you can resize. In the same editor you add a background and padding, a webcam bubble, captions generated in your browser, and a music bed, then export an MP4 up to 4K or a GIF. On Windows, or without a terminal, the free browser recorder gives you that editor with zooms you place yourself. The recording is edited and encoded on your computer and never uploaded, which matters for unreleased features. It costs $29 once or $12.49 a month; over three years that is $295 less than Screen Studio's yearly plan. Its limits: no share links or view counts, no Windows CLI, no motion blur, and automatic zoom only on recordings made with the CLI.

Prices and features of the other tools below are from each vendor's site, checked September 2026; we haven't hands-on tested the paid Mac apps in this table.

If you need something ZoomCap doesn't do:

• If you need a hosted link with view notifications for sales follow-ups: Loom. Its free plan allows 25 videos per person, 5-minute limit, 720p according to its pricing page.
• If you need motion blur or iOS device recording on a Mac: Screen Studio, according to its site, at $29/mo or $108/yr ($9/mo billed yearly).
• If you need hosted demos with team editing: Tella, cloud-based, Pro $26/user/mo.
• If your budget is $0: OBS for capture (you edit elsewhere), or OpenScreen for free automatic zoom on macOS, Windows and Linux.

We go deeper in the best screen recorders for product demos.

The edits that matter

Four edits do most of the work: cut dead air, zoom in on each action, burn in captions, and add a quiet music bed when there is no voice. Transitions, animated titles and logo intros rarely help a demo and often hurt it.

1. Cut dead air. Loading spinners, typing corrections, "um, where was that setting". A useful rule: if nothing changes on screen for two seconds and nobody is talking, cut it. In ZoomCap you split and cut on the timeline. Its speed setting (1×, 1.5× or 2×) applies to the whole video, voice included, so for narrated demos cut the slow parts rather than speeding everything up.
2. Zoom in on the action. A full 1080p frame shown in a phone-sized player makes UI text unreadable. Zoom in when something happens and pull back when the viewer needs context. Our guide to zooming in on a screen recording covers the manual way; a recorder with automatic zoom does it from your clicks. ZoomCap's CLI tracks every click and typing burst, so zooms land where you clicked and you just re-aim, stretch or delete the ones you do not want. Browsers cannot see clicks in other apps, so in browser recordings expect to place most zooms by hand.
3. Captions for muted autoplay. Landing pages and social feeds start videos muted, so the captions carry the message. Burn them into the video so they show on every platform. ZoomCap generates captions in your browser with a Whisper model and burns them into the export; proofread product names, which speech models often mangle.
4. A music bed, low enough that it never competes with the voice. It matters most for voiceless loops and short clips. ZoomCap includes seven built-in background tracks.
5. Frame it, lightly. A background, some padding and rounded corners make a raw capture look like a product shot. Pick one style and reuse it on every video. In ZoomCap these are one click each, with style presets you can reuse (see ZoomCap's style options).

Skip: transitions between steps, animated logo intros, a text callout on every click, and stock whoosh sounds.

Voiceover, or captions and music?

For a launch or sales demo, use a voiceover, because it explains why something matters and the screen cannot. For a muted hero loop or a 20-second feature clip, short captions plus a music bed are enough. Either way, caption the voiceover, since most feeds and landing pages start video muted.

Export settings per destination

Export an H.264 MP4 at 1080p as your master, then make a copy for each destination: a short, silent, small MP4 for your landing page, a YouTube upload for Product Hunt, and native uploads for X and LinkedIn. GIFs are for READMEs and email, not landing pages: a muted, looping MP4 is usually much smaller than a GIF of the same clip, looks sharper, and autoplays when it is muted and marked playsinline. For bitrates and codecs, see our MP4 vs MOV vs WebM guide.

The landing-page embed that actually autoplays

<video autoplay muted loop playsinline
       poster="/demo-poster.jpg">
  <source src="/demo-loop.mp4" type="video/mp4">
</video>

Each attribute is there for a reason. Chrome always allows muted autoplay (Chrome's autoplay policy). Safari on iPhone autoplays only video that is muted or has no audio track, needs playsinline to play in the page instead of going fullscreen, and pauses autoplaying video when it scrolls out of view (WebKit's video policies). The poster image shows while the file loads. Next to the loop, add a visible "watch with sound" link to the full narrated demo.

Where to post it

Put the muted loop on your landing page, upload the narrated version natively to X and LinkedIn instead of posting a link, and use a YouTube link for Product Hunt, which does not take video uploads. Every copy should make sense with the sound off.

Landing page

The hero loop goes above the fold or directly under the headline; the full demo sits one click away. Never autoplay with sound: browsers will block it anyway, and visitors who do hear it will leave.

X and LinkedIn

Upload the file itself rather than a YouTube link, so it plays in the feed. The first frame is your thumbnail and your hook, so start on the product, not a logo. A 60–90 second demo fits comfortably inside the length limits both platforms document; LinkedIn, for example, accepts 3 seconds to 15 minutes and files up to 5 GB (LinkedIn's video specs). Square (1:1) takes up more of a phone feed than 16:9; ZoomCap exports 16:9, 9:16, 1:1 and 4:3, with a follow-cursor mode for vertical.

Product Hunt

Product Hunt's gallery supports YouTube links only. Upload ahead of launch, make sure the video is not private, and paste the full URL, because shortened links do not load. Gallery images are recommended at 1270×760 and the gallery needs at least two images before it shows. Thumbnail GIFs do not autoplay (they animate on hover) and must be under 3 MB. Product Hunt's own launch guide says about 53% of products that reached Product of the Day since 2021 included a video (Product Hunt's launch guide). So a video helps, but it is not required.

Sales follow-ups and onboarding

Host these somewhere you can replace the file without breaking the link. For sales, personalise the first ten seconds: name their company and the question they asked. For onboarding, embed each clip next to the written steps for the same task, because some users read and some watch.

Three real-world examples

A founder recording a launch video

A two-person team launching an invoicing tool fills in the script template in half an hour, seeds a demo account, and records the 70-second flow in one sitting, redoing step two twice. The edit is cutting two loading pauses, checking the auto-zooms, fixing the product name in the captions and adding a quiet music bed under the voice. They export a 1080p 16:9 master, a 1:1 copy for X and LinkedIn, and a 20-second silent loop cut from the middle for the homepage. The 16:9 version goes to YouTube for the Product Hunt gallery.

An account executive after a discovery call

The prospect asked how approvals work for a team of forty. The AE records three minutes with the webcam on, in a demo workspace renamed to the prospect's company, walking through exactly that. No music, no background, light trimming only. It goes out the same afternoon as a link. Speed beats polish here.

A support lead building onboarding clips

The five most common tickets become five clips, each 30–90 seconds and each one task, with captions and the same visual style. Each clip sits in the matching help article. When the settings page is redesigned, only the clip that shows it gets re-recorded.

Common mistakes

• Opening on a logo, a login screen or "Hi, I'm…". Viewers are gone before the product appears.
• Touring every feature. Nobody remembers feature seven. Show one outcome.
• Narrating clicks instead of outcomes. "Now I click Settings" tells the viewer nothing the screen does not.
• Recording a large display full-screen and publishing it to a phone-sized player without zooming.
• Fake-looking demo data, or real customer data. Both cost trust, the second one far more.
• No captions on a video that autoplays muted.
• Music louder than the voice.
• Speeding the whole video up to hide slow parts. The voice goes chipmunk. Cut instead.
• One video for every job, such as a three-minute walkthrough squeezed into the landing-page hero.
• Letting it go stale. Re-record when the UI in the video no longer matches what a new user sees, or the core pitch changes. An old UI creates a small moment of doubt right at signup. If you keep the script and the demo account, a re-record takes an hour instead of a day.

When a live demo or an interactive demo is better

Use a video when the viewer should watch, an interactive demo when they should click through at their own pace, and a live demo when the buyer has questions a recording cannot anticipate. Best for reach and autoplay: video. Best for self-serve evaluation: interactive demos. Best late in a complex sale: live.

Interactive demo tools turn a captured workflow into a click-through the viewer controls. Supademo adds tooltips, hotspots and branching and reports where viewers drop off; Arcade builds clickable demos and now AI-generated product videos too. Both list a free plan with a limited number of demos and paid team plans billed monthly or annually; we haven't price-checked them for this post, so check Arcade's pricing and Supademo's pricing before you buy; plans in this category change often. And if what you need for sales follow-ups is a hosted link that tells you who watched, you need a hosted tool such as Loom rather than an exported file. We drew that line in our Loom alternative for demos post.

When you don't need a video at all

A single setting, a pricing detail or an API change is faster to explain with a screenshot, a sentence or a code sample. A video is worth making when the value is in a sequence of actions or in watching something happen. If a GIF of three seconds says it, do not make a 90-second video. And if the demo is mostly a terminal, see our guide to terminal demo videos, because text-based recorders sometimes beat video there.

Our recommendation

Make the 60–90 second launch demo first, from the script template, in a seeded demo account. Then cut everything else from that one recording: the silent hero loop from the middle, a square copy for social, the YouTube upload for Product Hunt. Record once, export several times. Re-record when the UI changes, and not before.

If the editing is the part you keep putting off, that is the part we built ZoomCap for. Record with npx zoomcap record and it zooms where you clicked and redraws a cursor you can resize; record in the browser and you place the zooms yourself. Either way it generates captions on your machine and exports an MP4 or GIF locally. It does not host your video, count views or take comments: you export the file and put it on YouTube, your site or a post yourself. The free plan (browser recorder and editor) gives you 2 exports a month with a watermark; Pro ($12.49 a month) and Lifetime ($29 once) add the terminal recorder and remove the watermark (pricing, as of September 2026). ZoomCap never uploads your recordings to us (how the data flows), payments go through Dodo Payments, and paid plans have a 14-day refund if it doesn't work for you and we can't fix it.

Pick something else only if the demo is a sales follow-up that needs a hosted link and view notifications, you need motion blur or iOS device recording, or you want automatic zoom on Windows (our CLI doesn't run there yet). Setup details are in the docs.

Frequently asked questions

Recording a bug instead of a demo? Our guide to recording a bug report video covers what developers need to see, with a template.

Record your demo now

Record your demo free in the browser, with nothing to install, and try the zooms, captions and background on your own product. When you want automatic zoom from your clicks and typing, no watermark and unlimited exports, it's $29 once on the pricing page.