How to Script an App Preview Video That Converts

Why most app previews do not convert

Most app previews are built as feature tours. They open with the app logo, show a list of screens, and end with the app icon. They are technically compliant and visually acceptable — and they do almost nothing for conversion.

The problem is structure. Without a deliberate narrative arc, even well-produced footage fails to move users from interest to install.

The Conversion Narrative Framework

Every preview we produce at W App Videos is built around a four-part structure called the Conversion Narrative Framework. It works because it mirrors how users actually make install decisions — not by evaluating features, but by feeling confident that this app will solve their problem.

Part 1 — Hook (0–3 seconds)

The hook has one job: stop the scroll and create immediate relevance.

In practice, this means opening with either the problem your app solves or the outcome your app delivers — in the clearest, most specific terms possible. Not "the best productivity app." Something like: a user in a recognizable situation, the app opening, the friction disappearing instantly.

Three seconds is not much time. But it is enough to create a moment of recognition: this is for me.

Part 2 — User Benefits (3–18 seconds)

The middle section is where you show the app working. But the goal is not to show everything — it is to show the right things in the right order.

Choose two or three user outcomes, not features. The difference: a feature is "real-time sync across devices." The outcome is "open the app on your phone and everything is already there." Show the outcome. The feature is implicit.

Each benefit should be demonstrated in no more than four or five seconds. If a screen requires more than that to understand, it is probably not the right screen for a preview.

Part 3 — Future Positive State (18–24 seconds)

This is the most underused part of the structure. The goal is to show the user what life looks like after they use the app — not just what the app does, but what becomes possible.

For a fitness app, this might be a completed workout log, a streak reached, a goal hit. For a finance app, it might be a clear dashboard with everything organized. For a note-taking tool, it might be an inbox at zero.

This section does not have to be long — six seconds is enough. But it shifts the video from "here is the app" to "here is who you become."

Part 4 — Call to Action (24–30 seconds)

The closing frames should reinforce the core promise one more time, clearly and simply. This is where many previews end abruptly or fade out on a logo. Instead, close with the app's clearest value statement and let the last frame be in-app footage — not a title card.

Voiceover vs text overlays

Both work. The decision depends on your app and your audience.

Voiceover is effective when the benefit needs explaining — when watching the app without audio context leaves users uncertain about what they are seeing. It adds personality and can guide the eye.

Text overlays are effective when the app is visually self-explanatory and the overlay just needs to name what is happening. They work well in competitive categories where users mute videos by default.

A common approach is a light voiceover combined with on-screen text for key moments — redundancy that works in both muted and unmuted states.

Practical scripting tips

• Write the script before you record. Trying to find a narrative in existing footage is much harder than recording to a plan.
• Time your script aloud. Read it at the pace you would want a voiceover to deliver it. Adjust until it fits 28 seconds comfortably.
• Choose your single strongest user outcome and build everything around it. Sub-narratives weaken the core message.
• Assume the user will watch muted. Make sure the footage communicates value even without audio or text.