highuniversal

App Preview Video

Also known as: Preview Video, App Video, 15-30 Second Video, Video Preview

Visual Assets & Creative

Definition

App Preview Videos are short, auto-playing video clips (15-30 seconds) that showcase app functionality in the app stores. They auto-play muted in search results (first position) and on product pages, providing dynamic visual communication of app value without requiring user interaction. Preview videos are a high-impact visual asset with mixed conversion effects: well-executed videos improve Conversion Rate|CVR by 5-15%, while poorly executed videos can decrease CVR by 5-10%. Video adoption is increasing as stores prioritize video-first galleries, making preview video optimization critical for ASO.

How It Works

Apple App Store

Technical Specifications:

  • Duration: 15-30 seconds (15-second videos most common)
  • Quantity: Up to 3 videos per locale per device type
  • Device types: iPhone and iPad (tested separately; videos shown on matching device)
  • Video codec: H.264 (MPEG-4 Part 10)
  • Frame rate: 24, 25, or 30 fps
  • Resolution by device:

- iPhone 15: 1170×2532 (portrait) or 2532×1170 (landscape)

- iPhone 14: 1125×2436 (portrait) or 2436×1125 (landscape)

- iPad Pro 12.9": 2048×2732 (portrait) or 2732×2048 (landscape)

  • Audio: Supported but videos auto-play muted in search results (sound only plays on product page)
  • File size: Maximum 500 MB per video
  • Submission method: Upload via App Store Connect

Playback behavior:

  • In search results: Auto-plays muted, loops continuously (first position only)
  • On product page: Shows play button; auto-plays muted with optional sound unmute
  • On home screen: Displays poster frame (first frame) as image
  • Device context: Only videos for matching device type shown (iPhone video on iPhone, iPad video on iPad)

Poster Frame:

  • The first frame of your video serves as the poster (thumbnail image)
  • Critical importance: users see this static frame before hover/play
  • Should communicate value prop clearly if video doesn't auto-play
  • Recommend designing first frame as standalone promotional image

Google Play Store

Technical Specifications:

  • Duration: 15-30 seconds recommended; maximum 45 seconds
  • Quantity: 1 video per listing
  • Video hosting: YouTube-hosted only (required; upload video to private YouTube channel, provide link)
  • Format: MP4, 3GP, MOV, AVI, or other YouTube-compatible formats
  • Resolution: 720p minimum; 1080p recommended
  • Aspect ratio: 9:16 (portrait) recommended; 16:9 (landscape) supported
  • Frame rate: 24-60 fps
  • Audio: Supported; plays with sound by default (user can mute)

Playback behavior:

  • In search results: Does NOT auto-play (thumbnail with play button shown)
  • On product page: Play button shown; requires user click to play
  • Streaming: YouTube handles hosting and CDN delivery
  • Compatibility: Works on all devices (web, app, TV)

Key limitation:

  • Google Play videos don't auto-play in search, reducing visibility compared to Apple
  • Video must be explicitly clicked to watch, lowering view-through rates

Amazon Appstore

Technical Specifications:

  • Video support: Limited compared to Apple and Google
  • Duration: 15-30 seconds recommended
  • Format: MP4 or similar
  • Hosting: Upload to Amazon Appstore system (not external hosting)
  • Quantity: 1 video per listing
  • Playback: Similar to Google Play (play button, requires click)

Limitation:

  • Amazon has lower traffic than Apple/Google, limiting video impact
  • Video support is less developed than other platforms

Video Hooks & Engagement Mechanics

First 3 Seconds Critical

Hook strategies for opening frames:

  1. Problem statement — show pain point your app solves

- Example: "Juggling too many apps?" (task management)

  1. Value prop flash — instant benefit statement

- Example: "Save 2 hours/week" (productivity)

  1. Visual surprise — unexpected or beautiful animation

- Example: app loading animation, transformation effect

  1. Human element — person smiling or reacting positively

- Example: user enjoying the app on phone

Best practice: Lead with emotional hook (1-2 sec), then show app in action (remaining 13-28 sec).

Sequential App Demo

Recommended structure:

  1. Seconds 0-3: Hook (problem or value prop)
  2. Seconds 3-8: First action (user takes primary action in app)
  3. Seconds 8-15: Feature showcase (show key feature working)
  4. Seconds 15-25: Benefits/outcomes (show result of using feature)
  5. Seconds 25-30: Call-to-action or final benefit statement

