How to make a tutorial video for your product
How to make a tutorial video for a software product: plan, script, record, narrate and keep it current. Steps and examples.

On this page
To make a tutorial video for a software product, pick one task, write the script while you click through the real product, record the screen and the voice separately, add captions and have someone follow the finished video step by step before you publish. Then plan for the day the product changes, because it will.
A tutorial video is a short screen recording with narration that shows one task from start to finish, so a viewer can follow along and get the same result.
Most guides on how to make a tutorial video are general. Before writing this, we read three of them, two from TechSmith and one from iSpring (on 14 November 2026). They're good on scripting, recording and editing. None of the three mentions checking the video against the product or what to do when the product changes. If you ship software every week or two, those two steps decide whether a tutorial is still right next month.
What is a tutorial video?
A tutorial video shows a viewer how to complete one task, step by step, in the order they'd do it themselves. For software, that usually means a recording of the screen with a voice explaining each click. The viewer should be able to pause, copy the step in their own account and carry on.
People use several names for nearly the same thing.
| Type | Its job | Who it's for |
|---|---|---|
| Tutorial video (also called a video tutorial) | Teaches one task from start to finish | A customer who wants to do the task now |
| How-to video | The same thing under its everyday name | The same customer |
| Training video | Teaches a role or a workflow across several tasks, often as a series | New customers, partners and academy learners |
| Product demo video | Shows what the product can do | A buyer who hasn't signed up yet |
| Launch video | Announces a release and why it matters | Existing customers on launch day |
How to make a tutorial video in seven steps
- Pick one task.
- Write the script inside the product.
- Set up a clean screen.
- Record the screen.
- Record the narration.
- Edit and add captions.
- Test the video against the product, then publish.
Step 1: Pick one task
One video covers one task and ends with one result. "How to create an invoice" is a tutorial. "Getting started with billing" is five tutorials.
Write the task as the sentence a customer would type into your help center search. That sentence becomes the title. Then decide two things before you write anything else:
- Who is watching. A new customer and an account admin need different starting points.
- Where the video starts. Assume the viewer is signed in and on the screen where the task begins.
Good tasks come from three places: the release notes for your next release, support tickets that begin with "how do I" and help center searches that returned nothing.
Step 2: Write the script inside the product
Open the product and do the task while you write. Don't write from memory or from the spec. Button names change between design and release, and a script written from the spec can describe a screen that never shipped.
Use two columns. The left column is what happens on screen. The right column is what the voice says.
| On screen | Narration |
|---|---|
| The Billing screen, before anything is clicked | "In this video, you'll send your first invoice. Start in Settings and open Billing." |
| Select New invoice | "Select New invoice." |
| Choose a customer from the list | "Pick the customer you're billing." |
| Select Send | "Check the total, then select Send. Your customer gets the invoice by email." |
A few rules keep the narration easy to follow:
- Open with the result, then say where to start.
- Name each control exactly as the screen names it.
- Give one action per sentence, and say the action before the reason.
- Stop when the task is done.
Read the script aloud and time it before you record. If it runs long, look for a second task hiding inside the first.
Step 3: Set up a clean screen
Whatever is on screen while you record ends up in front of every customer. Prepare the account and the window first.
- Use a demo or test account with realistic sample data. Never record real customer names, emails or payment details.
- Set the window to 1920 by 1080 and zoom the browser until the smallest label is easy to read on a laptop.
- Close other tabs, hide the bookmarks bar and turn off notifications.
- Keep dates and version numbers off screen where you can. They date a video.
- Reset the account to the same starting state before each take.
If the feature hasn't shipped yet, record in a test environment that matches what customers will get, and wait until the screens have stopped changing. At SWFTMENT, we ask for the screens to stop changing six days before launch.
Step 4: Record the screen
Any screen recorder that captures 1080p video and lets you export the file will do. You don't have to install one. macOS has a screen recorder built in, and in Windows 11, the Snipping Tool can record a video of part of the screen.
While you record:
- Move the pointer slowly and in straight lines.
- Pause for a beat after each click so the viewer sees what changed.
- Type at a normal speed. Don't paste.
- Record each step as its own short clip where you can. When one screen changes later, you replace one clip and keep the rest.
- Don't talk while you click. The voice comes next.
Step 5: Record the narration
Record the voice separately from the screen. Then a stumble costs you one sentence, and you never have to redo the clicks because of it.
A quiet room and a USB microphone or a good headset are enough. Read the script as written. If you trip on a line, pause, say it again and cut the first attempt later. Use the same voice, room and microphone across a set of tutorials. You'll need them to match when you re-record a line months from now.
An AI voice can work for tutorials if a person checks how it says your product's names and listens to the whole take before it goes out.
Step 6: Edit and add captions
Lay the narration under the screen recording and line up each sentence with its click. When the two drift apart, stretch or trim the pause in the picture and leave the voice alone.
After that, editing a tutorial is mostly removing things:
- Cut loading spinners, long typing and any pause that teaches nothing.
- Add a highlight or a zoom only where the viewer might miss the control.
- Leave music out, or keep it low enough that every word is clear.
Then add captions to every video. Captions for prerecorded video are a Level A requirement in the Web Content Accessibility Guidelines (WCAG 2.2, success criterion 1.2.2, read on 14 November 2026). They also let someone follow along with the sound off.
You already have the words, so captions take minutes. On YouTube, you can paste the script as a transcript. For the languages it supports, the timing is synchronized to the video automatically.
Step 7: Test the video against the product, then publish
Give the finished video to someone who didn't make it. Ask them to open the product in a fresh account and follow the video, pausing at each step.
Every click has to match what the video shows and says. If a label is different, a step is missing or a screen looks different, fix the video before it goes out. At SWFTMENT, an editor follows every step in the real product before anything goes live. If a step doesn't match, it doesn't ship.
Publish the video where the customer will look for it:
- next to the feature inside the product
- in the help article for the same task
- on YouTube, if you want people to find it through search
Put the written steps under the video. Some people would rather read, and search engines read the text on the page.
How long should a tutorial video be?
A tutorial video should be as long as one task takes and no longer. At SWFTMENT, we keep each tutorial to three minutes or less. TechSmith, which makes screen recording software, suggests three to five minutes for simple topics in its guide to tutorial videos (read on 14 November 2026).
When a script runs past that, the task is usually two tasks. Split it. A viewer looking for one step shouldn't have to scrub through four minutes to find it.
What do you need to make a tutorial video?
To make a tutorial video for software, you need six things: a script, a demo account, a screen recorder, a microphone, a video editor and a second person to test it.
| What | Use | Why |
|---|---|---|
| A script | The two-column script from step 2 | It keeps the video short and gives you the captions |
| A demo account | A test account with sample data | No real customer data on screen |
| A screen recorder | The recorder built into your PC or Mac, or a dedicated tool | It needs to capture 1080p and export the file |
| A microphone | A USB microphone or a good headset | Every word has to be clear |
| A video editor | Any editor that can cut clips and add captions | Tutorials need cuts and captions, and little else |
| A second person | Someone who didn't make the video | They run the test in step 7 |
For a mobile app, record the phone's own screen. Don't film the phone. iPhones and phones on Android 11 or later have a screen recorder built in. The seven steps stay the same.
How do you make a tutorial video for YouTube?
To make a tutorial video for YouTube, follow the same seven steps, then add four things when you upload: a title customers would search for, a two-line description, chapters and captions.
- Use the task as the title, in the customer's words.
- Say in the first two lines of the description what the viewer will be able to do, and link to the help article.
- Add chapters. Put a list of timestamps and titles in the description. YouTube asks that the first timestamp is 00:00, that there are at least three in ascending order and that each chapter is at least 10 seconds long (YouTube Help, read on 14 November 2026).
- Upload the script as captions.
Group tutorials into a playlist for each part of the product. In your help center, embed the YouTube video. Don't host a second copy there, or you'll have two versions to keep right.
One limit to plan around: YouTube doesn't let you replace a video. A new upload gets a new address. When a tutorial changes, you upload the new version, swap the embed on every page that used the old one and take the old one down.
How do you keep a tutorial video current when the product changes?
You keep a tutorial video current by saving everything it was built from, listing what each video shows and checking that list every time you ship. Skip that and the tutorials fall behind the product one release at a time.
Build each video so it can be changed:
- Keep the script, the editing project and the raw clips together in one folder for each video.
- Keep one list of every tutorial: the screens and labels it shows, every page it's embedded on and the date it was last checked.
- Give the list an owner by name.
Then tie the check to the release. When the release notes are drafted, search the list for every screen the release touches. For each video you find, use this table.
| What changed | What to do |
|---|---|
| A label or a button name | Replace the clip for that step and re-record the sentence that names it. If the new line sounds different from the rest, re-record the paragraph. |
| The order of steps, or a new required step | Rewrite and re-record that section |
| The whole screen or flow | Redo the video from the script |
| The feature was removed | Retire the video and point its links to the closest current one |
Do the update before the release goes live, so customers never follow steps that no longer match.
Where your video host lets you replace the file behind the same link, do that. YouTube doesn't, which is why the list records every page a video is embedded on.
At SWFTMENT, when a screen or a setting changes in a client's product, we update the tutorials and the help docs for it.
What should you check before you publish a tutorial video?
Before you publish a tutorial video, check eight things: the title, the scope, the control names, the data on screen, the captions, the test, the written steps and the saved source files.
- The title is the task, in the customer's words.
- The video covers one task and ends when the task is done.
- Every control is named exactly as the screen names it.
- No real customer data appears on screen, and dates and version numbers are kept out where possible.
- Captions are on and match the narration.
- Someone who didn't make the video followed it in a fresh account, and every step matched.
- The written steps sit under the video.
- The script, project file and clips are saved, and the video is on the tutorial list with today's date.
Questions people ask about making tutorial videos
What does video tutorial mean?
A video tutorial is a video that teaches one task step by step, so the viewer can do it themselves. "Video tutorial" and "tutorial video" mean the same thing. For software, it's usually a screen recording with narration and captions, short enough to watch while doing the task.
What is the difference between a tutorial video and a how-to video?
There's no real difference. Both show one task from start to finish, and people use the two names for the same thing. If you want to know how to make a how-to video, the seven steps above are the way to do it.
Can you give me some examples of how-to videos?
Common how-to videos for a software product include setting up an account, inviting a teammate, connecting an integration, creating a first report and changing a billing plan. Each one covers a single task with a clear result. A good test: the title starts with "How to" and the viewer can finish the task in one sitting.
Do you need to be on camera in a tutorial video?
No. A software tutorial needs the screen and a clear voice. A face on camera can help in a welcome or a launch video, where trust matters. In a tutorial, it adds little, and it's one more thing to re-record when the product changes.

Keep reading.
Rather have it done for you?
Book a free 20-minute release review. We look at your next release and what your customers need to learn it. No pitch.
Book a release review

