A useful YouTube Shorts script template does four jobs: introduces one specific problem, shows what causes it, demonstrates an answer, and ends with a payoff. For a 30-second narrated Short, start with roughly 60–75 spoken words, then time the actual voice. That range is a planning estimate based on 120–150 words per minute, not a YouTube requirement or a promise of better reach.
Write the narration and visual plan together. A sentence can sound good on paper while leaving the screen with nothing useful to show.
The YouTube Shorts Script Template
Use this as a first draft for one practical tip, small explanation, or before-and-after demonstration. The timing is a starting allocation; change it after listening to the read.
| Section | Approximate time | What to write | What to show |
|---|---|---|---|
| Problem | 0–4 seconds | Name the specific mistake or question | The mistake, result, or object immediately |
| Explanation | 4–10 seconds | Explain the one detail the viewer needs | A close-up, comparison, or simple diagram |
| Demonstration | 10–24 seconds | Show the fix in a short sequence | Each action as the narration describes it |
| Payoff | 24–30 seconds | State what the viewer can now do | The finished result or a clear before-and-after |
Fill-in version: “Struggling with [specific problem]? [Concrete cause] is getting in the way. Try [first action], then [second action]. Here is [visible result]. Next time you [relevant situation], [one useful instruction].”
You do not need to say every placeholder out loud. If the opening image already establishes the problem, use the first line to explain it. If the demonstration makes the result obvious, let the final shot breathe.
A Complete 30-Second Script Example
This original example teaches a simple production habit: checking whether captions cover the subject. It needs no presenter and can be made with a screen recording or a deliberately simple mockup.
| Scene | Spoken script | Visual direction |
|---|---|---|
| 1 | Your captions can hide the exact thing you want people to see. | Show a product close-up with a caption covering the product. |
| 2 | Before you export, pause on the busiest frame. | Freeze the frame and highlight the overlap. |
| 3 | Move the caption away from the subject, then check the next shot. | Reposition the caption and cut to a wider shot. |
| 4 | A position that works here might cover something important there. | Show why the same position blocks a detail in the second shot. |
| 5 | Watch once with sound off. Can you follow the action and read every line? | Play the corrected sequence silently, then hold on the clear result. |
The narration contains 56 words. At 150 words per minute, that is about 22 seconds before pauses. At 120 words per minute, it is about 28 seconds. A brisk read leaves room for the demonstration; a slower read leaves less space for pauses within a fixed 30-second slot.
That difference is why counting words is only the first check. Generate or record the voice, listen at normal speed, and shorten the copy if it feels rushed. You can remove “the exact thing” or simplify the final question without losing the lesson.
How Many Words Fit in a Short?
Use this calculation: spoken words ÷ words per minute × 60 = approximate narration seconds.
| Target runtime | At 120 words per minute | At 150 words per minute |
|---|---|---|
| 15 seconds | 30 words | About 38 words |
| 30 seconds | 60 words | 75 words |
| 45 seconds | 90 words | About 113 words |
| 60 seconds | 120 words | 150 words |
These are arithmetic estimates with continuous speech. Leave space for pauses, pronunciation, a visual reveal, and any moment when the viewer needs to read the screen. A technical explanation may need fewer words than a conversational story of the same length.
YouTube supports eligible square or vertical Shorts up to three minutes, but that maximum does not tell you how much script your idea needs. See the official Shorts length guidance for format eligibility. Our separate guide to choosing a Shorts runtime explores the length decision; this template focuses on writing within the time you choose.
Write a Hook You Can Deliver On
Start with something the viewer can recognize or inspect. “This caption hides the product” gives you a specific opening shot. “You have been making videos wrong” makes a much larger claim and leaves the viewer waiting for evidence.
Three useful opening patterns are:
- Visible mistake: “This label covers the button you need to press.”
- Direct question: “Which of these two frames is easier to read?”
- Demonstration first: “Watch what changes when we remove this line.”
Choose the opening after you know the ending. If the final scene cannot answer the first line, either change the promise or add the missing explanation.
Avoid adding a second hook halfway through a short lesson just because a template asks for one. Each new question consumes time you could spend answering the original question.
Keep Spoken Lines Separate From Scene Notes
For a faceless video, the script has two audiences: the person watching and the tool or editor building it. Give each audience its own text.
Narration: “Move the caption away from the subject.”
Scene note: “Show the caption shifting above the product. Keep the product visible throughout.”
Do not paste camera directions into a narration field and expect them to disappear. For EchoEtch, use the workflow overview to choose between narration with Images or Animated mix and a Full video. The narration options are suited to reading prepared copy; Full video uses a script, idea, or URL to make a short film, so review how the final wording fits the result.
Before rendering, remove any scene that repeats the same information without making it clearer. A new image should demonstrate the next step, show evidence, or establish a change.
Improve the Next Script With Your Analytics
YouTube's Shorts analytics guide distinguishes feed exposure from the share of viewers who choose to watch instead of swiping away. It also recommends comparing the same format and looking at both stronger and weaker uploads.
Use those reports to choose an editing hypothesis:
- People swipe away: Try a clearer first frame and a more specific first line on the next related video.
- People start but leave before the demonstration: Move the example earlier or remove setup that the image already explains.
- People rewatch one section: Check whether it is useful or confusing before repeating the technique.
YouTube's retention documentation explains that spikes can reflect rewatching or confusion. Some highlighted key moments require at least 60 seconds and 100 views, so do not expect every diagnostic label on a 30-second Short.
These observations suggest what to test. They do not prove that a single line caused a video's results. Keep the topic and format reasonably similar when comparing drafts, and write down the specific change you made.
Before You Render
- Can you describe the entire lesson in one sentence?
- Does the first shot show the subject immediately?
- Does every spoken claim have a clear meaning or visible example?
- Does the actual narration fit with room for pauses?
- Are scene directions excluded from the spoken text?
- Does the ending deliver the opening promise?
About this guide: The template, example, and production recommendations are original editorial guidance. Word counts use the stated speaking-rate assumptions. Platform documentation was checked on November 12, 2026; this is not a study of viral videos or a claimed retention benchmark.
Ready to use your draft? Create a video with EchoEtch and review the narration and visuals before publishing.