Example (meditation app):

  • 0-3: "Stressed?" (problem hook)
  • 3-8: User opens app, selects meditation
  • 8-15: Meditation session playing (guided audio visualization)
  • 15-25: User completes session, sees stats/badges
  • 25-30: "Feel calm. Download Calm." (CTA)

Design & Production Approaches

1. In-App Footage (Apple Preferred)

Characteristics:

  • Pure screen recording of actual app interface
  • Shows exactly what user will experience
  • No external footage, no actors, no staging
  • Apple's strict requirement: videos must show real app in action

Pros:

  • Transparent (shows actual user experience)
  • Easy to update (record new gameplay/features)
  • Cost-effective (no production crew needed)
  • Aligns with Apple's guidelines

Cons:

  • Can look boring if app UI is not visually engaging
  • May not communicate emotional benefits
  • Requires app to be functional and stable

Best practice for Apple: Pure in-app footage with strategic UI interactions, captions/overlays for benefit communication.

2. Lifestyle + In-App Hybrid

Characteristics:

  • Mix of lifestyle footage (person using phone) with actual app interface screens
  • Shows real-world context + actual functionality
  • Can include voiceover or text captions

Pros:

  • Emotionally engaging (human element)
  • Shows use context (when/where you use app)
  • Still transparent about actual app interface

Cons:

  • Requires production (filming, editing)
  • Apple allows lifestyle footage only if interspersed with app footage
  • Higher cost

Best practice for Google Play: Lifestyle opening + app demo works well since videos don't auto-play in search.

3. Text Overlays & Captions

