Short answer
A customer onboarding video shows a new customer how to reach their first useful result in your product. Most teams need four kinds: a short welcome, a first-task walkthrough, a setup video for admins, and feature videos for later. Keep each to one task, usually under two minutes, place it where the customer gets stuck (welcome email, empty states, checklist items, help center), and measure activation, not views.
Most onboarding videos fail quietly. They get made, they get linked from a welcome email, and nobody checks whether the customers who watched them did anything different afterwards. A customer onboarding video is worth making only if it moves someone from "signed up" to "got value", so start from that moment and work back.
Before you script anything, define your activation event: the action that tells you a new customer has got something real out of the product. For a made-up invoicing app called Ledgerly, it might be "sent a first invoice to a real client". Every video below should push toward that event or remove an obstacle in front of it.
Types of customer onboarding video
Four types cover nearly every product. Most teams make all four eventually, but the first-task video is the one to make first.
Welcome video
Thirty to sixty seconds that tell the customer what they'll be able to do and what to do first. It's an orientation, not a feature tour. A founder on camera works well here if your product sells on trust; a quick look at the main screen works for everyone else.
First-task video
The walkthrough of the one task that leads to activation: import the data, create the first project, send the first invoice. Show it with realistic sample data so the result looks like something the customer wants. This is the video most worth getting right.
Setup and admin video
In B2B products, the person who signs up is often not the person who does the work. Admins need their own short videos for inviting teammates, connecting single sign-on, setting permissions and linking integrations. Keep them separate so end users never sit through them.
Feature videos
Short clips for features customers reach after the first week: automations, reports, the API. Send them when behavior suggests the customer is ready, not on day one. Our post on feature discovery videos covers the timing.
Where to put onboarding videos
The same video works far better at the moment of need than in a library nobody opens. Here's where each type tends to fit.
| Onboarding moment | Video | Typical length | Placement |
|---|---|---|---|
| Just signed up | Welcome | 30–60 seconds | Welcome email and the first screen after sign-up |
| Facing an empty screen | First task | 60–120 seconds | The empty state itself, next to the main button |
| Working through setup | First task or setup step | 45–90 seconds per step | Each onboarding checklist item |
| Admin configuring the account | Setup and admin | 1–3 minutes each | Admin settings pages and a separate admin email |
| Stuck on a specific task | Task tutorial | 1–3 minutes | The matching help-center article, at the top |
| Ready for more (week 2 onward) | Feature video | 30–90 seconds | In-app announcement or a behavior-triggered email |
Email needs a special note: don't count on video playing inside the message. As of October 2026, caniemail.com estimates HTML5 video support at about 24% of email clients, and Gmail strips the video tag entirely (caniemail). Use a still image with a play button that links to the video on a page you control.
Inside the app, a muted autoplay preview is allowed in Chrome, but autoplay with sound generally needs the user to have interacted with the page first (Chrome for Developers). Let customers press play. A video that starts talking over the first screen they see feels like a pop-up.
How long a customer onboarding video should be
Shorter than the one you're planning. A new customer is trying to do something, and the video is a detour. Wistia's analysis of more than 13 million videos found that videos under a minute average 52% engagement, and that viewers typically watch over half of tutorials in the one-to-five-minute range (Wistia). For onboarding, that points to under a minute for welcomes and announcements, and one to three minutes for anything the customer follows step by step.
If a first-task video runs past three minutes, the task is probably too long for a first session, and that's a product question as much as a video one. Split it, or simplify the path. The video length calculator can help you size the script.
Measuring whether onboarding videos improve activation
Views tell you the video was found. They don't tell you it worked. Track three events for every onboarding video: played, watched to the end (or to the last chapter), and activation within a set window, such as seven days after sign-up.
- Define the activation event and the window before the video goes live.
- Log play and completion events with the customer's account ID, so you can join them to product usage.
- Compare activation for new customers who watched against those who didn't, by signup week.
- If you can, run a holdout: show the video to half of new sign-ups for a few weeks and compare.
- Read the drop-off curve. If most viewers leave at the same second, that scene is the problem.
Be careful with the watched-versus-didn't comparison on its own. Customers who choose to watch are often more motivated anyway, so they'd activate at a higher rate with or without the video. A holdout is the honest test. Support tickets on the task the video covers are a useful second signal; reducing support tickets with video goes into that.
Keeping a customer onboarding video accurate
Onboarding videos show your newest customers the screens they're about to use, so they go stale at the worst possible place. A renamed button in a marketing video is a shrug. In a first-task video, it's a customer who can't find the next step on day one.
List every onboarding video with the screens it shows, and check them as part of each release that touches those screens. Recording them in short scenes, one per step, makes fixes cheaper. DemoVexa is built for this case: it recreates your product's screens from its code and times them to the voiceover, so after a UI change you rebuild the video instead of re-recording it. If your onboarding is mostly in-app tours and checklists, an onboarding platform is the core tool and video is the supporting piece; the software walkthrough tool guide compares the formats.
- Captions on every onboarding video: they're a Level A requirement in WCAG 2.2 and plenty of people start work with the sound off.
- Localize the videos for each market you sell in, including the on-screen UI, not just the voice.
- Use the same sample data across every onboarding video so the customer sees one consistent world.
Questions
Can I put a video directly in an onboarding email?
Not reliably. Most email clients, including Gmail, don't play embedded video, so the standard approach is a thumbnail image with a play button that links to the video on your site or in your app. Make the thumbnail show the outcome, not a logo.
Do admins and end users need different onboarding videos?
Yes, in most B2B products. Admins need setup videos for teammates, permissions, single sign-on and integrations; end users need the first-task video. Mixing them makes both groups sit through steps that aren't theirs, and end users often stop watching before their part.
How many onboarding videos should a new product start with?
Start with one first-task video for the action that leads to activation, plus a short welcome if you have time. Add setup and feature videos once you can see in your data where new customers stall, rather than filming a full library up front.
Make product videos from your code
DemoVexa reads your app's code, writes the script, adds a voiceover and animates your real screens in 16:9, 9:16 and 1:1. Try it on your own product: 14 days free, no card.
Sources
- caniemail: HTML5 video support in email clients (checked 29 October 2026)
- Chrome for Developers: Autoplay policy in Chrome (checked 29 October 2026)
- Wistia: How to choose the right marketing video length for any goal (checked 29 October 2026)
- W3C: Understanding WCAG 2.2 Success Criterion 1.2.2, Captions (Prerecorded) (checked 29 October 2026)
DemoVexa publishes this guide and makes a product video app, so we have a stake in the topic. Facts about other products and platforms come from the sources listed, on the dates shown, and can change. Corrections are welcome through our contact page.