Thirty seconds is not a short video. It is a test of priorities. A viewer will have time to walk away understanding exactly one useful thing, so the working question is never "how do we squeeze it all in" but "what can we cut without losing the point." Hold that constraint and the explanation has to happen on screen, where it counts, instead of hiding inside a voiceover talking at triple speed.
Give the Video a Single Job
Write one sentence describing what the viewer should understand when the video ends. Something like: the clip keeps a charging cable within reach of the desk edge. That sentence does real work, because it hands the camera something concrete to show.
Then pick a separate next step, such as checking the product's dimensions. Keeping one message and one clear action aligned is the backbone of plain communication guidance, and it applies here: a thirty-second ad might want a visit, a short explainer might just want confusion gone. Neither format guarantees a conversion, and pretending otherwise is how teams start stuffing.
A Story Shape That Fits Thirty Seconds
The shape is simple: a question, a visible answer, a next step.
Open on the viewer's problem
Start somewhere recognizable. A cable slipping off the back of a desk lands instantly; innovative design does not. Show the friction in one shot. If the friction needs backstory to make sense, the problem you picked is too broad for this format.
Show the mechanism or the proof
Show what changes. The cable goes into the clip and stays within reach. For a service, show the sequence of actions; for a mission, show where a contribution actually goes. Animation can illustrate, but it cannot prove an unsupported claim. In the United States, rules against fake or misleading testimonials make invented customer praise a genuinely bad shortcut, not a clever one.
Close on one next step
Ask for an action the video itself justifies: inspect the dimensions, open the booking form, check the donation rules. Find out more is too vague to act on. And hold the final card long enough that a normal person can read it.
Spending the Thirty Seconds
Try four beats on a storyboard: six seconds for the problem, five for context, twelve for the demonstration, seven for the next step. These are planning slots, not laws. If something has to give, give the voiceover speed before you give the mechanism screen time.
For every frame, log the shot, the spoken line, the on-screen text, and the visual focus. Read the whole script aloud over rough frames and leave room for breaths and the final card. Vertical placements, like Shorts ads, tend to favor 9:16 assets, so check the framing early, before a vertical crop quietly hides the action you built the video around.
Three Original Thirty-Second Scripts to Study
All three are fictional, none are tested campaigns. Read each against a timer and adjust the shot holds to your own pace.
A product explanation
A made-up desk clip has to explain one physical action, not an entire product line. Seconds zero to six: a cable falls out of reach. Voiceover: the charger is here, the cable isn't. Six to eleven: a hand places the clip on the desk edge. Keep the end where you need it. Eleven to twenty-three: the cable slides into the channel and lifts out on demand. Slide it in, lift it out when it is time to charge. Twenty-three to thirty: hold on the product beside a laptop. Check the clip's size before choosing yours.
The sparse voiceover exists so the mechanism can be seen, not just heard. Board the cable's path in one close-up that keeps the hand and desk edge in frame, or the clip reads as a mystery object. Durability, universal fit, and charging speed are deliberately missing. Each would need evidence this video does not carry.
A process explanation
A small community studio explaining room reservations. Zero to seven: two people arrive for the same room. Not sure which room is free? Seven to twelve: the booking calendar. Choose a date and an open slot. Twelve to twenty-three: room details and a confirmation screen. Check the details, then confirm. Twenty-three to thirty: the next step. Start with the availability calendar.
Cancellation terms and fees are left out on purpose. Put them near the booking form unless one of them changes the decision before booking. And if you screen-record the flow, use a fictional booking; a real person's details have no business in a demo.
A mission explanation
A neighborhood seed library wants people to understand what it does. Zero to seven: sealed, labeled packets sitting unused. Extra seeds can still be planted. Seven to thirteen: a volunteer checks labels. Neighbors share labeled packets. Thirteen to twenty-three: packets organized for pickup. The library sorts them so others can find a variety to grow. Twenty-three to thirty: a clear destination. See what the library accepts.
This explains the exchange, not the impact. Keep labels legible enough that the sorting reads on screen. Avoid staged recipients presented as real beneficiaries, and remember that harvest and environmental claims need support you either have or do not.
Cut Anything Competing With the Point
Watch the rough cut with the sound off. Then listen to it with the picture hidden. Does each pass still explain the change? Captions should carry speech and meaningful sound cues, but captions cannot substitute for a demonstration that never got filmed.
If the cut feels crowded, remove an idea before you trim a pause. A scene-planning tool can propose a shorter draft in seconds, but claims, rights, timing, and platform fit still need a human pass. And one line never moves: synthetic people must not impersonate customers, staff, or experts.
Questions Teams Ask
How many words fit a thirty-second voiceover?
No fixed number. For visual-heavy scripts like these, thirty to sixty-five spoken words is a rough planning range, not a target. Time an actual read with pauses and the final card included. Names and unfamiliar terms slow delivery. Cut a claim before you make the speaker race.
Should the video open with a logo?
Usually not as a standalone beat. Let the brand appear on the product or the final card. A separate opener spends money before the viewer knows why to care, and paid-placement disclosure requirements still apply.
How does silent viewing change the build?
The visual sequence has to stand alone. Keep text readable over motion and test the mobile preview. Captions serve accessibility; the silent test checks whether the demonstration itself works.
How do you test comprehension before publishing?
Show the rough cut once to someone outside the project. Ask what changed and what they would do next, without explaining the brief. If they remember a side detail instead of the point, reorder the scenes.
Which aspect ratios to plan up front?
Start from the intended placement. A vertical social cut and a horizontal embed may need different compositions and text positions. Mark safe areas on the storyboard and preview every destination before production, not after.
The Takeaway
A thirty-second explainer succeeds by subtraction. One job, one visible mechanism, one next step, and the discipline to leave out claims you cannot support on screen. Draft it, read it aloud over rough frames, test it on someone who has never heard the pitch, and cut whatever competes with the point. The timer is fixed. The rest is yours to choose.
