ZeonTools
01Why App Store Screenshots Are Your #1 ASO Conversion Lever
App Store screenshots are the single highest-leverage Asset in any App Store Optimization strategy. Multiple independent studies confirm that screenshots drive 60–80% of the conversion decision on both the App Store and Google Play product pages. Apple's internal data from their Search Ads team shows that creative sets featuring strong screenshots convert at 3–4× the rate of text-only listings. For a mid-size app receiving 200,000 monthly impressions, a 5% improvement in conversion rate yields 10,000 additional installs — potentially worth tens of thousands of dollars in lifetime value at zero additional marketing spend.
The mechanics are simple: a user searching for "expense tracker" on the App Store sees a grid of app icons, app names, star ratings, and — critically — the first two or three screenshots in a horizontal strip. In most categories, the app with the most compelling three-screenshot story wins the tap. After the icon, screenshots are the first visual information the user processes.
Yet despite this outsized impact, screenshot optimization is routinely neglected. Developers upload screenshots once at launch, never revisit them, and leave enormous conversion potential on the table. The core reason is friction: Apple and Google require screenshots at over 22 distinct pixel-exact dimensions across iPhone, iPad, macOS, Apple Watch, Apple TV, Android Phone, Android Tablet, Wear OS, Android TV, and ChromeOS. Manually exporting every required size from Figma, Photoshop, or Sketch costs 2–4 hours per update cycle per localization.
02Complete App Store Screenshot Size Requirements 2025
Apple requires screenshots in specific pixel dimensions for each device display class. As of 2025, the iPhone 6.7" (1290 × 2796px) is now the primary mandatory submission size for iPhone apps, replacing the legacy 5.5" as the enforced minimum. Apps without a 6.7" or 6.5" screenshot will display scaled screenshots in search results — visibly degrading quality for users with the newest devices.
iPhone Screenshot Sizes (Portrait)
| Display | Resolution (px) | Models Covered | Status |
|---|---|---|---|
| iPhone 6.7" | 1290 × 2796 | iPhone 15 Pro Max, 14 Plus | Primary Required |
| iPhone 6.5" | 1242 × 2688 | iPhone 11 Pro Max, XS Max | Required (legacy) |
| iPhone 6.1" | 1179 × 2556 | iPhone 15, 15 Pro, 14 Pro | Strongly Recommended |
| iPhone 5.5" | 1242 × 2208 | iPhone 8 Plus | Legacy Support |
| iPhone 4.7" | 750 × 1334 | iPhone SE 3rd Gen | Optional |
iPad Screenshot Sizes (Portrait)
| Display | Resolution (px) | Models Covered | Status |
|---|---|---|---|
| iPad 12.9" (6th+) | 2048 × 2732 | iPad Pro 12.9" M1/M2 | Required for iPad |
| iPad 11" | 1668 × 2388 | iPad Pro 11", iPad Air 5 | Recommended |
| iPad 10.5" | 1668 × 2224 | iPad Air 3, iPad Pro 10.5" | Optional |
| iPad 9.7" | 1536 × 2048 | iPad 5th / 6th Gen | Legacy |
03Google Play Screenshot Requirements — Every Size & Constraint
Google Play's requirements are more flexible than Apple's in terms of aspect ratio range (16:9 to 9:16 allowed), but come with unique constraints. All screenshots must be between 320px and 3840px on the longer side, with a maximum file size of 8MB per image. Additionally, all screenshots for a given device type must be either all portrait or all landscape — you cannot mix orientations within the same device slot.
| Device Type | Recommended Size | Aspect Ratio | Notes |
|---|---|---|---|
| Android Phone | 1080 × 1920 | 9:16 | Standard recommendation, covers most devices |
| Android Phone (tall) | 1080 × 2400 | 9:20 | Matches modern long-display flagships (Pixel 8, S24) |
| 7" Tablet | 1200 × 1920 | ~5:8 | Small tablet slot in Play Console |
| 10" Tablet | 1600 × 2560 | 5:8 | Large tablet slot, increasingly important in 2025 |
| Wear OS | 384 × 384 | 1:1 | Square watch face screenshots only |
| Android TV | 1920 × 1080 | 16:9 | Landscape only. Can also submit 1280×720. |
| ChromeOS | 1920 × 1200 | 16:10 | Desktop-class screenshots for Chromebook listing |
| Feature Graphic | 1024 × 500 | Landscape banner | Not a screenshot — separate required promotional asset |
04How Browser Canvas API Resizing Works — Technical Architecture
This tool processes your screenshots entirely within your device's browser memory using the HTML5 Canvas 2D API. Zero server communication occurs. Understanding the architecture helps you get the highest possible output quality.
When you click "Generate All Sizes," the engine executes the following pipeline for each source image × each target size combination:
- File decoding:
URL.createObjectURL(file)creates a temporary memory blob URL. A newHTMLImageElementloads from it. The browser's native image decoder (libjpeg-turbo for JPEG, libpng for PNG) decodes the file into an uncompressed RGBA pixel buffer in GPU-accessible memory. - Canvas allocation: An off-screen
HTMLCanvasElementis allocated at the exact target pixel dimensions (e.g., 1290 × 2796 for iPhone 6.7"). The element exists in the DOM but hasdisplay:none— it is never visible to the user. - Pixel resampling:
ctx.drawImage(img, sx, sy, sw, sh, dx, dy, dw, dh)performs GPU-accelerated bicubic/bilinear interpolation down to the target resolution. The browser's compositing engine handles the actual pixel mathematics. - Encoding:
canvas.toDataURL('image/png')orcanvas.toBlob(cb, 'image/jpeg', quality)re-encodes the canvas pixel buffer into the chosen compressed format. PNG uses the DEFLATE algorithm (lossless); JPEG uses DCT compression; WebP uses VP8 intra-frame coding. - Output: The encoded data URL is used to create a download anchor (
<a href="dataurl" download="filename">) for individual downloads, or pushed into JSZip for batch ZIP generation.
05Resize Strategy Deep Dive: Contain, Cover, Pad & Stretch
The resize strategy is the most consequential setting in any screenshot resizer. Each mode produces dramatically different visual output when your source screenshot's aspect ratio doesn't match the target size — which is almost always the case when adapting a 9:20 iPhone design to a 3:4 iPad canvas.
| Strategy | Behavior | Best For | Trade-off |
|---|---|---|---|
| Contain | Scales the image to fit entirely within the target dimensions. Fills remaining space with black (or chosen pad color). | UI screenshots where no element should be cropped. The safest default for App Store submissions. | Letterbox bars (pillarbox for iPad) are visible at the edges. App Review team does not penalize this. |
| Cover | Scales the image to completely fill the target. Crops whatever exceeds the frame edges — center-anchored by default. | Full-bleed lifestyle screenshots, gradient backgrounds, photography shots with safe subject in the center. | UI elements near the edges will be cropped and invisible to the user. |
| Pad | Identical to Contain, but lets you choose the padding color rather than defaulting to black. | Screenshots with white or brand-colored backgrounds where colored letterbox bars look intentional and premium. | Same letterboxing as Contain. Choose a padding color that matches your screenshot's background color for seamless effect. |
| Stretch | Ignores all aspect ratio constraints. Distorts the image to exactly fill the target canvas. | Only acceptable when the source and target aspect ratios are extremely close (e.g., adapting 9:16 to 9:19.5). | Visible distortion on UI elements, fonts, circular icons, and faces. Almost always the wrong choice for App Store screenshots. |
06PNG vs JPEG vs WebP — Choosing the Right Output Format
The output format decision has significant consequences for screenshot quality and file upload compatibility. App Store Connect accepts PNG and JPEG only. Google Play accepts all three including WebP.
| Format | Compression Type | Transparency | App Store? | Google Play? | Best For |
|---|---|---|---|---|---|
| PNG | Lossless (DEFLATE) | Yes (RGBA) | ✓ | ✓ | UI screenshots with text, sharp edges, icons. No quality degradation regardless of how many times it's saved. |
| JPEG | Lossy (DCT) | No (RGB only) | ✓ | ✓ | Full-bleed lifestyle or photography screenshots without text overlays. Avoid for UI — DCT artifacts appear around high-contrast text. |
| WebP | Lossy + Lossless (VP8) | Yes | ✗ | ✓ | Google Play only. Provides 30–50% file size savings over PNG/JPEG at equivalent visual quality. Faster Play Store listing load times. |
07ASO Screenshot Best Practices: What Top-100 Apps Do Differently
An analysis of the top-performing apps across the App Store categories in 2024–2025 reveals consistent patterns that separate high-converting screenshot sets from underperforming ones.
- Screenshot 1 is your only first impression. Eye-tracking studies from StoreMaven and SplitMetrics show that users make a "install or bounce" decision in the first 2.6 seconds of seeing a listing. Screenshot #1 must instantly communicate the app's core value — not show a welcome screen, a login form, or a list of features.
- Use captions as conversion micro-copy. Screenshots with overlaid text outperform pure UI screenshots by 25–40% in A/B tests. Keep captions to 3–6 words in bold, large type (40pt+ equivalent). Lead with outcome ("Never miss a payment") not feature ("Set payment reminders").
- Show the outcome, not the UI. The most downloaded apps in each category show a user benefit in the caption and supporting UI in the background. "Your money, finally making sense" with a dashboard screenshot outperforms "Dashboard" with the same image.
- Use A/B testing (Apple PPO, Google Play Experiments). Apple's Product Page Optimization (PPO) allows testing up to 3 screenshot variants. Google Play Experiments does the same. Even a 5% improvement in conversion rate compounds into massive install volume over a quarter at scale.
- First 3 screenshots appear in search results on iOS. App Store search on iPhone shows the first 3 portrait screenshots in a horizontal strip without the user tapping through to the full listing. These 3 screenshots must function as a complete standalone pitch.
- Category-specific visual conventions matter. Finance apps convert best with dark-mode dashboards and green growth charts. Fitness apps convert with before/after progressions. Productivity apps convert with UI previews + time-saved captions. Match your category's visual language before testing against it.
08Localized Screenshot Strategy: 20–40% More Installs in Non-English Markets
Both the App Store and Google Play allow completely separate screenshot sets per territory and language. Japanese, Korean, German, and Brazilian Portuguese screenshots can be entirely different from your English US set — different images, different text, different visual aesthetics.
This capability is dramatically underused. Apps that localize their screenshots (not just their text strings) see 20–40% higher conversion rates in non-English markets compared to showing English-language default screenshots to those users. The gap is largest in these high-priority markets:
- Japan (ja): Japanese App Store users respond strongly to dense information, smaller caption text, anime-adjacent illustration styles, and UI screenshots that show more content per frame. Western minimalism underperforms significantly.
- South Korea (ko): Korean users favor K-beauty aesthetic — pastel colors, rounded UI, social proof in screenshots (review counts, "Top #1" badges), and webtoon-style visual framing.
- Germany (de): German users respond to precision, data density, authority signals (certification badges, "DSGVO-konform" compliance language), and technical feature callouts over emotional benefit copy.
- Brazil (pt-BR): Brazilian users convert best with bright, high-energy color palettes, social proof (number of users), celebrity or influencer endorsement visual cues, and WhatsApp/social integration callouts.
With this tool, localizing screenshots becomes a fast workflow: export your master screenshots at all sizes → translate the overlay text in Figma → re-export the localized versions → upload to this tool and batch resize. What previously required a design agency and a week of work now takes one developer 30 minutes per locale.
09Apple Watch & Apple TV Screenshot Specifications
Apple Watch and Apple TV have unique screenshot requirements that many developers overlook, resulting in auto-scaled or rejected screenshots on those platforms.
Apple Watch — Exact Per-Hardware Dimensions
Apple Watch screenshots must match the exact pixel dimensions for each hardware size. Unlike iPhone, Apple does not auto-scale Watch screenshots between sizes. If you submit only 45mm screenshots, users with a 40mm Watch SE will see scaled, blurry versions.
| Watch Model | Case Size | Required Screenshot (px) | Generation |
|---|---|---|---|
| Apple Watch Ultra 2 | 49mm | 410 × 502 | Ultra / Ultra 2 |
| Series 9 (Large) | 45mm | 396 × 484 | Series 7–9, Ultra 1 (44mm) |
| Series 9 SE (Small) | 41mm / 40mm | 324 × 394 | SE 2nd Gen, Series 4–9 40mm |
| Series 3 (Legacy) | 38mm | 272 × 340 | Series 3 and earlier |
Apple TV — Landscape Only
Apple TV screenshots are always landscape. You must submit in either 1080p (1920 × 1080) or 4K (3840 × 2160). The tvOS store shows screenshots on large displays in dark environments, so dark-mode UI screenshots with high-contrast, brightly-lit elements work best. Always submit at least 1080p; 4K is optional but recommended for apps targeting Apple TV 4K.
10Production Screenshot Workflow for App Store Submission
Here is the exact end-to-end production workflow used by professional ASO specialists and mobile marketing teams:
- Design master at 1290 × 2796px. Start with the iPhone 6.7" canvas in Figma or Sketch. This is the largest commonly-required iPhone size. All UI and caption elements should be positioned within safe margins (at least 80px from all edges).
- Export master as PNG. Always export from your design tool as lossless PNG to prevent generation loss before the resize step. Never export JPEG from your design tool — that bakes in compression artifacts before our tool has a chance to resize.
- Upload to this tool. Drag and drop your master PNG. Select "All iOS" + your desired Android preset. Choose "Contain" mode for safety.
- Review the preview grid. Check each generated variant visually. Confirm no critical UI elements are being letterboxed into invisibility. If they are, switch to "Cover" mode or redesign the master with more centered composition.
- Download as ZIP. One click exports all variants as a ZIP file, organized by platform (ios/ and android/ subfolders), with self-documenting filenames like
screenshot1_iphone_67_1290x2796.png. - Upload to App Store Connect. Drag the correctly-named files from the ZIP into the App Store Connect screenshot slots. The interface auto-detects size and assigns files to the correct device. Upload all platform sizes before submitting your build.
- Upload to Google Play Console. In the Play Console → Store Presence → Main store listing → Screenshots, upload the android/ folder contents to the appropriate device type slots.
- Set up A/B test (optional but recommended). Use Apple's Product Page Optimization or Google Play Experiments to test screenshot variants against your submission. Allocate 20–30% of traffic to the challenger for statistical significance.
11ZeonTools vs Paid Screenshot Resizers: Honest Comparison
The market for screenshot resizers ranges from free (but watermarked) tools to premium SaaS platforms charging $99+/month. Here is an honest feature-by-feature comparison:
FAQFrequently Asked Questions
What screenshot size is required for iPhone 15 Pro Max on the App Store?
The iPhone 15 Pro Max requires screenshots at exactly 1290 × 2796 pixels (portrait) or 2796 × 1290 pixels (landscape). This is the 6.7" display size class. As of 2025, Apple designates the 6.7" size as the primary required submission size. Without it, Apple auto-scales your legacy 6.5" screenshot (1242 × 2688) to fill the 6.7" display, introducing visible bicubic interpolation blur — especially noticeable on text edges and icon borders.
Does this tool upload my screenshots to a server?
No. This tool uses the browser's HTML5 Canvas 2D API to perform all image resizing entirely within your device's memory. Your screenshot files never leave your computer — no server request, no upload, no network transmission. This is critical for developers working on unreleased apps under NDA, or for studios that handle sensitive client work. The processing happens in your browser's JavaScript engine, with the same image quality as Photoshop's Bicubic Sharper algorithm for downscaling operations.
Why do I need to provide the exact pixel dimensions? Can't Apple just scale them?
Apple will auto-scale screenshots when an exact-size version is not provided, but the results are visibly degraded. Bicubic interpolation on a 6.5" source image to fill a 6.7" display introduces softening artifacts, particularly around sharp text edges and fine UI lines. For users browsing the App Store on their brand-new iPhone 15 Pro Max, this blurred screenshot is their first impression of your app's quality. Providing native-resolution screenshots for each device ensures pixel-perfect clarity, which directly impacts conversion rate.
What is the difference between Contain, Cover, Pad, and Stretch resize modes?
These four modes control what happens when your source screenshot's aspect ratio doesn't match the target canvas size:
• Contain: Scales the image down so it fits entirely within the target. Fills empty space with black (or pad color). No cropping. Use for UI screenshots where nothing should be cut off.
• Cover: Scales the image up/down to completely fill the target canvas, cropping any excess from the edges. Use for full-bleed lifestyle shots where the subject is centered.
• Pad: Identical to Contain but lets you choose the background fill color. Use when your screenshot has a white or colored background and you want the letterbox bars to blend seamlessly.
• Stretch: Ignores aspect ratio and distorts the image to exactly fill the target. Almost always wrong for UI screenshots — creates visibly warped fonts and interface elements.
How many screenshots does Apple allow per device per localization?
Apple allows up to 10 screenshots per device size, per localized language version of your app. For a universal iOS + iPad + macOS app targeting 5 languages, that's up to 10 × 3 devices × 5 languages = 150 screenshots you can upload. In practice, the first 3 portrait screenshots are the most impactful because they appear directly in App Store search results (below the icon and rating) without requiring a user tap. Invest most of your design effort in those first three.
What is the required Google Play Feature Graphic size?
The Google Play Feature Graphic must be exactly 1024 × 500 pixels in landscape orientation. It's a PNG or JPEG (no transparency/alpha) with a maximum file size of 1MB. The Feature Graphic is a separate promotional asset from your screenshots — it appears at the top of your Play Store listing as a banner and is used in editorial promotions, "Top Charts" listings, and Google Play promotional emails. It is not auto-generated from your screenshots. This tool includes a 'Feature Graphic' preset in the Android tab.
Can I use WebP format for App Store submissions?
No. Apple App Store Connect only accepts PNG and JPEG screenshot files. WebP is not supported for iOS App Store submissions as of 2025. However, Google Play fully supports WebP (both lossless and lossy modes). For Google Play submissions, WebP is highly recommended — it produces files 30–50% smaller than equivalent PNG/JPEG quality, which means faster Play Store listing load times and better user experience on slow mobile connections. This tool exports WebP for Android-targeted outputs.
Why do my screenshots look slightly blurry after resizing?
Blurriness after resizing is almost always caused by upscaling — generating a large output from a small source image. The browser's Canvas API uses bicubic interpolation to "invent" pixels that don't exist in the source, which causes softening. For sharp output, always design your master screenshot at the largest required size (1290 × 2796 for iPhone, 2048 × 2732 for iPad) and let this tool scale DOWN. Downscaling averages existing pixels and produces significantly sharper results than upscaling. Never use a 750 × 1334 iPhone SE screenshot to generate a 2048 × 2732 iPad size.
Do screenshots for Apple Watch need to be portrait-only?
Yes. All Apple Watch screenshots must be portrait orientation. The watch display is always portrait, and Apple does not accept or display landscape Watch screenshots. Additionally, unlike iPhone (where Apple will scale a 6.5" screenshot to the 6.7" slot), Apple Watch requires screenshots at the exact pixel dimensions for each hardware case size. The Ultra 2 (49mm) requires 410 × 502, the Series 9 45mm requires 396 × 484, and the SE 40mm requires 324 × 394. This tool generates all four Watch sizes from a single source image.
How does Google Play Experiments differ from Apple's Product Page Optimization?
Both allow A/B testing of screenshots, but with different mechanics:
Apple Product Page Optimization (PPO): Test up to 3 alternative page treatments (icon, screenshots, preview video) against your default. Traffic is split at the App Store server level. Results available after 90 days of minimum traffic. Free, but requires a separate app version in App Store Connect.
Google Play Experiments: Test alternative graphics and store listings for up to 500,000 users. Can run multiple experiments simultaneously. Results typically statistically significant within 2–4 weeks. Available directly in Play Console under Growth → Store Performance.
Can I process multiple screenshot files at the same time?
Yes. This tool supports multiple source images simultaneously. You can upload all 10 of your App Store screenshot designs at once, and the engine will generate all target sizes for every source image in a single batch operation. For example: upload 5 screenshots × 22 sizes = 110 output files generated automatically. The Download ZIP button packages all outputs organized by platform (ios/ and android/ subfolders) for direct upload to App Store Connect and Play Console.
What should I do if App Store Connect rejects my screenshots?
App Store Connect screenshot rejections typically occur for these reasons:
1. Wrong pixel dimensions: Verify you're using the exact sizes from this tool's size table (not approximate values).
2. File too large: App Store allows up to 10MB per screenshot. PNG files at 2048 × 2732 can exceed this — switch to JPEG at 85% quality for iPad submissions.
3. Screenshots showing non-app content: Apple rejects screenshots showing other apps' UIs, content from other apps, or web browser chrome unless your app is a browser.
4. Placeholder content: Screenshots with Lorem Ipsum, test data marked "test", or debug overlays are rejected.
5. Wrong format: Apple only accepts PNG and JPEG. WebP is not supported.
Is there a minimum number of screenshots required for App Store submission?
Apple requires a minimum of 1 screenshot for each device size that your app supports. However, the practical minimum for a competitive listing is 3 screenshots for the primary iPhone size (to appear in search results with all 3 slots filled) and 1 for iPad if your app is iPad-compatible. Apple strongly recommends 5–10 screenshots to maximize the conversion opportunity. For new submissions, having at least the 6.7" (1290 × 2796) and 6.5" (1242 × 2688) iPhone sizes is mandatory as of 2025.
Can I include video previews alongside screenshots?
Yes. Both App Store and Google Play allow video previews (app preview videos on iOS, promo videos on Android). On the App Store, the video preview appears before your screenshots in the listing carousel and plays muted by default. App preview videos must be 15–30 seconds long, recorded at native device resolution (e.g., 1290 × 2796 at 30fps for iPhone 6.7"), and must show actual in-app content — not marketing footage. This tool handles screenshot resizing only; for video previews, use screen recording directly on the device.
What is the maximum file size for App Store and Google Play screenshots?
App Store Connect accepts screenshot files up to 10MB per individual image. In practice, even the largest iPad Pro screenshots (2048 × 2732) exported as PNG typically range from 1–6MB depending on content complexity. If you hit the 10MB limit, switch to JPEG at 90% quality — the visual difference is imperceptible at these sizes. Google Play accepts screenshots up to 8MB each, with the Feature Graphic limited to 1MB separately. WebP format (Google Play only) consistently produces the smallest files — often under 1MB even for tablet-resolution screenshots.