App Store Preview Video Design Guide: From Script Planning to Conversion Optimization

Have you noticed that of two apps with the same features, the one with a video often gets two or three times the downloads? It's not your imagination: App Store data shows that apps with preview videos see an average 35% lift in conversion. Today let's talk about how to make a preview video that actually brings in downloads.

Why preview videos matter more than screenshots

Many developers think screenshots are enough and that video takes too much time and money. But user behavior gives them away: when users come across your app, they instinctively watch the video preview, even if they only watch the first three seconds.

That's not because users are impatient; it's because video can convey in 6–15 seconds what screenshots need 30 seconds to express. Users don't need to know how many features your app has; they just need one reason: "this app looks like it solves my problem".

So a preview video's core job isn't showing features; it's creating that instant feeling of "this is exactly what I need".

Technical specs: don't put effort in the wrong place

Before making a video, it's important to know the platform requirements; otherwise you finish a video only to discover you can't use it, which is demoralizing.

App Store video requirements:

• Resolution: portrait or landscape at the device-specific sizes Apple lists in its App Preview specifications (for example, 1080×1920 for portrait on some devices)
• Frame rate: 30fps is enough; don't force 60fps (files get too big)
• Duration: 15 to 30 seconds (we recommend close to 30 seconds for more information)
• File format: MOV or MP4
• File size: up to 500MB per video

Google Play's requirements are similar, with one key difference: Google Play supports up to 8 screenshots + 1 video, while the App Store lets screenshots and videos be shown together in sequence.

Tip: if your app is listed on several app stores, make the portrait video (9:16) first, then crop it to landscape (16:9) for other platforms. Portrait videos have a 40% higher completion rate on phones than landscape: users don't have to rotate their phones.

Script planning: more important than editing

I've seen too many teams pay agencies a lot to make videos that turn out to be lists of features, with dismal conversion. The problem lies in the script stage.

Step 1: Define the video's goal

Before creating any visuals, ask yourself: "After watching this video, what should users do?"

If your answer is "download", that's too vague. More specific goals are:

• Make users realize they have this need
• Make users believe this app can meet the need
• Make users believe this app is better than competitors

Step 2: Choose a story structure

Pick a structure that fits your app type:

Problem–solution (good for utilities)

0–3s: show the user's pain point ("Always spend ages fixing layouts?")
4–10s: show the app's solution ("Try this: one-tap layout")
11–20s: show core feature highlights
21–30s: call to action ("Download now and start creating")

Showcase (good for entertainment and design apps)

0–5s: strongest visual impact (your coolest finished result)
6–20s: feature highlights (3 core features, 3–5s each)
21–30s: brand tone + download prompt

Social proof (good for productivity and social apps)

0–3s: user testimonial or data endorsement
4–15s: real usage scenarios
16–25s: feature highlights
26–30s: download prompt

Step 3: Write a shot list, not a full script

A common mistake is writing long voiceovers. Users' attention lasts only a few seconds; there's no time to hear long lines.

The right approach: one shot + one keyword/phrase

For example:

• Shot: the app's main screen

• Caption: "One-tap beautify"

• Shot: a before/after comparison

• Caption: "Save 80% of your time"

• Shot: a user smiling while using the app

• Caption: "Loved by users"

Remember: the video is a silent salesperson. On the subway, at the office, in a mall, users will likely see your video muted. So key information must come through visuals and captions.

Production options: you don't need to spend big

Option 1: In-app screen recording (free, done in 2 hours)

iOS screen recording and tools like Gamebench on Android are convenient. After recording the basic content, add:

• Opening and closing captions
• Callouts for key features
• Background music (mind the licensing)

Recommended editing tools:

• CapCut (free and powerful)
• iMovie (built into iOS, quick to learn)
• Jianying (剪映, the Chinese version of CapCut, with lots of templates)

Option 2: Live-action scenes (for teams with a budget)

For education, fitness and lifestyle apps, videos with real people using the app usually convert 20–30% better than pure screen recordings.

You don't need a professional crew; a phone + fill light + gimbal can produce footage above the passing line. The keys:

• Scenes should feel real (not too much like an ad)
• Speech should sound natural (like a friend's recommendation, not a sales pitch)
• Show the results (let users "see" the value)

Option 3: Animated demos (for complex features)

If your app's features are abstract (such as data analysis or code editors), consider an animated demo. Lottie animations and After Effects templates can produce good results.

This option costs the most, though, so test the conversion of a pure screen-recording version first before deciding whether to invest more.

Details decide conversion: easily overlooked points

The opening: the first 3 seconds decide whether users keep watching. Don't open with a logo animation; get straight to the point. The worst video I've seen spent its first 5 seconds on a company introduction.

Captions: always add them. Whether or not users are muted, captions make information land more efficiently. Make them large enough, with colors that contrast with the background.

Music: choose light, upbeat background music, lower in volume than voice or captions. Avoid overly hyped electronic music, which makes users feel "this app is noisy".

The download prompt: always end with a clear call to action. But avoid cold phrases like "Click to download"; "Get started" or "Try it free" feels more natural.

A/B testing: not testing is gambling

Finally, the most important point: always test.

App Store Connect lets you upload up to three app previews, and you can compare different versions with Product Page Optimization. If your budget allows, test:

• Different story structures
• Different openings
• Different background music
• Different lengths (15 seconds vs 30 seconds)

Google Play's A/B testing is more powerful, showing you the conversion difference between versions directly.

My experience: for the same app, different video versions can differ in conversion by 50% or more. So don't think testing is a waste of time: get it right and doubling downloads isn't a dream.

Final thoughts

Preview videos aren't rocket science; the hard part is thinking from the user's perspective. Who are your users? What do they care about? In what situation would they download your app?

Answer those three questions and your video is half done. The other half is execution and testing.

If making a video feels like too much trouble, or you don't have a design team, try an App Store preview video generator. These tools can usually create motion effects from your screenshots automatically, saving time and effort. Of course, for the best results, we still recommend polishing the details yourself.

That's it for today. If you run into problems making your preview video, leave a comment and let's discuss.