App Preview Videos That Convert

The honest disclosure up front

We build in public and we do not fake experience. On our own app, SparkQuest, we planned and scripted short promotional videos for TikTok as part of the go-to-market, but we have not produced or shipped an App Store preview video or a Google Play promo video. So everything below is drawn from Apple's and Google's current requirements and from public ASO research, not from a preview we personally cut and measured. When we ship one, we will update this guide with what actually happened. Treat this as the accurate map, not a travelogue.

Why a preview video is optional, and when it earns its place

Neither store requires a preview video, and plenty of strong listings run on screenshots alone. Published ASO research generally credits a good preview with a meaningful install lift, but the operative word is good. A preview that shows the real app in motion, resolves a clear value story, and is legible on a silent autoplaying loop can help. A produced ad with stock footage and little real interface does not help and can be rejected. So the honest sequencing is: nail your screenshots that convert first, since those do the heavier lifting and appear in search results, then add a preview when you can make a genuine one.

App Store preview specs (verified July 2026)

Straight from Apple's current App Store Connect requirements:

• Length: 15 to 30 seconds.
• Count: up to three previews per device family, shown before your screenshots.
• File size: 500 MB maximum.
• Frame rate: up to 30 fps.
• Format: H.264 in .mov, .m4v, or .mp4, or ProRes 422 HQ in .mov.
• Resolution: matched to the device slot. For current iPhone slots you export a portrait frame in the 1080 by 1920 range (some tools target 886 by 1920 for specific devices); for current iPad slots, 1200 by 1600 portrait. Confirm the exact accepted size for your target device in App Store Connect before you render, because like screenshots, previews are validated against expected dimensions.

The most important craft rule inside that 15 to 30 second window: show the app itself in the first three seconds. Apple's guidance and the ASO research both stress that the preview should be captured from the real app, not opened with a logo card or a produced intro. Viewers decide in the first beats, and a title card spends them.

The shape of a preview that converts

Working from published ASO benchmarks, the cut that performs looks like this:

1. Hook, 0 to 3 seconds. Real app on screen, doing the one thing that matters. No logo intro.
2. Core loop, 3 to 12 seconds. The main action performed cleanly, one motion, no menu tours.
3. Payoff, 12 to 20 seconds. The result, the finished artifact, the win state.
4. Close, final seconds. A calm end frame. Let the last state breathe.

Aim for 18 to 22 seconds even though 30 is allowed. Design for silent autoplay, because most previews play muted, so any critical message needs an on-screen caption, not a voiceover. And keep it to real captured footage; Apple wants the preview taken from the app, with only limited framing.

A storyboard you can shoot this week

Turning the shape above into a real cut, here is a concrete 20-second storyboard for a tool app like ours, timed to the beat:

• 0 to 3s: Open on the primary screen mid-use. For an idea app, the moment an idea resolves on screen. On-screen caption: the value in three words.
• 3 to 8s: One clean pass of the core action. A tap, a result. No settings, no menus, no tour.
• 8 to 14s: The detail payoff. The full result the user wanted, scrolling calmly so it reads.
• 14 to 18s: A second small win or the save-to-vault moment, showing there is more than one trick.
• 18 to 20s: A still, legible end frame. Not a hard sell, just the product at rest.

Write the on-screen captions first and let them carry the story silently, because the preview will autoplay muted for most viewers. If your message only lands with sound, it does not land.

Capturing and editing to spec

The pipeline is short and needs no budget. Record real footage from the iOS Simulator or a physical device; both produce the clean screen capture Apple wants, and a device recording captures real gestures and timing. Bring the clips into any editor, trim to 15 to 30 seconds (aim 18 to 22), add silent-friendly captions, and export to Apple's spec: H.264, up to 30 fps, under 500 MB, at the resolution your target device slot expects. One detail people miss: App Store Connect lets you choose the poster frame, the still shown before the video plays, so pick a frame that already tells the story rather than accepting a random or blank opening frame.

iPad and the multi-device reality

If your app runs on iPad, the preview is a separate export, not a scaled phone video. Current iPad slots expect roughly 1200 by 1600 portrait, against the iPhone slot's portrait frame in the 1080 by 1920 range. You can upload up to three previews per device family, so the honest minimum for an iPhone-and-iPad app is one strong iPhone cut and one iPad cut, each sized correctly. As with screenshots, a preview validated against the wrong dimensions is rejected, so confirm the exact accepted size in App Store Connect before you render the final file.

Video-specific rejection traps

The preview inherits every creative rule from screenshots and adds a few of its own:

• Too much produced footage. Apple wants the preview captured from the app; Google Play wants roughly 80 percent real app footage. A cinematic ad with a three-second glimpse of the interface fails the intent of the format.
• Pricing and earnings claims on screen. Same rule as screenshots. A "$10K/month" overlay in motion is no safer than one in a still.
• Features not in the build. A preview showing a screen the shipped app does not have is misleading content, a clean rejection.
• Wrong length or size. Under 15 or over 30 seconds, or off-spec dimensions, bounce before a human even watches.

Google Play is a different deliverable

Google Play's promo video is not an uploaded file, it is a YouTube link. It displays landscape at 1920 by 1080, and Google wants it to be predominantly real app footage, roughly 80 percent, rather than a produced commercial. Because it is a YouTube link shown in landscape, you generally cannot reuse your portrait App Store preview as-is; plan a separate landscape cut. The upside is that a YouTube-hosted video also lives on your channel and can be embedded elsewhere, so it does double duty beyond the listing.

When a preview is actually worth making

Because it is optional, the honest question is when it earns the day of work. A preview pays off most when the app's value is motion: a smooth interaction, an animation, a real-time result, a game, anything a still cannot show. It pays off least for apps whose value is a static layout that screenshots already capture fully. So the decision rule is simple: if a still screenshot tells the whole story, lead with screenshots and skip the video until launch is behind you. If the magic only reads in motion, the preview is where you show it, and it is worth doing well. That is the call we are making on our own app, screenshots first, a preview once we can show the strike in motion honestly.

Accessibility and the silent-play reality

Two craft notes that lift a preview from adequate to good. First, design for muted playback, because most previews autoplay without sound, so every essential message needs a legible on-screen caption rather than a voiceover carrying the point. Second, keep captions high-contrast and large enough to read on a phone in a search result, the same legibility bar your screenshots have to clear. A preview that only works with the sound on is a preview most people never understand.

Tools and the realistic effort

You do not need a production budget. The iOS Simulator and a physical device both capture clean screen recordings, which is the raw material Apple wants anyway. A basic editor trims to length, adds silent-friendly captions, and exports to the H.264 spec. The honest effort is a day once your app has a clean demo state to record, and it is genuinely optional, so it is a fair thing to defer until after launch when you have real usage to inform the story.

Where this sits in the journey

A preview video is one asset in the launch-assets stage, alongside screenshots and your store listing. For the full path from finished build to live on both stores, start at how to ship an app in 2026. Pair this with screenshots that convert and the exact screenshot sizes and specs, and if you are still upstream deciding what to build and validate, our idea to App Store in 30 days walks the sprint. When we cut our first real preview, this guide gets the first-person update it is honestly missing today.