Frequently asked questions
Everything developers and marketers ask about App Store and Google Play screenshots — sizes, formats, requirements, headlines, and localization.
Apple requires screenshots at the iPhone 6.9" or 6.7" size (1290×2796 or 1284×2778 pixels) and the iPad Pro 13" or 12.9" size (2064×2752 or 2048×2732 pixels). Older iPhone 6.5" (1284×2778) and 5.5" (1242×2208) sizes are still accepted but no longer required if you provide the newer ones. Screenshots must be PNG or high-quality JPEG in RGB color, sRGB or P3.
Google Play accepts phone screenshots between 320 and 3840 pixels on each side, with a 16:9 or 9:16 aspect ratio. The recommended phone size is 1080×1920 pixels. Tablet screenshots use the same range; 1200×1920 is a good 7" target and 1800×2560 is a good 10" target. Screenshots must be PNG or 24-bit JPEG, with no alpha channel.
Apple requires at least one screenshot per required device size and allows up to 10 per language per size. Most apps upload 3 to 6, since only the first three are visible without scrolling on the App Store product page. You only need to upload screenshots once for the largest required iPhone and iPad sizes — Apple displays them on smaller devices automatically.
Google Play allows 2 to 8 screenshots per form factor (phone, 7-inch tablet, 10-inch tablet, Wear OS, Android TV). At least 2 phone screenshots are required to publish. Google recommends uploading 4 to 8 to fully showcase the app, since users swipe through them on the Play Store listing.
Both PNG and high-quality JPEG are accepted by the App Store and Google Play. PNG is preferred when your screenshots contain text, sharp UI elements, or solid colors because JPEG compression can blur edges. Use sRGB or P3 color space, and avoid transparency on Google Play (it requires a 24-bit JPEG or PNG with no alpha channel).
Text and captions are not required, but they significantly improve conversion rates. Most top-ranked apps use a short headline (3 to 7 words) on each screenshot to highlight a key benefit or feature. Apple allows marketing text overlays as long as they reflect the actual app and don't include pricing, ratings, or claims that violate the App Store Review Guidelines.
Yes, but you must choose one orientation per language and per device size — Apple does not let you mix portrait and landscape screenshots in the same set. If your app supports both, pick the orientation that best showcases the experience. Game apps often use landscape; productivity apps almost always use portrait.
Good App Store screenshots lead with a single, scannable benefit in the first three frames, use a short headline above or below a clean device mockup, and stay readable at thumbnail size. Avoid cramming the full UI into the frame. Use brand colors, consistent typography across the set, and localize the headlines for every market you target.
Yes. AI tools like ScreenCraft take your raw app screenshots, generate marketing headlines, place them in styled device frames, and export every required size for the App Store and Google Play. AI is particularly useful for writing benefit-focused headlines, localizing them into 70+ languages, and producing the 8 to 12 device-size variants Apple and Google require without manual resizing.
You can add headlines in design tools like Figma, Photoshop, or Sketch by placing text above or below your screenshot inside a 1290×2796 or 1284×2778 canvas. Or use a generator that writes and places headlines for you. Keep headlines under 7 words, use a font weight of 600 or higher, and make sure the text is legible at the App Store's thumbnail size.
Yes — localizing screenshots is one of the highest-ROI ASO investments. Apps that localize headlines into the user's language see meaningfully higher conversion rates in non-English markets. Apple and Google both support per-language screenshot sets, so you can ship a different headline and visual treatment to each storefront. Translate marketing copy, not just the literal words.
Yes. You can update App Store screenshots any time by submitting a new version of the app or, for in-flight metadata changes, through the App Store Connect screenshot section without resubmitting binaries (Apple introduced this in 2023). Google Play lets you update screenshots directly in the Play Console without releasing a new APK or AAB.