Strategy:

  • Add benefit text on top of app footage ("Save 2 hours/week")
  • Use short, impactful captions
  • Maintain visual clarity (don't cover critical UI)

Guidelines:

  • Font: Sans-serif, bold, 24pt+
  • Contrast: Ensure readable on app background (use shadows or semi-transparent backgrounds)
  • Duration: Leave captions for 2-3 seconds
  • Placement: Bottom third of screen (avoid status bar area)

Example captions:

  • "Organize your life in seconds"
  • "Get back 10 hours/week"
  • "Connect with 5M+ users"

CVR Impact & Effectiveness

Positive impact scenarios (typical +5-15% CVR lift):

  • Well-produced videos with professional editing
  • Videos that clearly show app solving specific problem
  • Emotional hooks that resonate with target audience
  • App with complex UI benefit from video explanation
  • Category where video is expected (games, fitness, creative apps)

Negative impact scenarios (typical -5-10% CVR decline):

  • Low-quality or laggy video (suggests app performance issues)
  • Video showing features but not benefits (feature overload)
  • Talking head or external footage not clearly connected to app (confusing)
  • Video that's too fast or difficult to follow
  • Audio-focused videos without visual clarity (silent video viewers miss content)
  • Category where static screenshots are standard (users expect images, not videos)

Mixed/neutral scenarios:

  • Video of average quality
  • App with simple, intuitive UI (video doesn't add new understanding)
  • Video showing same information as screenshots (redundant)

Key insight: Video quality matters MORE than video presence. A poor video hurts more than no video.

Best Practices

  1. Hook viewers in first 3 seconds — videos auto-play muted in Apple search. Hook must be visual and instant. No logos or intro delays.
  1. Show app in action, not static — avoid static screenshots or talking heads. Movement and interaction grab attention in search results.
  1. For Apple: use in-app footage only — external footage, actors, and staged scenarios are against Apple's guidelines. Stick to real app interface and user interactions.
  1. For Google: lifestyle + app works — since videos don't auto-play in search, opening with lifestyle context (person using phone) improves engagement.
  1. Keep audio off for search visibility — design video to be compelling muted (since Apple auto-plays muted). Save voiceover for product page viewers who unmute.
  1. Design poster frame for maximum impact — first frame is critical. Make it benefit-focused if video doesn't auto-play, or attention-grabbing if it does.
  1. Avoid feature overload — show 1-2 core features max. Users retain 1-2 benefits, not 5.
  1. Use text captions sparingly — captions help communicate benefits but can clutter video. 2-3 captions max.
  1. Test video vs no video — use Product Page Optimization (PPO) (Apple) or Store Listing Experiments|SLE (Google) to test whether video improves or hurts CVR for your specific app.
  1. Monitor quality metrics — if video quality degrades (compression artifacts, lag), re-upload. Poor-quality video signals low app quality.
  1. Align with App Icon and Screenshot visual style — video should match icon colors, screenshot aesthetic, and brand identity.
  1. Consider seasonal variations — test different video messages (seasonal promotions, new features) via PPO/SLE.

A/B Testing Videos

Variables to test:

  1. Hook type — problem statement vs value prop vs visual surprise
  2. Pacing — slow vs fast-paced demonstrations
  3. UI vs lifestyle — pure app footage vs lifestyle context
  4. Music/audio — different soundtracks or voiceover styles (on product page where audio plays)
  5. Feature ordering — which feature to highlight first

Testing methodology (Apple PPO):

  • PPO allows testing videos (up to 3 variants + control)
  • Run for 1-2 weeks minimum
  • Measure CVR (install rate)
  • Google Play SLE does NOT currently support video testing (only supports graphics/descriptions)

Limitations:

  • Video testing is lower frequency than screenshot testing
  • Production cost makes rapid iteration expensive
  • Results take longer due to lower view-through rates
  • Consider pre-testing via video ads (YouTube, TikTok) before app store testing

Formulas & Metrics

Video CVR Impact:

CVR Lift from Video = (CVR_With_Video - CVR_Without_Video) / CVR_Without_Video × 100%
Range observed: -10% to +15%
Average (well-executed): +7-10%

Video visibility (Apple):

  • Auto-plays in first search result position
  • View-through rate: 40-60% for auto-playing videos (users see it)
  • Click-through to product page from search: 60-80% of those who see video

Comparison of CVR impact (typical):

AssetCVR Impact RangeNotes
[[App Icon]]10-25%Highest variance depending on design
[[Screenshot]]15-35%Multiple screenshots compound effect
Video5-15%Variable; quality dependent
Combination (optimized icon + screenshots + video)30-60%Multiplicative effect on total CVR

Examples

High-performing video strategies:

  1. Duolingo (Education)

- 0-2sec: Character mascot appears ("Ready to learn?")

- 2-8sec: User taps lesson, app shows interactive exercise

- 8-15sec: User completes lesson, gets rewarded with animation

- 15-30sec: Mascot celebrates, "Learn a language today"

- Result: +12% CVR from optimized video (per split test data)

  1. Tinder (Dating)

- 0-3sec: "Find your match" (text overlay on app screen showing profile)

- 3-15sec: Swipe interactions (left, right, super like)

- 15-25sec: Match notification animation

- 25-30sec: "Download Tinder"

- Result: Video drives high engagement due to instant action/reward loop

  1. Headspace (Meditation)

- 0-3sec: Calming visual (nature scene transitioning to app)

- 3-12sec: App meditation session playing (soothing visuals, animations)

- 12-25sec: Session completion stats (time, streak)

- 25-30sec: "Start meditating"

- Result: +8% CVR; emotional hook + benefit demonstration

Poor video patterns to avoid:

  • Static screenshots scrolling (why not use actual screenshot gallery?)
  • Voiceover-heavy with no visual movement (confusing when muted)
  • Feature list (showing 8+ features in 30 seconds)
  • External footage not clearly connected to app
  • Very low production quality (suggests low app quality)
  • Long intro or branding (hook is in first 3 seconds)

Dependencies

Influences (this term affects)

Depends On (affected by)

Platform Comparison

AspectApple App StoreGoogle Play StoreAmazon Appstore
**Max videos**3 per locale/device11
**Duration**15-30 sec15-45 sec15-30 sec
**Auto-plays in search**Yes (muted)NoNo
**Hosting**Upload to App Store ConnectYouTube (external)Amazon upload
**Video codec**H.264 requiredYouTube formatsMP4
**In-app footage required**YesNo (lifestyle OK)No
**A/B testing support**PPO (available)Not currentlyLimited
**Typical CVR impact**5-15%5-12%3-8%
**Production cost consideration**MediumMediumLow

Related Terms

Sources & Further Reading

#aso#glossary#visual-assets#video
App Preview Video — ASO Wiki | ASOtext