App Store Screenshots vs App Preview Video: Which Converts Better?
A data-driven comparison of App Store screenshots versus app preview videos, including conversion benchmarks, category-specific recommendations, and when to use each.
Every App Store listing can include both screenshots and an app preview video. But which one actually drives more downloads? It is a question that divides developers, and the answer is more nuanced than most people realize.
The short version: screenshots consistently outperform video in conversion rate for most app categories. But there are specific categories and situations where video wins decisively. Understanding when each format shines and how they work together lets you build a listing that converts at its maximum potential.
This guide presents conversion data comparing screenshots and video, breaks down the auto-play behavior that affects user experience, and provides category-specific recommendations so you can make the right choice for your app.
Screenshots vs Video: The Conversion Data
The data comes from A/B tests run by developers using Apple’s product page optimization tools, supplemented by aggregate data from ASO platforms. Here is what the numbers show:
| Metric | Screenshots Only | Video + Screenshots | Video Only |
|---|---|---|---|
| Average conversion rate (free apps) | 6.2% | 5.8% | 4.1% |
| Average conversion rate (paid apps) | 3.1% | 3.4% | 2.0% |
| Time spent on product page | 8-12 seconds | 15-25 seconds | 12-18 seconds |
| Scroll depth (% who see screenshot 4+) | 35% | 28% | N/A |
| Impression-to-view rate in search | 32% | 29% | 27% |
The surprising finding: for free apps, screenshots-only listings actually convert slightly better than listings with video. For paid apps, the combination of video and screenshots performs best.
Why Screenshots Often Win
- Faster information density. Users can scan 3-4 screenshots in the time it takes a video to auto-play its first 5 seconds.
- User control. Screenshots let users swipe at their own pace. Video forces a linear experience.
- Auto-play friction. On cellular data, videos do not auto-play, showing a static poster frame instead.
- Clarity at a glance. Well-designed screenshots with captions communicate value instantly.
Why Video Wins in Some Categories
| Category | Video Advantage | Why |
|---|---|---|
| Games | Strong | Gameplay footage is expected and compelling |
| Photo/Video editors | Strong | Showing the editing process demonstrates value |
| Music creation | Moderate | Audio-visual apps benefit from showing the experience |
| AR apps | Strong | AR is difficult to convey in static images |
| Animation tools | Moderate | Movement and creation process is the selling point |
| Social apps | Weak | Screenshots show the UI more effectively |
| Productivity | Weak | Users want to see the UI, not watch it |
| Utilities | Weak | Simple concepts explained faster in screenshots |
How Auto-Play Behavior Affects Performance
The auto-play behavior of app preview videos differs across contexts, and this significantly affects their performance:
| Context | Auto-Play Behavior | Sound | Impact |
|---|---|---|---|
| Search results (Wi-Fi) | Auto-plays, muted | No sound | Can attract attention but delays screenshot viewing |
| Search results (Cellular) | Shows poster frame only | N/A | Video provides no benefit over screenshots |
| Product page (Wi-Fi) | Auto-plays, muted | Tap for sound | Full video experience |
| Product page (Cellular) | Shows poster frame, tap to play | Tap for sound | Most users do not tap to play |
| Today tab / Features | Auto-plays, muted | No sound | Video gets premium placement |
The cellular behavior is critical. In many markets, a significant percentage of users browse the App Store on cellular data. For these users, your video is effectively invisible, replaced by a single static frame.
The Poster Frame Problem
When a video does not auto-play, users see the poster frame, which is the first frame of your video. If your first frame is not as compelling as your first screenshot, video is actively hurting your conversion rate on cellular connections.
| Poster Frame Quality | Impact on Conversion |
|---|---|
| Strong (clear UI, benefit text) | Neutral to slightly positive |
| Weak (loading screen, splash screen) | Negative compared to screenshots |
| Black or generic | Significantly negative |
Always design your video’s first frame as if it were a screenshot. It might be the only frame many users see.
When to Use Video
Based on the data and category analysis, here is a decision framework:
Strong Yes (Use Video)
- Your app is a game (gameplay footage is expected by users)
- Your app has complex interactions that are hard to convey in static images
- Your app produces visual output (photo/video editing, animation, design)
- Your app uses AR, spatial audio, or other experiential features
- You have the resources to produce a high-quality 15-30 second video
Probably Not (Skip Video)
- Your app is a utility with simple, clear functionality
- Your app’s value is in its content, not its interaction model
- You cannot produce a professional-quality video
- Your app’s UI is visually simple (text-heavy, list-based)
- Your screenshots already communicate your value proposition effectively
Conditional (Test It)
- Your app is in a competitive category where differentiation matters
- Your competitors use video effectively
- You have a unique interaction model that benefits from demonstration
- You are unsure whether video would help (use A/B testing)
Video Production Tips
If you decide to use video, quality is non-negotiable. A bad video is worse than no video.
Technical Requirements
| Requirement | Specification |
|---|---|
| Duration | 15-30 seconds |
| Resolution | Must match device display (e.g., 1290x2796 for iPhone 6.7”) |
| Format | H.264, M4V or MP4 |
| Frame rate | 30 fps |
| Audio | Optional but recommended |
| File size | Under 500 MB |
| Content | Must show actual app footage (no rendered mockups) |
What to Show in 30 Seconds
You have 30 seconds maximum, but the first 5 seconds determine whether anyone watches the rest.
| Second Range | What to Show | Why |
|---|---|---|
| 0-5 | Your app’s hero moment | Hook the viewer immediately |
| 5-15 | Primary feature demonstration | Show the core value in action |
| 15-25 | Secondary features or results | Reinforce value, show breadth |
| 25-30 | Call to action or final impact | Leave a strong last impression |
Production Quality Checklist
| Element | Standard |
|---|---|
| Screen recording quality | Native resolution, no compression artifacts |
| Transitions | Clean cuts or simple transitions, no flashy effects |
| Text overlays | Brief, readable, benefit-focused (not feature-focused) |
| Pacing | Quick enough to hold attention, slow enough to understand |
| Demo data | Realistic, attractive, representative of actual use |
| Background music (optional) | Subtle, professional, properly licensed |
| Touch indicators | Show finger taps for clarity (built into screen recording) |
The Combined Strategy: Video + Screenshots
For apps where video makes sense, the optimal approach is combining video with strong screenshots. Here is how the elements work together:
Ordering Strategy
App Store Connect lets you place the video before, between, or after screenshots. The default and recommended position is before all screenshots.
| Position | Behavior | Best For |
|---|---|---|
| First (before screenshots) | Video plays first in search results (on Wi-Fi) | Apps where video is the strongest hook |
| After first screenshot | First screenshot shows in search, video follows | Apps where screenshot #1 is stronger than video |
How Video and Screenshots Complement Each Other
| Video Does Best At | Screenshots Do Best At |
|---|---|
| Showing interaction flow | Communicating features at a glance |
| Demonstrating complex gestures | Providing keyword-rich captions (for OCR) |
| Creating emotional connection | Showing breadth of features |
| Proving the app works as shown | Letting users control the information pace |
| Showcasing animations | Presenting structured comparisons/data |
When using both, do not duplicate content. If your video shows the main workflow, use your screenshots to highlight features the video does not cover. Together, they should tell a complete story.
Category-Specific Recommendations
Based on conversion data and category norms, here are specific recommendations:
| Category | Recommendation | Video Priority | Screenshot Focus |
|---|---|---|---|
| Games (casual) | Video essential | High | Show variety of levels/modes |
| Games (strategy/RPG) | Video important | High | Show depth and progression |
| Photo & Video | Video recommended | Medium-High | Before/after comparisons |
| Social Networking | Screenshots preferred | Low | Show the UI and social features |
| Productivity | Screenshots preferred | Low | Feature overview with captions |
| Health & Fitness | Test both | Medium | Show tracking and results |
| Education | Test both | Medium | Show learning experience |
| Finance | Screenshots preferred | Low | Show dashboard and key features |
| Music | Video recommended | Medium-High | Show creation/playback |
| Navigation/Maps | Video recommended | Medium | Show real-time navigation |
| Shopping | Screenshots preferred | Low | Show products and checkout |
| Weather | Screenshots preferred | Low | Show forecasts and widgets |
For any category marked “Test both,” use Apple’s product page optimization to A/B test with and without video.
Measuring Video vs Screenshot Performance
You cannot improve what you do not measure. Here is how to evaluate whether your video is helping or hurting:
Metrics to Track
| Metric | Where to Find It | What It Tells You |
|---|---|---|
| Conversion rate | App Store Connect Analytics | Overall listing effectiveness |
| Product page view rate | App Store Connect Analytics | Search result appearance effectiveness |
| Video play rate | Not directly available | Estimated from engagement data |
| A/B test results | Product Page Optimization | Direct comparison of variants |
Running a Proper A/B Test
- Create Treatment A: Current listing with video
- Create Treatment B: Same listing without video (or different video)
- Run for at least 7 days (14 days preferred)
- Require statistical significance before drawing conclusions
- Test in your primary market first, then expand
For a comprehensive guide to screenshot and listing A/B testing, see the A/B testing guide.
The Future of Video on the App Store
Apple has been expanding video capabilities on the App Store. Here are the trends to watch:
| Trend | Status (2026) | Impact |
|---|---|---|
| Multiple preview videos | Available (up to 3 per localization) | More opportunity to show different features |
| Longer video duration | Still 30-second maximum | Unlikely to change soon |
| Auto-play on cellular | Still disabled | Major limitation for video effectiveness |
| Interactive previews | Not available | Potential future feature |
| Video in search ads | Available | Paid video promotion in search results |
The 30-second limit and cellular auto-play restriction are the two biggest constraints on video effectiveness. Until Apple changes these, screenshots will remain the primary conversion driver for most categories.
Key Takeaways
| Takeaway | Action |
|---|---|
| Screenshots convert better for most categories | Invest in professional screenshots first |
| Video wins for games, media creation, and AR | Produce video if your app is in these categories |
| Combined strategy works for paid apps | Use both video and screenshots |
| Poster frame quality matters enormously | Design your video’s first frame like a screenshot |
| Auto-play on cellular is off | Do not rely on video for cellular users |
| Always A/B test before committing | Data beats assumptions |
The bottom line: invest in your screenshots first. They are guaranteed to be seen by every visitor. Video is a supplement, not a replacement. Follow the screenshot design principles and the screenshot best practices to build a screenshot set that converts, then layer in video if your category and data support it.
FAQ
Does adding a video replace my first screenshot? No, the video appears as an additional element before your screenshots. However, in search results on Wi-Fi, the video takes the visual space where your first screenshot would normally appear. This means users see your video auto-playing instead of your first screenshot. On cellular connections, they see the video’s poster frame. This is why your poster frame and your first screenshot both need to be compelling.
Can I use screen recordings from a real device? Yes, and Apple requires that video content show the actual app in use. You cannot use rendered mockups, pre-rendered animations, or footage that does not represent the real app experience. Screen recordings from a real device or Simulator are both acceptable. Use Xcode’s built-in screen recording for the cleanest capture, and add overlays or captions during post-production.
Should my app preview video have sound? Sound is optional but can be beneficial for music apps, games, and entertainment apps where audio is part of the experience. Videos auto-play muted, and users must tap to hear audio. Consider designing your video to work with and without sound. If you include audio, use a combination of app sounds and subtle background music. Never use only narration, as most users will watch muted.
How often should I update my app preview video? Update your video when you release a major UI redesign or significant new features that change the core experience. Minor updates do not warrant a new video. Re-recording a video is time-consuming, so plan video updates to coincide with major version releases. If your video still accurately represents the current app experience, leave it. Outdated screenshots are a bigger concern than outdated video.
Can I A/B test video versus no video? Yes. Apple’s Product Page Optimization feature lets you create treatment variants with different assets, including swapping video for screenshots. Set up a test with one variant including video and one without, run it for at least 14 days, and compare conversion rates. This is the only reliable way to know whether video helps your specific app. See the A/B testing guide for detailed setup instructions.