· ASO · 5 min read

App preview video vs screenshots — which converts?

App preview video vs screenshots — which converts?
TL;DR. Video wins where motion sells (games, fitness, video editors, music creation). Screenshots win where the install decision happens in 2 seconds off the first panel (banking, weather, notes, utilities). For most apps the right answer is one short video on top plus a strong static carousel — not video instead of screenshots.

Apple added App Preview videos in 2014 and most apps ignored them until ~2020. By 2026 the feature has earned its weight: the autoplay poster sits at the top of the App Store product page, larger than it used to, and a 30-second muted clip plays on first scroll. For some categories the video has become the single highest-conversion creative asset.

For other categories it does nothing.

Where video wins

Categories where motion is the product or close to it:

  • Games. The carousel is the trailer. Static screenshots can't communicate gameplay. Video almost always wins.
  • Fitness apps with workout-flow features. Showing the actual workout in motion sells better than static "demo workout" screenshots.
  • Video editors / camera apps. Output is video; show the output.
  • Music creation tools. Same logic.
  • AR / 3D / animation apps. Static screenshots flatten the value prop.

In these categories, published case studies from StoreMaven, AppTweak, and Mobile Action have reported meaningful tap-to-install lifts from adding a strong 15-30 second video — magnitudes vary by category and creative quality. Read their case studies for the specifics; we'd rather point at the source than restate a single percentage.

Where video loses (or doesn't help)

Categories where the install decision is fast and static:

  • Banking / finance utilities. Users look at the carousel for "does this bank handle my country / look legit". Video doesn't add information; static screenshots do.
  • Notes / productivity utilities. Same. Notion's video page probably converts about the same as their no-video page would.
  • Weather, calculators, simple tools. Watching a calculator in motion is not informative.
  • Reference apps (dictionaries, manuals, lookups). The user wants to see content depth, not motion.

In these categories, the time spent producing a 30-second video would have been better spent on a stronger static carousel.

Where it's category-dependent

Mixed verdict:

  • Social apps. Depends on whether the social value is conversational (chat — static fine) or visual (photo/video sharing — video helps).
  • Health tracking. Splits on whether the app's value is in the data (static wins) or the doing (video helps).
  • Travel. Photo-led carousels often beat video unless the app has unique motion content.

If you do ship a video

Apple's video specs (covered in detail on the video requirements guide) — 15-30 seconds, H.264, per-device-class dimensions, no marketing voiceover, no external URLs. The constraints are tighter than YouTube/Instagram ad video.

Three rules that hold up:

  • The poster frame matters more than the video. Most users see the poster frame and don't tap to unmute. Pick a poster frame that conveys value at a glance.
  • Don't try to demo every feature. One feature, shown well, in 15 seconds, beats six features rushed in 30.
  • Skip the intro card. The first 3 seconds should be the actual app in action, not a "WELCOME TO APPNAME" splash. Users skip slow-starts.

The realistic plan for most apps

  1. Ship strong static screenshots first. Carousel does most of the lifting.
  2. Add a video if your category benefits from it. Skip the video if it doesn't.
  3. Localize the carousel before localizing the video. Translated captions on static screenshots are cheap and high-impact. Localized videos are expensive and less impactful.
  4. A/B test video vs no-video if you have install volume for significance — categories vary.

What to read next

Open the editor →