If you need a script template for a 30 second video ad, the fastest path is a timed structure: hook (0-3s), problem (3-8s), solution with benefits (8-18s), proof (18-25s), and offer plus call to action (25-30s). Below is a copy-paste template you can fill in for any product, app, or service, along with the second-by-second logic behind each line and two fully written examples.
Why a 30-second video ad needs a script template
Thirty seconds is long enough to make a case and short enough to lose someone every few seconds. A template forces discipline: every line has to earn its place, and nothing gets added just because it sounded good in the moment. Without structure, most first drafts spend too long on setup and too little on the offer, or they repeat the same selling point three times in slightly different words.
A reliable template splits the 30 seconds the way a short play uses acts — setup, complication, resolution — and gives each act one job. That's true whether you're selling a physical product, an app, a service, or promoting a one-time event. The bones stay the same; only the details in the brackets change.
The anatomy of a 30-second ad: second-by-second breakdown
Before filling in any template, it helps to know what each stretch of time is actually responsible for. Here's the timing breakdown that holds up across product ads, app ads, service ads, and even motion-poster style event promos.
| Time | Section | Job it does | Rough word count |
|---|---|---|---|
| 0-3s | Hook | Stop the scroll with a bold claim, a question, or a visual pattern break | 5-8 words |
| 3-8s | Problem | Name the pain point so the viewer feels understood, not sold to | 12-18 words |
| 8-18s | Solution + benefits | Show the product doing its job; state 2-3 concrete benefits, not features | 25-35 words |
| 18-25s | Proof | Add a specific detail, a before/after, or a reason to believe | 15-20 words |
| 25-30s | Offer + CTA | State the offer plainly and tell the viewer exactly what to do next | 10-15 words |
Add up the word counts and the total spoken script lands around 70-90 words for a comfortably paced voiceover. Go much higher and the read starts to feel rushed; go lower and the middle section probably lacks a real benefit. For a shorter, more compressed version of this same logic, the quick product video ad script formula is worth a look.
Script template for a 30 second video ad (copy-paste)
Copy the structure below into a doc and fill in the brackets. It works whether you're writing for a physical product, an app, a local service, or a one-off event.
- [0-3s] HOOK — "[Bold claim, a question about the pain point, or a visual pattern break described in words]"
- [3-8s] PROBLEM — "If you've ever [struggled with a situation], you know [specific frustration]."
- [8-18s] SOLUTION — "That's why [product name] exists. It [does X], so you can [benefit 1] and [benefit 2]."
- [18-25s] PROOF — "[Specific detail: a use case, a before/after, or a result]. Not a generic 'customers love it.'"
- [25-30s] OFFER + CTA — "Right now, [offer detail]. Tap [button] to [specific action]."
Keep the CTA concrete. "Shop now" works, but "Tap below to get 15% off your first order" gives the viewer a reason and an action in the same breath. If you're writing specifically for a physical product, the script template for a 30-second product ad goes deeper on product-only variations of this same structure.
Three variants depending on what you're selling
The five-part structure holds, but what you put in the hook and the middle section should shift depending on the offer.
| Ad type | Hook angle | Middle section focus | Proof/offer |
|---|---|---|---|
| Ecommerce product | Lead with the pain point or a close-up of the product in use | Demo the product solving the problem in 2-3 quick shots | Before/after or a specific use case; offer is a discount or bundle |
| App or software | Lead with the annoying manual task it replaces | Screen recording or mockup showing the flow in three steps | A workflow it replaces; offer is a free trial or a specific feature unlocked |
| Service or local event | Lead with what's happening and who it's for | Show the setting, the people, or the result customers get | Date, location or booking link as the offer; any urgency should be real, not invented |
Two sample scripts using this template
Example 1: a phone stand (ecommerce product)
- Hook (0-3s): "Your phone keeps falling off the dashboard. Again."
- Problem (3-8s): "Suction mounts stop sticking. Vent clips snap. You end up holding your phone at a red light."
- Solution (8-18s): "This stand locks on with a weighted base and adjusts to any angle, so your phone stays put on bumpy roads and tight turns."
- Proof (18-25s): "One clip shows the mount holding tight through a pothole test — no wobble, no drop."
- Offer + CTA (25-30s): "Get free shipping this week. Tap below to order yours."
Example 2: a task-management app
- Hook (0-3s): "Your to-do list has 40 items and none of them got done."
- Problem (3-8s): "Sticky notes fall off. Spreadsheets get ignored. By Thursday you've forgotten what Monday-you planned."
- Solution (8-18s): "This app turns your week into three daily priorities, syncs across your phone and laptop, and nudges you before you forget."
- Proof (18-25s): "Teams that switched say their Monday planning meeting shrank to a quick check-in instead of a long sit-down."
- Offer + CTA (25-30s): "Try it free for 14 days. Tap below to start."
Notice both scripts follow the identical skeleton — only the brackets changed. If you want more worked examples before writing your own, the video ad script examples for beginners post has five more scripts you can copy and adapt.
Common mistakes that break a 30-second script
- Spending too long on the hook's setup and leaving the offer for the last two seconds, where it gets cut off by captions or an end card.
- Writing the script as if it will always be heard — without on-screen text, the hook and offer can get lost for anyone watching on mute.
- Stacking three or four benefits in the solution section instead of picking the two that matter most to the buyer.
- Changing the CTA wording every time a new version is made, which makes it hard to tell which version of the script actually earned the result.
- Treating the proof section as optional. A specific detail — a use case, a before/after, a sensory detail — does more work than a generic claim like 'customers love it.'
How FrameNotion fits into this workflow
Once the script is solid, turning it into a finished vertical video is usually the next bottleneck. FrameNotion handles that step: paste a product or website link and FrameNotion AI writes a custom 30-second script following this same hook-problem-solution-proof-offer logic, then renders a 9:16 MP4 with an AI voiceover, a music track cut to the beat, and word-by-word captions — so the ad works whether someone is watching with sound or on mute. A finished ad is usually ready in about 10 to 20 minutes, and you can add a logo, up to six product images, and an offer or promo code before it renders.
If you're testing multiple hooks against the same body script, the Pro and Agency plans can generate A/B hook variants without rebuilding the whole ad, and every ad also exports as 4:5, 1:1 and 16:9 for other placements. See how it works on the features page, or start from a link if you'd rather see this template applied to your own product.
Frequently asked questions
How many words should a 30-second video ad script have?+
Aim for roughly 70-90 spoken words, which usually fits a 30-second voiceover at a comfortable pace. If your draft runs much higher than that, read it aloud with a timer — it will likely feel rushed once a voiceover is added.
Does the script need to be different for TikTok, Reels and YouTube Shorts?+
The core structure — hook, problem, solution, proof, offer — doesn't need to change across platforms since all three use the same vertical format and similar viewing patterns. What's worth testing per platform is the hook's tone: a more conversational feel versus a slightly more polished one. Test it rather than assuming one tone wins everywhere.
Should I write the voiceover script first or the on-screen captions first?+
Write the voiceover script first, then let captions follow it almost word-for-word. Captions that paraphrase the voiceover create a small mismatch that's distracting, even when neither version is wrong on its own.
How do I decide which hook to use if I have three options?+
Keep the rest of the script identical and change only the first three seconds across versions. Running the same body with different hooks isolates the one variable you're actually testing.
Is 30 seconds too short to fit in a product demo?+
No. A demo doesn't need to show every feature — pick the one moment that proves the product works, such as the fit, the click, or a before/after, and show only that, usually inside the 8-18 second window.