MotionShineShort answer: a good tutorial script has six parts: a one-line promise, a short setup, the steps (one action and one reason each), a check that it worked, a recap and one next step. Write what you will say in the left column and what the screen shows in the right. The template below is ready to copy. Nothing here is a rule from a platform or a study. It is a structure that keeps screen recordings short and easy to follow.
The template
Copy this into a document and replace the text in brackets.
Title: How to [do the task] in [app or tool]
1. Hook (10 to 15 seconds)
- Say: "In this video I will show you how to [task]. By the end you will have [result]."
- Show: the finished result, or the first screen.
2. Before you start (10 to 20 seconds)
- Say: "You need [app or version], [file or account], and about [time] minutes."
- Show: the app open, with the starting file.
- Optional: say the one thing that goes wrong most often.
3. Steps (the main part) For each step, fill in:
- Step number and name: [Step 1: Open the settings]
- Do: [click Settings in the menu bar]
- Say: [what you are doing, in plain words]
- Why: [one sentence on the reason]
- Show: [what the screen should look like]
- Zoom or highlight: [the button or field to make large]
Repeat for each step. Aim for 3 to 7 steps. If you have more, split the video in two.
4. Check (10 to 20 seconds)
- Say: "To check it worked, [look at X]. You should see [Y]."
- Show: the finished result.
5. Recap (10 to 15 seconds)
- Say: "So the steps were: [one], [two], [three]."
- Show: a text list on screen, or the final result.
6. Next step (5 to 10 seconds)
- Say: "If you want to [next task], watch [video name]. If you hit a problem, [where to ask]."
- Show: the end screen or a link.
The time ranges above are suggestions for keeping a video moving, not measured figures.
A two column version
Many people find it easier to write two columns, one for the voice and one for the screen. Here is the shape.
| Time (rough) | What I say | What the screen shows |
|---|---|---|
| Hook | "Here is how to [task]." | The result |
| Setup | "You need [x]." | The starting screen |
| Step 1 | "First, [action], because [reason]." | Zoom on [button] |
| Step 2 | "Next, [action]." | Cursor moves to [field] |
| Check | "You should now see [y]." | The result |
| Recap | "That is [steps]." | Text list |
| End | "Next, watch [video]." | End card |
You can keep this in any document or spreadsheet. Fill the right column even if you plan to record live. It reminds you what must be visible.
A filled example
This sample is for a made-up task, so you can see the level of detail. Replace the content with your own.
Title: How to resize a picture in Preview on a Mac
Hook: "In this video I will show you how to make a picture smaller in Preview. By the end you will have a copy that is small enough to email." Show: a large picture, then the small one.
Before you start: "You need a picture on your Mac. Preview is already installed." Show: the picture in Finder.
Step 1, open the picture. "Double click the picture. It opens in Preview, because that is the Mac's default for pictures." Zoom on the title bar.
Step 2, open the size window. "Open the Tools menu and choose Adjust Size. This is where Preview keeps the size settings." Zoom on the menu.
Step 3, set the new size. "Type a smaller width. Leave the lock on so the shape does not stretch. We do this so the picture does not look squashed." Zoom on the fields.
Step 4, save a copy. "Export it with a new name, so your original stays safe." Zoom on the name field.
Check: "Open the new file. It should look the same, only smaller."
Recap: "Open, Adjust Size, set a width, export a copy."
Next step: "To make it smaller still, watch my video on compressing pictures."
Check your own app's menu names before you write a script. Menu names change between versions, so record with the version your viewers will have.
How to write each part well
The hook
Say what the viewer will be able to do, not who you are. Your name can come later. If your title says "How to resize a picture in Preview", the viewer already knows the topic. Use the first line to confirm it and show the result.
The steps
- One action per step. If a step has "and" in it, split it.
- Name the thing on screen. "Click the blue button in the top right" is clearer than "click it".
- Give the reason once. One short sentence. More than that slows the video.
- Write the way you speak. Read each line aloud. If you stumble, rewrite it.
- Avoid reading the screen. Viewers can read. Tell them what to notice and why.
The pauses
Leave a short silence after each click so the viewer sees what changed. In the edit, you can also cut waiting time, such as loading screens.
The recap
A recap helps people who skim. Keep it to the step names. If you show it as text on screen, viewers can pause and copy it.
Script versus bullet points
Do you need a full word for word script? It depends.
| Style | Good for | Watch out for |
|---|---|---|
| Full script, read aloud | Precise, short videos; voice over after recording | Can sound stiff if you read it flat |
| Bullet outline, speak freely | Natural tone, longer demos | You may ramble or forget a step |
| Hybrid: full hook and recap, bullets for the steps | Most tutorials | Needs a little practice |
The hybrid works well for most people. Write the first and last lines in full, because those are the hardest to improvise, and use bullets for the middle.
Record in a way that keeps the script simple
- Rehearse once without recording. You will find the missing step.
- Record in short pieces. One step at a time is easier to redo than one 10 minute take.
- Add the voice later if you prefer. Some creators record the screen first and then read the script as a voice over. That lets you do the clicks without talking at the same time. MotionShine's editor has a voice over lane for this.
- Cut and tighten. After recording, remove pauses and mistakes. See video editing tips for screen recordings.
MotionShine is made by the maker of this site. It is a free Mac screen recorder with auto zoom on clicks, a smooth cursor, and an editor that has text, pictures, music lanes, voice over and on-device captions. You can add click effects and motion blur. That fits the two column script above: the "zoom on" notes in the right column are what auto zoom does for you.
It runs on Mac only. The free version exports up to 720p at 30 fps with no watermark and no time limit, and Pro unlocks 1080p, 1440p, 4K and 60 fps. If you work on Windows, or you want live streaming scenes, it is not the right tool. The built-in Shift-Command-5 recorder, described in how to record a video on Mac, is enough for a simple first video.
After the script: title, chapters and captions
- Title: use the task words from your script's title line.
- Chapters: your step names are your chapter names. The YouTube chapters generator can format timestamps.
- Captions: your script is already written text, so it is a head start on captions. Check any automatic captions against the script for names and menu items.
If you are starting a channel, see how to make a YouTube channel for screen recordings.
FAQ
How long should a tutorial video be?
As long as the task needs and no longer. Many tutorials fit a single task in a few minutes. If a script has more than seven steps, think about splitting it into two videos.
Should I read my script word for word?
You can, but it can sound flat. A hybrid works for most people: write the hook and recap in full and use bullet points for the steps.
What is the difference between a script and an outline?
A script has the exact words you will say. An outline lists the points and leaves the wording to you. The template above can be used either way.
Do I need a script for a screen recording?
You do not need one, but a short one saves time. It stops you from forgetting a step and helps you cut waiting and repeating.
Where should I put the call to action?
At the end, after the viewer has the result. One next step is enough. A long list of requests at the start delays the part they came for.
How do I script a demo instead of a tutorial?
A demo shows what a product does, not how to do a task. Swap the steps for three or four moments that show value, and keep the same hook, check and next step.
