An explainer video script template follows six parts: hook, problem, solution, how it works, proof and call to action. At the average speaking rate of 150 words per minute, a 30-second video holds about 75 words, a 60-second video about 150 and a 90-second video about 225. Build yours below, section by section, and watch the word budget as you type.
Key Takeaways
- Word budgets: at about 150 words per minute, 30, 60 and 90 seconds hold about 75, 150 and 225 words. The templates start well under that, so your own details, pauses and music fit.
- Structure: hook, problem, solution, how it works, proof, call to action. The 30-second version drops the proof; the 90-second version adds an objection.
- One idea per video: a longer video should add proof, not more features.
- Edit in place: every section on this page is editable, and its label shows the live word count against its time budget.
- Write for mute: Chrome always allows muted autoplay, so put the hook and web address on screen as text.
- Plan captions early: WCAG success criterion 1.2.2 requires captions for prerecorded video with audio at Level A, and your final script is the best starting point for them.
How do you build an explainer script section by section?
- Fill in your details in the boxes below. Nothing is sent or saved.
- Pick a length in the builder. Your details appear in every section.
- Edit any section by clicking in it. The label turns red when the section runs over its time budget.
- Copy the full script and paste it into Kveeky to hear it.
Explainer video script builder: 30, 60 and 90 seconds
Choose a length. Each label shows the words in that section, the spoken length at 150 words per minute, and its time budget. Click inside any section to rewrite it; the count updates as you type. Highlighted placeholders count as one word until you replace them. The last 2 tabs hold scripts for other use cases, and hooks and calls to action you can swap in.
30-second explainer script, section by section
A 30-second explainer carries one idea. Skip the long set-up: name the problem, show the answer, and ask for one action. The time budget for each section is in its label (Hook 4 s, Problem 7 s, Solution 8 s, Steps 6 s, Action 5 s); the total is 30 seconds.
1. Hook 4 words · ≈ 2 s of 4 s
2. Problem 14 words · ≈ 6 s of 7 s
3. Solution 13 words · ≈ 5 s of 8 s
4. Steps 8 words · ≈ 3 s of 6 s
5. Action 5 words · ≈ 2 s of 5 s
Full 30-second script 44 words · ≈ 18 s of 30 s
60-second explainer script, section by section
A 60-second explainer has room for one idea and a short proof. Add a how-it-works step list and a line of evidence. The time budget for each section is in its label (Hook 6 s, Problem 10 s, Solution 12 s, Steps 16 s, Proof 8 s, Action 8 s); the total is 60 seconds.
1. Hook 8 words · ≈ 3 s of 6 s
2. Problem 19 words · ≈ 8 s of 10 s
3. Solution 21 words · ≈ 8 s of 12 s
4. Steps 17 words · ≈ 7 s of 16 s
5. Proof 8 words · ≈ 3 s of 8 s
6. Action 16 words · ≈ 6 s of 8 s
Full 60-second script 89 words · ≈ 36 s of 60 s
90-second explainer script, section by section
A 90-second explainer can tell a small story. Open with a scene, answer the biggest objection, and give the viewer a clear next step. The time budget for each section is in its label (Hook 8 s, Problem 14 s, Solution 14 s, Steps 24 s, Proof 12 s, Objection 10 s, Action 8 s); the total is 90 seconds.
1. Hook 15 words · ≈ 6 s of 8 s
2. Problem 28 words · ≈ 11 s of 14 s
3. Solution 28 words · ≈ 11 s of 14 s
4. Steps 44 words · ≈ 18 s of 24 s
5. Proof 19 words · ≈ 8 s of 12 s
6. Objection 18 words · ≈ 7 s of 10 s
7. Action 16 words · ≈ 6 s of 8 s
Full 90-second script 168 words · ≈ 67 s of 90 s
Explainer scripts by use case
The same structure works beyond product pages. Swap the proof for whatever your viewer trusts most. Each label shows the live length against the video length.
New feature launch, 30 seconds 68 words · ≈ 27 s of 30 s
Local or service business, 30 seconds 56 words · ≈ 22 s of 30 s
Internal process or onboarding, 60 seconds 141 words · ≈ 56 s of 60 s
Hooks and calls to action you can swap in
Keep the hook to 12–15 words so it fits the first 5 seconds. Keep the call to action to one step.
Hook: question 10 words · ≈ 4 s of 6 s
Hook: before and after 10 words · ≈ 4 s of 6 s
Hook: "you're not alone" 11 words · ≈ 4 s of 6 s
Call to action: free start 11 words · ≈ 4 s of 8 s
Call to action: book a demo 16 words · ≈ 6 s of 8 s
Words in square brackets without a highlight are details only you know. Replace them before you generate the audio, and only use proof and quotes you can check.
Script ready? Paste it into Kveeky, pick a voice, set the speed so it lands on 30, 60 or 90 seconds, and download an MP3 or a WAV for your video editor.
Voice your explainer freeHow many words fit in each explainer length?
Use this as your budget before you write, and keep a little under it for breaths, music and on-screen moments. For other lengths or speeds, use the words to minutes calculator.
| Video length | Words at 150 wpm | Words at 130 wpm (slower, clearer) | Sections in the template |
|---|---|---|---|
| 30 seconds | 75 | 65 | 5 |
| 60 seconds | 150 | 130 | 6 |
| 90 seconds | 225 | 195 | 7 |
Which explainer video length should you choose?
| Length | Best for | Leave out |
|---|---|---|
| 30 seconds | Social ads, one feature, a homepage loop | Step-by-step detail and long proof |
| 60 seconds | Homepage, landing page, sales email | More than 3 steps or features |
| 90 seconds | Products with setup steps, onboarding, internal processes | A full feature tour: link to a demo instead |
Word budgets use the average US speaking rate. The section timings in the templates are our editorial guidance, not a platform rule.
How do you write each section?
- Hook (first 5 seconds). A question or result in the viewer's words. Save your product name for later.
- Problem. One or two concrete costs, such as lost hours or missed sales. Skip the market overview.
- Solution. Name the product once and say what result it gives, and for whom.
- How it works. 3 steps, one short sentence each. Show each step on screen as the voice says it.
- Proof. One real result, customer name or quote you have permission to use. Never invent numbers.
- Call to action. One next step. Keep the web address on screen while the voice says it.
Does your own script fit its length? Paste it and check
Paste a script you already have. The counter shows the live word count, the spoken length at your chosen pace and the word budget for your video length.
What goes on screen while the voice speaks?
Write the script first, then plan the picture around it. This storyboard shows how the 60-second template maps to visuals. The seconds are the section budgets from the builder above.
| Time | Section | The voice says | On screen |
|---|---|---|---|
| 0–6 s | Hook | The question about the problem | The problem, shown large and simple |
| 6–16 s | Problem | Why the old way fails | Two or three quick cuts of the pain |
| 16–28 s | Solution | What your product does | Product name and the main screen |
| 28–44 s | How it works | Three steps | One screen per step, numbered |
| 44–52 s | Proof | One result or quote | A customer name, logo or figure |
| 52–60 s | Call to action | Where to go | Web address, big and still |
Pre-record checklist Brief
Write for the ear. Read each section aloud, cut any sentence you run out of breath on, and see our guide to pauses, emphasis and pacing for shaping the read. If the explainer also goes out as a podcast clip or audio ad, the podcast intro and outro templates show how to adapt the same lines for audio only.
How do you write for viewers watching on mute?
An explainer that autoplays on your page usually starts without sound. Chrome’s autoplay policy always allows muted autoplay, while autoplay with sound needs the viewer to have interacted with the site first. So the first seconds must make sense with no audio at all.
| Do this | Why it helps |
|---|---|
| Put the hook on screen as text, too | Muted viewers get the point before they turn on sound |
| Match each “how it works” step to one scene | The picture and the voice tell the same story |
| Use your final script as the caption file | WCAG 2.2 success criterion 1.2.2 (Level A) asks for captions on prerecorded video with audio |
| Keep the website on screen during the call to action | Viewers can read it even if they can’t hear it |
This is general information, not legal advice.
How Kveeky helps you voice an explainer video
Kveeky turns a finished script into a voice read in minutes, so you can hear two versions before you record anything on screen.
Voice your explainer free
Sign up in seconds. No credit card needed.
See AI voiceover for explainer videos and product demo voiceovers for more on voices that suit these videos, or read the English text to speech page to pick an accent. The plans and pricing page lists what each plan includes, and the voiceover cost calculator compares the cost of a human voice actor. For a deeper look at the 60-second format, read the 60-second product demo script framework and explainer video voiceover tips.
Frequently asked questions
How long should an explainer video script be?
As long as the idea needs, and no longer. A 30-second video suits one idea, 60 seconds adds a short how-it-works and proof, and 90 seconds adds an objection and a clearer story. At 150 words per minute that is about 75, 150 and 225 words.
How many words is a 60-second explainer video script?
About 150 words at the average US speaking rate of 150 words per minute. Aim for 120 to 140 so there is room for pauses, music and on-screen moments.
What is the structure of an explainer video script?
Hook, problem, solution, how it works, proof and call to action. Shorter videos drop the proof; longer ones add a section that answers the biggest objection.
Should I write the script before the visuals?
Yes. The script sets the length and the order of ideas, and the visuals can then follow each line. Changing the words later means redoing the animation or edit.
Should an explainer video work without sound?
Yes. Chrome always allows muted autoplay, so a video that autoplays on your page may start with no sound. Put the hook and website on screen, and add captions made from the final script.
Can I use an AI voice for an explainer video?
Yes. Paste the script into Kveeky, choose a voice, adjust the speed, and download an MP3. Use a paid plan if the video promotes a business, and check each platform’s rules on labelling AI voices before you publish.
Sources
- Average speaking rate of about 150 words per minute: National Center for Voice and Speech, “Voice Qualities”, retrieved 16 October 2026.
- Muted autoplay always allowed, autoplay with sound after interaction: Chrome for Developers, “Autoplay policy in Chrome”, retrieved 17 October 2026.
- Captions required for prerecorded audio in synchronized media, Level A: W3C, “Understanding Success Criterion 1.2.2: Captions (Prerecorded)”, retrieved 16 October 2026.
- Kveeky formats, plans and rights: Kveeky pricing, retrieved 16 October 2026.