App store screenshot sizes can use a shared portrait creative set: export 2–8 PNG or JPEG screenshots at Apple’s 6.9-inch iPhone size of 1290 × 2796 px or 1320 × 2868 px, then upload those files to Google Play if they represent the Android app accurately. Apple uses 6.9-inch screenshots to supply smaller iPhone display slots, while Google Play accepts images with each side from 320 px to 3840 px. Create Google Play’s separate required 1024 × 500 px feature graphic before publishing.
Key takeaways
- •Apple accepts 6.9-inch portrait screenshots at 1290 × 2796 px or 1320 × 2868 px.
- •Apple scales 6.9-inch iPhone screenshots down for smaller iPhone display sizes.
- •A 6.5-inch iPhone portrait screenshot is 1242 × 2688 px or 1284 × 2778 px.
- •Google Play requires 2–8 screenshots, with every side between 320 px and 3840 px.
- •Google Play requires a 1024 × 500 px feature graphic for a store listing.
This guide is for mobile UI/UX designers, founders, and engineers who can export final iOS and Android screen compositions.
Time: 25 minutes · You'll need: Final iOS and Android app builds or representative device captures, Image editor with pixel-based export controls, App Store Connect access, Google Play Console access
What's on this page
- •Choose the 6.9-inch iPhone export master
- •Add 6.5-inch iOS screenshot sizes only when needed
- •Prepare Google Play screenshot sizes from the same story
- •Export the feature graphic and validate both uploads
- •Reference table
Sizing app store screenshot sizes step by step
1. Choose the 6.9-inch iPhone export master
Build the portrait master at 1290 × 2796 px or 1320 × 2868 px. These are Apple’s accepted 6.9-inch iPhone screenshot dimensions. Use one size consistently across the full sequence; do not mix 1290 × 2796 px files with 1320 × 2868 px files in one visual story unless the underlying device framing changes intentionally.
Apple’s 6.9-inch slot is the efficient iPhone source because App Store Connect scales screenshots supplied for that display down to smaller iPhone display slots. Upload the 6.9-inch files directly. Do not expect Apple to create a 6.9-inch asset from a 6.5-inch upload; that would require upscaling, so the 6.9-inch source must be supplied at its native accepted dimensions.
Capture the app state rather than a generic marketing mockup when a screen contains platform UI. A payment sheet, permission prompt, navigation bar, or status area should match the app version submitted for review. Keep screenshot order identical across stores when the same creative narrative is truthful for both platforms.
Tip: Use the 6.9-inch source even when most of your customers use smaller phones; it avoids maintaining a separate 6.5-inch App Store Connect set.
2. Add 6.5-inch iOS screenshot sizes only when needed
Use 1242 × 2688 px or 1284 × 2778 px for a direct 6.5-inch iPhone portrait upload. These are valid 6.5-inch iOS screenshot sizes, but they are not a replacement for the 6.9-inch source when your app is listed on current large iPhones. Apple can scale a supplied 6.9-inch screenshot down to the 6.5-inch presentation; it does not scale a 6.5-inch screenshot up to fill the 6.9-inch slot.
Choose a direct 6.5-inch set only when you are deliberately maintaining that older source size or when App Store Connect asks for it for the device support you selected. If you upload both 6.9-inch and 6.5-inch files, use the same screen order, copy, locale, and feature claims. A mismatch such as “Scan receipts” in image one on 6.9-inch and “Track budgets” in image one on 6.5-inch makes the App Store gallery inconsistent across devices.
Check each export’s pixel dimensions in the file inspector, not just the artboard label. A 2× or 3× export setting can produce a file that looks correct but fails the accepted upload size.
Tip: Treat 1242 × 2688 px and 1284 × 2778 px as alternate accepted files, not two files to upload for the same 6.5-inch slot.
3. Prepare Google Play screenshot sizes from the same story
Export 2 to 8 phone screenshots for Google Play. Google Play requires each screenshot side to be at least 320 px and no more than 3840 px. A 1290 × 2796 px or 1320 × 2868 px 6.9-inch iPhone master falls within those per-side limits, so it can be uploaded to Google Play without resizing solely for the stated pixel bounds.
Use the same screenshot sequence only when it accurately shows the Android app. Replace iOS-specific elements before export: Dynamic Island framing, iOS permission dialogs, Apple system sheets, and iPhone-only navigation conventions make an Android listing misleading. Keep shared campaign copy and composition where possible, but show Android status bars, Material components, and Android flows where they appear in the product.
Upload no more than eight files in Google Play Console. Start with four if four screens tell the complete acquisition story: the primary task, the key differentiator, a proof screen, and the outcome. Add screenshots five through eight only when each explains a distinct feature or audience use case.
Tip: Do not pad Google Play to eight images with alternate color themes; every screenshot should introduce a new product claim or task.
4. Export the feature graphic and validate both uploads
Create Google Play’s required 1024 × 500 px feature graphic as a separate asset. It is not a screenshot and should not be counted among the 2–8 Google Play screenshots. Design it as a wide promotional composition: keep the app name and focal product element readable at the actual 1024 × 500 px canvas, then export the final file rather than relying on an editor preview.
Before upload, make one delivery folder with ios-6.9, ios-6.5-optional, google-play-screenshots, and google-play-feature-graphic subfolders. Put the 1290 × 2796 px or 1320 × 2868 px Apple source files in the first folder. Put only 2–8 files, each with sides between 320 px and 3840 px, in the Google Play folder. Name files by order, such as 01-capture-expenses.png through 04-review-month.png.
Upload the iPhone set in App Store Connect and the Android-accurate set in Play Console. Review the store previews before saving. The correct technical dimensions do not correct cropped headlines, hidden navigation, or stale product UI.
Tip: Keep the 1024 × 500 px feature graphic outside the numbered screenshot sequence so release managers cannot upload it into the wrong Play Console field.
Reference table
Current iOS and Google Play asset limits
| Asset | Required size or count | Upload behavior |
|---|---|---|
| Apple 6.9-inch iPhone portrait | 1290 × 2796 px or 1320 × 2868 px | Apple scales downward |
| Apple 6.5-inch iPhone portrait | 1242 × 2688 px or 1284 × 2778 px | Upload directly if needed |
| Google Play screenshots | 2–8 files; 320–3840 px per side | PNG or JPEG |
| Google Play feature graphic | 1024 × 500 px | Separate required asset |
Do it with the free App Store Screenshot Sizes
Required screenshot dimensions for the App Store and Google Play, with counts and limits.
Open the App Store Screenshot Sizes → — free, no sign-up.
Common mistakes
Uploading a 6.5-inch iPhone set and assuming Apple will fill the 6.9-inch slot.
Upload 1290 × 2796 px or 1320 × 2868 px screenshots directly for the 6.9-inch display. Apple scales from the larger 6.9-inch source down, not from 6.5-inch up.
Counting the Google Play feature graphic as one of the screenshots.
Upload 2–8 screenshots in the screenshot field, then add the 1024 × 500 px feature graphic in its separate Play Console field.
Using iPhone system UI in the Google Play gallery.
Reuse the creative concept, not blindly the iOS capture. Replace iOS-only system UI with accurate Android app screens before upload.
Exporting files from a scaled artboard without checking final pixels.
Inspect each final PNG or JPEG. Apple accepts the named iPhone pixel dimensions, while Google Play rejects any screenshot side below 320 px or above 3840 px.
Frequently asked questions
What are the app store screenshot sizes for a 6.9-inch iPhone?
The accepted 6.9-inch iPhone portrait screenshot sizes are 1290 × 2796 px and 1320 × 2868 px. Upload one of those sizes directly to App Store Connect for the 6.9-inch display. Apple uses that large-display source to provide screenshots for smaller supported iPhone display sizes.
What are the 6.5-inch iOS screenshot sizes?
The accepted 6.5-inch iOS screenshot sizes in portrait are 1242 × 2688 px and 1284 × 2778 px. Use them only when you need to provide a 6.5-inch source directly. They do not replace the 6.9-inch source for listings that need current large-iPhone screenshots.
How many screenshots does Google Play require?
Google Play requires at least 2 and allows up to 8 screenshots for an app listing. Each side of every screenshot must be between 320 px and 3840 px. The feature graphic is a separate required 1024 × 500 px asset, not one of the screenshot files.
Can I use the same screenshots for the App Store and Google Play?
You can use the same raster screenshots for both stores when they meet Google Play’s 320–3840 px per-side limits and accurately represent both app versions. A 1290 × 2796 px or 1320 × 2868 px Apple 6.9-inch file meets those Google Play pixel limits. Replace iOS-only system UI if the Google Play listing would otherwise misrepresent the Android app.
Does Apple automatically scale App Store screenshots?
Apple automatically scales screenshots supplied for the 6.9-inch iPhone display down for smaller iPhone display sizes. Apple does not create a 6.9-inch screenshot by scaling up a 6.5-inch asset. Supply the 6.9-inch file directly at 1290 × 2796 px or 1320 × 2868 px when that display is supported.
Where this leaves you
Use a 6.9-inch iPhone portrait master at 1290 × 2796 px or 1320 × 2868 px as the iOS source, then retain only Android-accurate files that meet Google Play’s 320–3840 px per-side limit. Keep the shared sequence to 2–8 screenshots so it fits Google Play without a second content plan. Apple’s scaling removes the need to manufacture a 6.5-inch set when the 6.9-inch source is present; it does not remove the need to show the correct platform UI. Export the separate 1024 × 500 px Play feature graphic next, then validate the final files with floow.design’s free App Store Screenshot Sizes tool at /free-tools/app-store-screenshot-sizes before the first upload.
Design the screens first
Describe the screen you need in plain English and floow.design generates production-ready iOS and Android layouts you can iterate on by chat, then export to Figma or code. Design your mobile app screens in floow.design first, then build.
Related
- •Aspect Ratio Calculator — Work out the missing width or height for any ratio, with the common phone and store ratios one click away.
- •Device Size Reference — Screen dimensions, density and safe areas for current handsets — searchable, and exportable as code.
- •App Store Screenshot Generator: 5 Frames That Convert — Use an app store screenshot generator workflow to build five benefit-led frames that sell
- •App Name Generator: Name a Mobile App — Use an app name generator and a practical naming process to create mobile app names that f
- •Design by AI: A Realistic Workflow for Mobile App Teams — Learn a realistic Design by AI workflow that helps mobile app teams move from clear briefs