How Long Should an Explainer Video Be? Length by Channel and Goal
Practical length targets for landing pages, ads, YouTube, and sales—plus when shorter wins, when to go longer, and how to cut without losing the argument.
"How long should our explainer be?" is really two questions: How long can you hold attention, and how long do you need to complete one argument? The second number is often shorter than teams fear—if the script is focused. The first number is often shorter than teams hope—if the script is unfocused.
This guide gives practical length targets by placement, rules for cutting without gutting the mechanism, and signs you have the wrong runtime for your goal.
The one-argument rule
An explainer video should prove one claim or teach one model. Length follows from that scope.
If you need to explain three products, three personas, or three unrelated use cases, you do not need a longer video—you need more videos or a series.
Foundation: what is an explainer video. Structure: product explainer video structure.
Default length targets by placement
These ranges assume a focused B2B or prosumer explainer. Regulated or enterprise committee sales may justify the high end—if every beat earns retention.
Landing page hero video
Target: 60–90 seconds
Visitors clicked your headline; they are warm but impatient. Show problem, mechanism in two or three steps, differentiation, CTA.
If you are past two minutes on a homepage hero, you are likely touring features.
More: explainer video for landing pages.
Paid social and pre-roll
Target: 15–45 seconds
Hooks must land in three seconds. Often one mechanism beat plus CTA.
Create a dedicated cut; do not chop a ninety-second video at arbitrary timestamps.
Vertical variants: short-form explainers.
YouTube educational explainer
Target: 4–10 minutes for a single teachable unit
Length follows depth. Retention matters more than convention—six minutes of tight teaching beats ten with repetition.
Guide: educational explainer video for YouTube.
Sales meeting opener
Target: 2–3 minutes
Reps can pause for questions. Slightly more context is acceptable if visuals stay crisp.
In-app onboarding
Target: 30–120 seconds per task
Micro-explainers at the moment of confusion outperform one giant welcome video.
Email and nurture
Target: 45–75 seconds
Assume partial attention. Lead with outcome in thumbnail and first line of copy.
Why shorter often converts better
Shorter videos reduce:
- Cognitive load — fewer beats to track
- Commitment anxiety — "I do not have time for this"
- Production debt — faster to revise when product changes
Longer videos help only when each segment changes understanding. Padding destroys trust faster than brevity destroys detail.
When longer is justified
Extend runtime only when:
- The audience is warm (webinar attendees, existing users)
- The mechanism truly requires four steps that cannot merge
- Compliance needs careful qualifiers viewers must see
- You are teaching on YouTube and retention data supports depth
Do not extend because stakeholders each added "just one more thing."
The beat budget method
Allocate seconds before writing prose.
Example ninety-second SaaS landing explainer:
| Beat | Seconds |
|---|---|
| Hook | 8 |
| Stakes | 10 |
| Promise | 10 |
| Step 1 | 12 |
| Step 2 | 12 |
| Step 3 | 12 |
| Differentiation | 10 |
| Proof | 8 |
| CTA | 8 |
Total: 90. If script reads long, cut words—not steps—until it fits.
Outline tool: explainer video script outline.
How to cut without breaking the story
Cut in this order:
- Adjectives and throat-clearing — "innovative," "world-class," "we are excited to…"
- Duplicate proof — one stat, one logo row
- Secondary personas — save for another video
- Extended company history
- Fourth mechanism step — merge into step three
Do not cut the hook or CTA first. Do not merge visually identical mechanism beats—that creates retention valleys.
Reading time vs watch time
Spoken narration runs roughly 130–160 words per minute for clear explainers. Faster can work for shorts; slower for dense finance.
Rough word budgets:
- 30 seconds: ~70–90 words
- 60 seconds: ~140–160 words
- 90 seconds: ~210–240 words
- 2 minutes: ~280–320 words
If your word count exceeds budget, the video will run long unless you speed up—which hurts comprehension.
Practical notes for this topic
Aspect ratio and perceived length
9:16 vertical clips feel faster because frames are tighter and hooks are harsher. The same script may need a faster open in vertical even at equal duration.
16:9 landing cuts can carry slightly more context if typography is readable on desktop and mobile.
Format effects on length
Motion-graphics explainers often tighten well because visuals carry parallel information—you can say less when the diagram shows more.
Talking-head videos sometimes run long because filler creeps in between takes. Compare formats: explainer video vs talking head.
Signs your video is too long
- Retention cliff before halfway
- Comments say "get to the point"
- Sales skips the video because reps cannot spare time
- You struggle to summarize the takeaway in one sentence
Fix structure before you argue for runtime.
Signs your video is too short
- Viewers ask basic questions the video should have answered
- Mechanism is one vague sentence
- CTA conversion is low but watch-through is high—offer mismatch, not always length
Consider a second explainer for advanced depth, not stretching the first.
Testing length responsibly
If you have traffic, A/B test hero videos at sixty vs ninety seconds with the same core beats, not different messages.
On YouTube, compare retention curves across uploads with similar topics before chasing ten-minute defaults.
SaaS and product specifics
SaaS homepage explainers rarely need more than ninety seconds. Complexity belongs in docs, interactive demos, and segmented explainers.
Mistakes catalog: SaaS explainer video examples and mistakes.
Channel-specific cheat sheet
| Channel | Typical sweet spot | Notes |
|---|---|---|
| Homepage hero | 60–90s | Mechanism in three steps max |
| Product Hunt / launch | 45–75s | Faster hook; social proof light |
| LinkedIn feed | 30–90s | Captions essential; hook text on frame one |
| In-app tooltip video | 20–45s | One task only |
| Webinar recap | Avoid full replay | Re-cut to one insight |
| Investor update | 2–4 min | Warm audience; still need beats |
Use this table in briefing docs so stakeholders align before scripting.
Workshop: cutting a two-minute script to ninety seconds
- Highlight every adjective—delete half.
- Merge stakes into hook as one compound sentence.
- Combine steps that share one visual layout.
- Replace proof montage with one number.
- Read aloud at conversational pace; stop when over time.
If still long, you have two topics—split.
Voiceover pace and comprehension
Rushing narration to hit time targets hurts comprehension more than adding fifteen seconds of runtime. If words must be cut, cut concepts—not speaking speed.
Non-native audiences especially need clear pacing and on-screen anchors for new terms.
Practical notes for this topic
Series length strategy
Flagship explainer stays stable. Satellite videos can be shorter and sharper—thirty to sixty seconds each addressing one objection or use case.
Playlist order matters: concept → application → comparison → implementation tips. Do not randomize.
Runtime and word count reference
At ~150 words per minute spoken clearly:
| Runtime | Approximate words |
|---|---|
| 30 sec | 70–80 |
| 45 sec | 105–120 |
| 60 sec | 140–160 |
| 90 sec | 210–240 |
| 2 min | 280–320 |
| 3 min | 420–480 |
Use this when writers exceed timecode budgets.
Children's and general audience pacing
Simpler language can run slightly faster; dense B2B mechanism may need slower pace and more on-screen reinforcement—effective runtime creeps up even at same word count.
Practical notes for this topic
Executive summary vs full explainer
Executives sometimes want thirty-second "summary" and two-minute "detail." Produce two cuts from one outline—do not speed-read the long cut.
Summary cut: hook, outcome, CTA.
Detail cut: add mechanism and proof.
Same claims in both; different depth.
Stakeholder conversations about length
When a stakeholder asks for a longer video, ask which beat they feel is missing. If they cannot name a beat, they want presence—not length.
When they ask for shorter, identify which mechanism step they are willing to drop. Shortening without dropping a step means faster narration—which hurts comprehension.
Document agreed runtime on the outline approval email. Scope creep often arrives as "just one more example."
Legal and regulated runtime
Some disclaimers require minimum on-screen duration. Budget three to five seconds per disclaimer line. Regulated explainers run longer—not because teaching needs it, but because compliance does.
Plan disclaimer beats in outline so they are not crammed at end illegibly.
Pairing length with distribution spend
Paid distribution amplifies length mistakes. A two-minute video with a weak hook burns budget faster than a sixty-second cut with the same CTA.
If you are spending on ads, test a forty-five-second cut first. Scale spend only when retention and conversion justify longer storytelling.
Organic YouTube can reward longer teaching when each minute adds new understanding—not repetition.
Documentation and support tie-ins
Match explainer length to where it lives in the help journey. Tooltip videos should be under forty-five seconds. Academy courses can chain multiple explainers instead of one marathon file.
Link from video description to docs that go deeper; the video is the map, not the encyclopedia.
Runtime decision tree
Start with placement. Homepage hero? Default sixty to ninety seconds unless retention data on longer cuts wins.
Paid social? Start forty-five seconds maximum.
In-app single task? Thirty seconds target.
YouTube essay? Let outline depth dictate; cut ruthlessly in edit.
Only if tree points to two minutes AND you have proof each beat retains should you ship long.
Recording runtime during table read
Time the table read aloud at natural pace. Add ten percent for visual beats without words. That estimate beats guessing from page count.
Practical notes for this topic
When stakeholders cite competitor runtime
Competitor videos are not your script. Their audience, placement, and product complexity may differ. Use competitor work as inspiration for beats, not as runtime law.
If their video is three minutes and yours is ninety seconds, argue with retention and conversion data on your pages—not with imitation.
Benchmark your own uploads after thirty days live, then adjust length on the next cut.
Summary length targets by intent
Persuade on homepage: sixty to ninety seconds.
Teach on YouTube: six to ten minutes if retention supports.
Tease on Shorts: thirty to forty-five seconds.
Enable sales: two to three minutes with pause-friendly beats.
Write the intent on the outline header so reviewers do not argue runtime in a vacuum.
Final sanity check before export
Read total word count aloud one last time. If you are ten seconds over target, cut an adjective cluster—not a mechanism step.
Ship when the argument completes; perfectionism past ninety-five percent readiness rarely moves conversion.
Length is a constraint that serves clarity—not a target to max out for its own sake.
Frequently asked questions
Is 30 seconds enough for a product explainer?
Sometimes for retargeting or known audiences. Cold homepage visitors usually need enough mechanism to believe you—often sixty seconds minimum.
Should all explainers match the same length?
No. Match length to placement and argument. Series can mix lengths if each video has one job.
Does YouTube favor longer videos?
YouTube favors watch time and satisfaction. Long videos that retain win; long videos that bore lose.
How long should captions stay on screen?
Long enough to read comfortably—usually not more than one short sentence per caption card in motion graphics.
Can I speed up narration to hit a time target?
Slight pace increases are fine; chipmunk delivery hurts trust. Cut script instead.
What about multilingual versions?
Budget extra time for on-screen text reflow. German and French often need more characters per line—design layouts flexibly.
Practical notes for this topic
Related links
- Explainer videos
- Product explainer video structure
- Explainer video for landing pages
- Educational explainer video for YouTube
Test length with a tight first cut: AutoMotion Graphics generates motion-graphics explainers from your topic in 16:9 or 9:16—no talking head. Edit beats, export MP4, and shorten or expand when retention data tells you to.
Part of Explainer Videos: The Complete Guide for Marketers and Creators.