How to Make a Tutorial Video

To make a tutorial video, work in three phases: plan a shot-synced script where each line maps to one on-screen action, record a full pass plus pickup re-takes for spots you flub, then edit out filler and dead air. Pick your tool by output volume: OBS Studio (free) under a few videos a month, Camtasia (~$179.88/yr) once you're shipping 1-2 polished videos a week. Record at 1080p, narrate at 90-120 words per minute, and export voiceover as WAV 44.1 kHz. For software where the viewer needs to do the steps, an interactive demo often beats video outright.

Pick your tool: free vs paid in 2026

Choose by how many videos you'll actually make, not by feature lists.

OBS is the strongest free pick: no watermark, no time limit, no upsell, on all three platforms. You build a scene, add a Display Capture or Window Capture source, then add an Audio Input Capture source for your mic. The catch is that OBS does not edit — beginners get stuck looking for a trim button that isn't there, so budget for a separate editor.

Camtasia earns its price once you're recording regularly. Its 2026 version added AI noise removal, auto-captions, and Smart Cut, which automatically strips dead air and filler words. Below roughly 2-3 videos a month, that's money you don't need to spend; at 1-2 polished videos a week, it pays for itself in editing time. If you just want a recorder, our roundup of screen recorders for product demos compares these in more depth.

The plan-record-edit method

The three phases keep you from the most expensive mistake: editing while you record. Plan the whole video first, capture it in one focused session, then fix it in a separate pass with fresh ears. Mixing the phases — stopping to re-watch every take — triples the time a tutorial takes.

Before you record anything, decide on the single task the video teaches. One task per video. If you can't state the outcome in a sentence ("by the end, you'll have published your first demo"), the scope is too big and the recording will ramble.

Writing a shot-synced script (why topic order fails)

This is the part most people skip, and it's why their narration drifts out of sync with the screen.

Write a shot-synced script: each line maps to one on-screen action — a click, a transition, a panel appearing — not paragraphs of prose. Structure the script around the visual flow, not the logical or topic flow. If you script by topic ("first, let's understand permissions..."), the words and the cursor pull apart, and the viewer watches you talk about one thing while clicking another.

A teaching arc that holds up: outcome → setup → steps → recap → next action. Show where you're headed, get set up, walk the steps, recap, then point to what to do next.

Write spoken language, not written. Sentences shorter than feel natural on the page read fine out loud. The same instinct that makes step-by-step guides clear — one action per step — makes scripts clear: one action per line.

Pacing: the 90-120 words-per-minute rule

Target 90-120 words per minute. That feels slow when you read it, which is the point — nerves push people past 120 wpm and the tutorial becomes a blur.

Use the rate to estimate length. A 4-minute voiceover is roughly 400-480 words of script. Write the script, count the words, and you'll know the runtime before you press record. Slow the logic down — pause on each step — while keeping the pace up so you don't ramble. Rambling kills retention as surely as racing does.

Recording settings and the pickup-pass technique

Record at 1080p or higher. 720p looks visibly soft on modern displays and reads as amateur immediately. Audio quality matters as much as video: export your voiceover as WAV, 44.1 kHz, 16-bit for the editor.

Don't chase a perfect single take. Record the full pass start to finish, then do a pickup pass — re-record only the few spots where you stumbled, and splice them in. Watching the screen recording while you narrate calibrates your pace to what's actually happening on screen and cuts editing time sharply.

Editing: cut dead air, filler, and clean the audio

The edit pass is short if the recording was planned. Three jobs: remove filler words ("um," "uh"), normalize volume so it's even throughout, and apply noise reduction. Camtasia's Smart Cut and Descript do all three automatically; in OBS-then-editor workflows you trim manually. Leaving filler and dead air in is the biggest amateur tell — viewers feel the slack even if they can't name it.

When an interactive demo beats a video

Video is the wrong format when the viewer needs to act. A passive video can't let someone practice the steps, so for help-center content — "how do I do X in this product" — a self-guided, click-through walkthrough converts better. The viewer advances at their own pace and actually performs each click.

Tools like Supademo, Storylane, Arcade, and createademo build these by capturing your product as you walk through it. With createademo you install a Chrome extension, record the flow as screenshots and/or video, then add clickable hotspots, tooltips, zoom, redaction, and per-step audio narration — and share it as a link or embed it. For showing multi-step software where the user has to follow along, an interactive demo beats a tutorial video because it's self-paced and re-recordable one step at a time.

Interactive also wins when content changes often. Re-shoot a whole video every time a button moves, or swap a single screenshot — the second is a few minutes. See interactive demo vs video for the full trade-off, and interactive demo examples for what finished ones look like.

Pick the tool by your volume, script to the screen and not the topic, hold 90-120 wpm, and record in passes. Then ask the real question before you ever open OBS: does the viewer need to watch this, or do it? The answer decides whether you're making a tutorial video at all.