MotionShineShort answer: pick one viewer and one job they want done. Write a short script that opens on their problem, shows the product solving it in a few steps, and ends on one next step. Record on a clean screen with a rehearsed run, then cut everything that does not help the job. Most guides we read land on about two to five minutes, and shorter is safer. Nothing below is a rule from a platform. It is a way of working, backed by the sources named in each section.
Sources were read on 24 October 2026: TechSmith (page dated 16 January 2025), Typito (12 June 2023), Viostream (the page shows both 14 October 2021 and 20 October 2026) and Wistia (a page dated 1 July 2025). Where a number comes from one of them, it is named. Where it is general advice, it says so.
What a product demo video is, and what it is not
A product demo video shows your product doing its job, so a viewer can decide if it fits them. TechSmith describes it as a video that shows the product in action to explain its value. Typito says demos are used early in the buyer's journey to build awareness and interest.
It is not the same as three nearby things:
- A tutorial teaches one task in detail, step by step. If you want that, read the tutorial video script template.
- A feature tour walks through every menu. Viewers leave in the middle of it.
- An app demo for a store page or a launch has its own rules. How to make an app demo video on Mac covers that case.
TechSmith's advice is to keep the main demo as a general overview and move the intricate steps into separate tutorial videos. For a complex product it suggests several demos. That split is the most useful idea in this whole topic: one demo, one job.
Step 1: decide the one job before you open the app
Before anything else, write three lines:
- Who is watching? A buyer who has never seen the product is different from a customer who already pays. Typito tells you to research the audience's pain points and set a goal such as leads, sales or education.
- What job do they want done? Say it as the viewer would: "send an invoice in a minute", not "use our invoicing module".
- What should they do after? TechSmith says to define what viewers should learn and their next step. One step: start a trial, book a call, read the docs.
If you cannot fill all three lines, you are not ready to record. A demo with no audience tends to show everything, and a demo that shows everything tends to land with no one.
Step 2: choose the length
There is no official right length. Here is what the sources say, side by side.
| Source | What it says about length | Date and note |
|---|---|---|
| Typito | Keep videos to two to five minutes. For products with many features, make a shorter series | 12 June 2023 |
| TechSmith | Gives no running time. Keep the demo general, move detail to tutorials | 16 January 2025 |
| Viostream | Gives no running time | Not found |
| Wistia | Videos under one minute average a 52% engagement rate, which Wistia explains as viewers watching about half the video's length. Testimonial videos average 46% and product videos 50%. It also says engagement declines after five minutes | Page dated 1 July 2025, citing its 2026 State of Video Report of over 13 million videos |
Two cautions on the Wistia numbers. The page does not describe how the data was sampled. It also does not say whether its 11% drop in engagement is a relative or a percentage-point change, so do not quote that as a hard rule. What you can take from it, as general advice, is that the average viewer drops off over time, so the first minute matters most.
A working rule that fits all four sources: aim for under three minutes, put the answer to "what is this and why care" in the first fifteen seconds, and split anything that needs more into a second video.
Step 3: write the script
You do not need a polished speech. You need an order. Typito suggests an intro, a feature demo and a call to action. TechSmith says to cover four things: describe the product, show the solution to a pain point (not just features), show how it works at a high level, and end with a clear call to action such as "Start a Trial". Viostream recommends a simple story, where the viewer is the hero, the obstacle is their problem and your product helps them past it.
Here is one outline that fits all three. The timings are an example, not a standard.
| Part | What you say | What the screen shows | About how long |
|---|---|---|---|
| Hook | The problem, in the viewer's words | The messy "before" state | 10 to 15 seconds |
| What it is | One sentence: what the product is and who it is for | The home screen | 10 seconds |
| The job, step 1 | What you do and why | The first click | 15 to 20 seconds |
| The job, step 2 | Same | The next screen | 15 to 20 seconds |
| The job, step 3 | Same | The result | 15 to 20 seconds |
| The payoff | What changed for the viewer | The finished result, large | 10 seconds |
| Next step | One action, said once | A plain end card with the link or button name | 5 to 10 seconds |
Rules that make the script better:
- Write for the ear. Short sentences. Read it aloud. If you run out of breath, split the sentence.
- Show benefits, then features. "Your team sees every request in one list" beats "we have a unified inbox."
- Name only what you show. If the script mentions a feature that never appears on screen, cut the line.
- Keep jargon off the voice track. Typito suggests defining acronyms with text on screen instead of in the script.
- One call to action. Typito's tip, and a sound one: two asks split the viewer.
If you want a filled-in version with the left column for words and the right for the screen, the tutorial video script template is built that way. Adapt it by swapping the steps for your job.
Should you memorise the script?
Viostream suggests the presenter memorise lines so they can focus on the demonstration rather than the script. For a screen demo, a different approach often works better, and this is general advice from experience of the format, not from a study: record the voice from the script as a separate pass, or read short lines one at a time while you click. How to record your voice on a Mac covers the options.
Step 4: set up the screen before you record
TechSmith warns that system audio can capture notifications and distracting sounds, so set the audio sources on purpose. Typito suggests low background noise and prepared sample files for screen recordings. Put those together and you get a checklist.
Clean the desktop and the app
- Close every app you do not need. Turn on Do Not Disturb so no banner appears mid-take.
- Hide personal data. Use a demo account with believable but fake names, emails and numbers.
- Pre-load the sample data your story needs, so you never wait for a spinner on camera.
- Log in before you start. A password field on screen is a mistake you cannot unsee.
- Clear the browser bookmarks bar and extra tabs if the browser is on screen.
Match the screen to the video
- Pick a resolution you will export at, and keep text big enough to read at that size. If the demo will play small, bump the app's own zoom or font size. See YouTube video size, resolution and aspect ratio for the sizes that platform lists.
- Hide the Dock and use a plain wallpaper if the full screen is in shot.
- Make the cursor easy to follow. A smooth, steady cursor beats a jittery one. If your recorder cannot change the cursor, move slowly.
Check the audio
- A quiet room beats an expensive microphone. Typito and Viostream both name a quiet location as a basic.
- Record a ten-second test and listen on headphones before the real take.
Step 5: record the demo
How you record depends on how much you want to fix afterwards. The choices are:
| Option | Good for | Limit |
|---|---|---|
| Screenshot app, Shift-Command-5 | A quick first take, no install | Editing is trim only afterwards (see how to record a video on Mac) |
| QuickTime Player | Simple recordings with a microphone | Same limit: basic trim and split |
| OBS Studio | Scenes, overlays, a webcam beside the screen | More setup. See how to use OBS Studio on Mac |
| An editor-first recorder | Demos that need zoom and cursor polish | You decide the tool in the next section |
Tips for the take itself. TechSmith says to rehearse the demo a few times first, and Viostream says to record several takes. Add these, which are general advice:
- Do a dry run with the script and no recording. You will find the broken step before the camera does.
- Click slower than you think you need to. You can speed a slow part up later. You cannot slow down a rushed one.
- Pause for a beat before and after each step. It gives you a clean place to cut.
- Do not fix mistakes mid-take. TechSmith's advice is to remove unwanted footage later rather than re-record missed steps. Stop for a second, then repeat the line. The pause shows up as a flat spot you can find and cut.
- Record in short sections. One section per script part is easier to redo than a ten-minute take.
If a tool looks small on screen, zoom the recording afterwards or zoom the app. Do not ask viewers to squint.
Step 6: edit it down
Editing is where a demo goes from fine to good. TechSmith says to keep the edit simple and check it against the storyboard. Typito adds that you should vary the pace: speed up repeated steps and slow down close-ups. Both sources say to avoid overusing effects.
A cut list that works in any editor:
- Cut the dead start and end. Everything before your first word and after your last.
- Cut the pauses and the false starts. Use the flat spots you left.
- Speed up the waiting. If a page loads for six seconds, cut it or speed it up.
- Zoom in on what matters. The viewer should never hunt for the cursor.
- Add text only where it helps. Typito suggests text cues to label steps and features.
- Add captions. Typito and Viostream both recommend subtitles. Many people watch with the sound off, but that is general advice, not a number we are quoting.
- Keep music low or skip it. Typito says to avoid distracting music. If you use any, keep it under the voice.
- End on the next step, once, on screen.
For the tools, how to edit a screen recording on Mac shows what QuickTime can and cannot do, and video editing tips for screen recordings goes deeper on pacing. Looking for a full editor? See best video editing software for Mac.
Step 7: export and publish
- Export as MP4. MP4 plays nearly everywhere (general advice). If your file is a .mov, the free MOV to MP4 converter runs in your browser.
- Check the size. If the file is too big to email or upload, the video compressor shrinks it. How to compress a video on Mac has the steps.
- Trim a last stray second with the free video trimmer.
- Put it where the viewer already is. On the product page near the top, in the sales email, in the onboarding flow. Viostream suggests sending demo videos to buyers after purchase as onboarding guidance, and sharing them on social media and with customer service.
- Watch it once, cold. Open the exported file, not the project, and watch it from start to end with the sound on. Then once with the sound off.
A quick checklist you can copy
- One viewer, one job, one next step written down
- Script under 3 minutes, with the problem in the first 15 seconds
- Demo account, fake data, notifications off
- A dry run, then the take
- Pauses left in so cuts are easy
- Zoom on every small thing that matters
- Captions on
- One call to action, on screen and in the voice
- Exported as MP4 and watched start to end
Where MotionShine fits (by the maker of MotionShine)
This guide works with any recorder. If you want one more option, MotionShine is a free Mac screen recorder made by me, and I should say plainly what it is and is not.
What it does: it records your display, a window or an area. It adds an auto zoom on every click, a smooth cursor, click effects and motion blur. Its editor has text, picture and music lanes, a voice over, and captions made on your Mac. That covers most of the cut list above, so one app handles recording and polish. It runs on macOS 13 and later.
Free export goes up to 720p at 30 fps, with no watermark and no time limit. Pro unlocks 1080p, 1440p and 4K, and 60 fps, as a one-time purchase.
Who it is not for: anyone on Windows, anyone who needs a share link with viewer analytics (MotionShine has no share links, you export a file), and anyone making a live-action product video with a camera. If your plan is a polished brand film, a full video editor is a better home. And if all you need is a trim, QuickTime Player is already on your Mac.
FAQ
How long should a product demo video be?
There is no official length. Typito says two to five minutes, and Wistia's data shows engagement falling as videos get longer, with a decline after five minutes. As general advice, aim for under three minutes and split anything longer into a second video.
What should a product demo video include?
TechSmith lists four things: a description of the product, the solution to a pain point, how it works at a high level, and a clear call to action. Add the audience's problem at the start, and keep the demo to one job.
What is the difference between a product demo and a tutorial?
A demo shows what the product does and why it matters, in broad strokes. A tutorial teaches one task in detail. TechSmith suggests keeping the demo general and moving the detailed steps into separate tutorial videos.
Do I need a script for a product demo video?
You need at least an outline. Viostream and TechSmith both recommend writing the script before you record, so the demonstration stays focused. The script template gives you a ready structure.
Do I need to show my face or use a voice?
Not required. Many software demos use screen footage with a voice over or captions only. The sources here do not say a face is needed for screen demos. A clear voice and a clean screen matter more.
What should I record a product demo with on a Mac?
The built-in Screenshot app (Shift-Command-5) and QuickTime Player both work for a first take. For zoom, cursor polish and captions in one place, use an editor-first recorder such as MotionShine, or pair a recorder with an editor from the best video editing software for Mac list.
