AppWispr

Find what to build

Preview Video Scripts That Convert: 3 Proven 30s Templates + Storyboards for App Store & Ads

AW

Written by AppWispr editorial

Return to blog
S
AP
AW

PREVIEW VIDEO SCRIPTS THAT CONVERT: 3 PROVEN 30S TEMPLATES + STORYBOARDS FOR APP STORE & ADS

SEOMay 6, 20266 min read1,122 words

Stop guessing at app preview video creative. This post gives founders and product builders three battle-tested 30‑second script + storyboard templates (hook, demo, CTA) formatted for App Store and Play. Each template includes frame-level timing, guidance to meet platform specs, and a 90‑day A/B testing plan you can implement without an agency.

app-preview-video-scripts-30s-templates-storyboards-asoapp preview videoApp Store preview scriptGoogle Play promo videoASO video templatespreview storyboard

Section 1

Quick platform rules every founder must follow

Link section

Start here so you don’t waste creative time. Apple App Previews are strict: each preview must be a screen capture or faithful recreation of the in-app experience, and each file can be up to 30 seconds long. You can upload up to three previews per language and must match device resolution requirements. Apple also enforces codec, frame-rate, and audio channel expectations that commonly cause rejections if ignored.

Google Play differs: it uses a single promotional video (hosted via YouTube) for the store listing and accepts a broader range of creative styles, but the store displays only one video per listing. That means you should treat Play’s video as your single best store-level pitch and reserve multiple App Store previews for feature-specific slices.

  • Apple: up to three previews per language, each ≤ 30s; must be screen recordings or faithful UI simulations. (App Store Connect docs).
  • Google Play: single promotional video via YouTube link; broader creative flexibility but only one slot.
  • Practical: design each 30s asset so it also works as a 15s cut for ads.

Section 2

Template A — The Fast Hook (best for utility apps & productivity)

Link section

Why it converts: utility users decide fast — show immediate value in the first 3–5 seconds, then demo the core action, end with a clear CTA. This template is optimized for viewers who scan the listing and need instant clarity.

How to use: produce a 30s App Preview for Apple (and a 30/15s cut for ads). For Play, publish a single 30s promo that ramps the same hook into a concise feature demo.

  • 0:00–0:03 — Hook: 3s on-screen text + quick in-app action (e.g., “1 tap to X”).
  • 0:03–0:15 — Demo: 12s uninterrupted screen capture of the core flow (speed matters).
  • 0:15–0:24 — Benefit shots: 9s showing outcomes (before/after, data, notifications).
  • 0:24–0:30 — CTA: 6s with download prompt + one-sentence offer (e.g., “Start free”) and branded poster frame.

Section 3

Template B — Story Problem → Solution (best for consumer & lifestyle apps)

Link section

Why it converts: stories make features memorable. Open with a short relatable problem, pivot to the app solving it, and close on the lifestyle benefit. This pattern works well when emotional context sells retention.

How to use: keep on‑screen text short, rely on clear UI motion during the solution segment, and use real device captures to comply with App Store rules.

  • 0:00–0:04 — Situation: 4s establishing pain point with visuals (text + quick real-world footage).
  • 0:04–0:16 — Solution demo: 12s showing the app flow solving that pain (single linear task).
  • 0:16–0:24 — Outcome: 8s demonstrating the improved moment (smiles, saved time, achievement).
  • 0:24–0:30 — CTA + social proof: 6s with a concise CTA and a one-line metric or short review quote (avoid trademarked review text in App Store overlays).

Section 4

Template C — Feature Spotlight (best for complex apps and marketplaces)

Link section

Why it converts: when your product has multiple valuable features, pick the one that most directly increases installs (onboarding speed, a unique match algorithm, or lowest price). The viewer should leave knowing exactly what one thing your app does better than alternatives.

How to use: dedicate the first half of the video to a crisp walk-through of that single feature and the second half to context and CTA. Use callouts and minimal narration; Apple prefers on‑screen text and UI footage over staged video unless it clarifies the experience.

  • 0:00–0:06 — Feature hook: 6s showing the feature name + why it matters.
  • 0:06–0:18 — Step-by-step: 12s step-through of the feature in the real UI (highlight taps & swipes).
  • 0:18–0:25 — Context: 7s show how it fits into the user’s workflow or a marketplace outcome.
  • 0:25–0:30 — CTA: 5s final branded poster frame and platform-appropriate download phrasing.

Section 5

Production checklist & 90‑day A/B testing plan (what to measure and how)

Link section

Production checklist: export formats, exact device resolutions, 30fps, stereo audio track (even if silent), and a clean poster frame. Apple’s App Preview specs require exact display sizes for target devices; failures are common if you render at generic resolutions.

90‑day testing plan: run controlled A/B tests on store listings and ads in parallel. Use three variants: (A) Hook-first (Template A), (B) Story (Template B), (C) Feature spotlight (Template C). Track installs per-impression (CVR), first-week retention, and cost per install for paid ads. Swap in the best performing preview on each platform and iterate.

  • Export: follow App Store Connect exact resolution & file specs; App previews max 30s and must be screen-accurate. (See Apple docs).
  • Test setup: equal traffic splits (store experiments or third‑party A/B tools), minimum 2,000 impressions per variant to start seeing signal.
  • Primary metric: CVR (installs / listing views). Secondary: 7‑day retention and LTV proxies.
  • Timeline: week 0 — launch 3 variants; weeks 1–4 — collect early CVR; weeks 5–12 — validate retention; week 13 — declare a winner and scale.

FAQ

Common follow-up questions

How strict is Apple about the ‘screen capture only’ rule?

Apple requires App Previews to show actual in‑app experience or faithful recreations — the safest approach is to use direct screen captures or well-labeled UI simulations. Non‑UI footage is allowed sparingly (poster frames or illustrative B-roll) but primary content should be the app in use; check App Store Connect App Preview specifications before upload.

Can I reuse the same 30s file for App Store, Play, and ads?

You can reuse the core footage, but export variants: Apple requires exact device-resolved files for previews; Google Play needs a YouTube-hosted file. Also create a 15s cut for ad placements — shorter versions often perform better in paid channels.

What improvement in CVR should I expect after optimizing previews?

Benchmarks vary by category and baseline creative quality. A well-targeted preview that communicates value clearly typically moves CVR enough to justify testing (single-digit to double-digit percentage point improvements are common in ASO case studies). Measure with experiments and compare installs-per-impression before and after to quantify gains.

What common upload issues cause App Store rejections?

Typical problems: wrong resolution/frame-rate, missing stereo audio track (Apple expects audio channels even if quiet), use of non‑app footage as main content, and overlays with prohibited wording. Rendering to Apple’s exact specs and validating in a clean QuickTime player helps avoid rejections.

Sources

Research used in this article

Each generated article keeps its own linked source list so the underlying reporting is visible and easy to verify.

Next step

Turn the idea into a build-ready plan.

AppWispr takes the research and packages it into a product brief, mockups, screenshots, and launch copy you can use right away.