What is a tutorial video?

What separates a tutorial from a walkthrough

The words are often swapped, but they answer different needs. A tutorial is task shaped: reset a password, publish a roster, send a recurring invoice. It has a start state, a finish state and nothing else. A walkthrough is space shaped: it tours a dashboard or a product so a new user knows where things live, without necessarily finishing anything. An instructional video sits wider still, teaching a procedure or skill with explanation, often as part of formal training. Mixing them is the usual cause of a video that feels long: a viewer who wants one task does not want the tour.

The shape that works

Open by stating the task and, where it helps, the end result, so the viewer knows they are in the right place. Nielsen Norman Group's research found that lengthy introductions frustrate viewers, and even a few seconds of preamble can feel excessive in instructional video. Then give one step per scene, each naming the control exactly as it appears on screen and showing the change it causes. If the process has an unfamiliar concept, a short overview before the steps helps the viewer build a map. End with confirmation that the task is done and, optionally, what to do next. Keep one task per video and link related tasks separately.

Accessibility is part of the job

A tutorial is only useful if the viewer can take in every step. The W3C's guidance on making audio and video accessible covers captions for people who cannot hear the narration, transcripts, and description of important visual information for people who cannot see it. In practice that means captions on every tutorial, narration that says which control to press rather than click here, and a written list of the steps beside the video. A transcript also helps sighted viewers, because they can scan for the step they need without watching from the start.

Common mistakes

Going too fast is the most frequent problem, because the person recording already knows the steps. Next are vague instructions such as go to the settings area, which leave viewers hunting. Changing the layout of every scene forces the eye to relearn the screen. Showing an outdated interface, or a demo account that differs from what customers see, breaks trust immediately. Ending with a sales pitch confuses the purpose, since the viewer came for help, not persuasion. And publishing without a clear title that uses the words people search for means the tutorial is never found.

Length and pace

Most single task tutorials land between one and five minutes, which matches Wistia's grouping of educational, how to and tutorial videos. Pace matters as much as total length. Each step needs time for the viewer to see the screen, hear the instruction and find the control in their own window, which is far slower than a promo's rhythm. If a tutorial runs past five minutes, it is usually several tasks joined together, and splitting it makes each part easier to find, follow and update when the interface changes. A useful check is to follow the finished video yourself on a fresh account with no prior knowledge, pausing only where the video tells you to act; every place you have to rewind marks a step that needs more time or a clearer instruction.

Where it shows up in the product

Tutorial is one of the video generator's three types and is a paid feature from the Starter plan. Tutorial mode offers only five scene roles: intro, tutorial, how it works, checklist and outro. Each step scene runs 5 to 9 seconds, the intro and wrap up 3 to 5, and step narration is 10 to 25 words. The voice is forced to the instructional style, and AI tutorials come back on the Calm pace. Screenshots can be uploaded or captured from a shared screen as still frames. The CRM pipeline example adds a how it works overview before its steps.

Questions people ask