Your first screenshot influences conversion rates more than your app icon. That single fact surprises most developers, yet the majority still treat preview images as a last-minute checkbox before submission. The reality is that users spend only a few seconds scanning your listing before deciding to install or scroll past. Getting your preview images right is not just a design exercise. It is a direct lever on downloads, revenue, and your app’s long-term visibility in search results. This article breaks down exactly what app preview images are, what each platform demands, and how to design assets that actually convert.
Table of Contents
- What are app preview images?
- Platform differences: Apple vs Google requirements
- Best practices for designing app preview images
- Edge cases and advanced tips: maximizing impact with nuanced assets
- Take your app preview images to the next level
- Frequently asked questions
Key Takeaways
| Point | Details |
|---|---|
| Preview images boost conversions | Well-designed images and videos help apps stand out and convert users more effectively in stores. |
| Know platform requirements | Apple and Google have different size, format, and content rules that can lead to rejection if ignored. |
| Design for impact | Prioritize the first few images, use clear benefits, and test regularly to maximize performance. |
| Localization matters | Localizing preview assets can increase installs and broaden your app’s market reach. |
| Tools streamline creation | Using screenshot generators saves time and ensures images meet app store standards. |
What are app preview images?
App preview images is an umbrella term covering two distinct asset types: static screenshots and short video previews. Both appear on your app store listing and serve as the primary visual evidence that your app does what it claims. Think of them as your storefront window. If the display looks cluttered or confusing, shoppers keep walking.
Apple and Google use different terminology, which trips up a lot of developers. On the Apple App Store, the term app preview refers specifically to a short video clip, while screenshots are the static images. Google Play groups everything under preview assets, including screenshots, a feature graphic, and an optional promotional video. Understanding this distinction matters because each asset type has its own upload slot, its own technical rules, and its own impact on conversion.
Here is a quick comparison of the two asset categories across both platforms:
| Asset type | Apple App Store | Google Play |
|---|---|---|
| Static images | Up to 10 screenshots per device/localization | 2 to 8 screenshots per device |
| Video | App preview, 15 to 30 seconds | Promotional video via YouTube link |
| Feature graphic | Not applicable | Required, 1024×500 px |
| Formats accepted | PNG or JPEG, RGB, no alpha | JPEG or 24-bit PNG |
Both platforms treat effective visual assets as central to app store optimization (ASO), which is the practice of improving your listing so it ranks higher and converts better. Screenshots and videos are not decoration. They are ranking signals and conversion tools rolled into one.
Key things to keep in mind about preview images:
- They appear in search results, not just on your product page
- The first one or two images carry the most visual weight
- Video previews autoplay muted in Google Play search results
- Poor assets can suppress your listing even if your app is excellent
Platform differences: Apple vs Google requirements
With definitions in place, let’s look at what each platform actually expects and where developers most often stumble.
Apple is the stricter of the two. App previews on Apple are videos between 15 and 30 seconds, encoded in H.264 or ProRes, with a maximum file size of 500MB, and you can upload up to three per listing. Screenshots must match exact device pixel dimensions. For the iPhone 6.9 inch display, that means 1320×2868 pixels in portrait orientation. Submit the wrong size and your build gets rejected before a human reviewer even looks at it.
Google is more flexible but still has firm boundaries. Screenshots must fall between 320 and 3840 pixels on any side, with a 9:16 or 16:9 aspect ratio. The feature graphic requirement of 1024×500 pixels is mandatory, not optional. Videos on Google Play are hosted on YouTube and linked rather than uploaded directly.
Here is a side-by-side breakdown of the critical technical specs:
| Requirement | Apple App Store | Google Play |
|---|---|---|
| Screenshot format | PNG/JPEG, RGB, no alpha channel | JPEG or 24-bit PNG |
| Max screenshots | 10 per device per localization | 8 per device |
| Video length | 15 to 30 seconds | No strict limit via YouTube |
| Video format | H.264 or ProRes, max 500MB | YouTube hosted |
| Pixel flexibility | Exact device dimensions required | 320 to 3840px, flexible ratio |
The numbered steps below reflect the order in which you should approach compliance:
- Confirm the exact pixel dimensions for every device size you support
- Export screenshots without alpha channels (transparency layers cause instant rejection)
- Encode video previews to the correct codec before uploading to Apple
- Upload your YouTube video link to Google Play rather than a raw video file
- Verify your feature graphic is exactly 1024×500 pixels for Google Play
Pro Tip: Build your storyboarding and mockups workflow around the largest required size first. Scaling down preserves quality. Scaling up destroys it.
Best practices for designing app preview images
Knowing the technical rules is only half the battle. The other half is designing assets that stop the scroll and communicate value in under three seconds.
Your first screenshot is your headline. It needs to lead with your single strongest benefit, not a generic welcome screen or a logo. Users scanning search results see a thumbnail roughly the size of a postage stamp. If your text is small or your UI is cluttered, the message disappears entirely. Design for thumbnail readability first, then layer in detail for users who tap through to your full listing.
Real UI overlays on device mockups outperform illustrated or abstract visuals. Users want to see what the app actually looks like before they commit to a download. Pair real screenshots with a short benefit caption in large, bold text. Keep captions to five words or fewer when possible.
“Screenshots typically impact conversions more than app icons. Prioritize your first three to five screenshots, lead with your top benefit, and A/B test rigorously because small visual changes can produce outsized conversion lifts.”
Common mistakes that cost developers installs:
- Using the default simulator screenshot without any context or caption
- Cramming too many features into a single image
- Ignoring localization and using English text for all markets
- Skipping A/B testing screenshots entirely and assuming the first version is optimal
- Uploading images with alpha channels, which triggers automatic rejection on Apple
Pro Tip: Treat your screenshot set like a visual story. Image one introduces the problem your app solves. Images two and three show the solution in action. Images four and five handle objections or highlight secondary features. This narrative structure keeps users engaged long enough to hit install.
Quarterly updates matter more than most developers realize. App stores reward fresh listings with slightly better visibility, and user expectations shift over time. An asset set that converted well eighteen months ago may now look dated compared to newer competitors.
Edge cases and advanced tips: maximizing impact with nuanced assets
With the basics covered, let’s dig into the subtleties that separate good listings from great ones.
Device-specific assets are non-negotiable if you support multiple form factors. iPad screenshots cannot be the same file as iPhone screenshots. Wear OS, Android TV, and tablet listings each require their own dedicated assets. Submitting phone screenshots for a tablet listing is a fast path to rejection and a poor user experience for anyone who does see your listing.
Dark mode screenshots are increasingly important. A large share of users run their devices in dark mode full time. Showing only light mode screenshots signals that your app may not support the preference, which can quietly suppress installs among that segment.
Localization is one of the highest-leverage moves available to small teams. Localized preview assets can boost installs by up to 48% in non-English markets. That is not a marginal gain. For an app with any international audience, translating your screenshot captions and adapting your visuals to local context is one of the best returns on time you can find.
Advanced workflow tips for small teams:
- Design all assets at the largest required resolution and scale down for smaller devices
- Use device-specific mockups to maintain visual consistency across form factors
- Include at least one dark mode screenshot per device type if your app supports it
- Never include prices, discounts, or third-party brand marks in your screenshots
- Avoid showing content that does not appear in the actual app, which is a direct violation of both Apple and Google policies
Pro Tip: Set a calendar reminder every quarter to audit your preview images. Compare them against your top three competitors. If their assets look sharper or communicate value more clearly, that gap is costing you installs right now.
One often-overlooked detail: videos autoplay muted in Google Play search results. This means your video must communicate its core message visually, without relying on audio or narration. Design your video as if the sound will never be heard, because for most viewers, it will not be.
Take your app preview images to the next level
Mastering the theory behind preview images is a strong start, but execution is where most small teams lose time. Manually resizing assets for every device, checking compliance with Apple and Google specs, and iterating on designs without a streamlined workflow can eat days out of a sprint.
AppScreenKit is built specifically for this problem. You can create stunning screenshots using pre-built templates that already conform to Apple and Google size requirements, so rejection due to wrong dimensions or missing feature graphics becomes a thing of the past. The platform lets you place your real app UI into professional 3D device mockups, add branded text and gradient backgrounds, and export pixel-perfect assets for every device size with a single click. For teams juggling localization across multiple markets or managing assets for several apps at once, that kind of automation is not a luxury. It is a competitive advantage.
Frequently asked questions
What is the difference between app previews and screenshots?
App previews on Apple are short videos showcasing app functionality, while screenshots are static images presenting the UI. Google groups both under the term preview assets, but the distinction still matters for upload slots and technical requirements.
How can preview images improve app store conversion rates?
Optimized images help users understand your app’s value in seconds. Screenshots impact conversions more than app icons, and combining strong design with A/B testing can produce significant lifts in install rates.
What are common reasons for preview image rejection?
Rejections most often happen because of wrong pixel dimensions, alpha channels in PNG files, inclusion of prices or third-party brand marks, or screenshots that show content not present in the actual app. Wrong sizes and alpha channels are the most frequent triggers.
Should I localize my app preview images?
Yes. Localization can boost installs by up to 48% in non-English markets, making it one of the highest-return investments available to small app teams targeting international users.