Google Play Store Screenshot Sizes 2026: Dimensions, Feature Graphic and Icon Requirements

The Google Play Store screenshot sizes for 2026 are flexible rather than fixed: according to the Play Console Help page on preview assets, each screenshot must be a JPEG or 24-bit PNG with no alpha channel, between 320 px and 3,840 px on each side, and the longer side cannot be more than twice the shorter side. You need at least two screenshots to publish and can add up to 8 per device type. To be eligible for Google Play's large recommendation formats, apps should provide at least four screenshots of at least 1080 px resolution: 1080 x 1920 px or larger for portrait (9:16) and 1920 x 1080 px or larger for landscape (16:9).

Last updated: November 2026. This guide is for small business owners, founders and marketers preparing an Android store listing. Every size, limit and rule below was checked against Google's and Apple's own documentation on November 10, 2026; the sources are linked inline and listed at the end.

• Format: screenshots must be JPEG or 24-bit PNG without alpha (no transparency).
• Size range: every side must be between 320 px and 3,840 px, and the long side can be at most twice the short side.
• Quantity: a minimum of two screenshots is required to publish, with up to 8 per supported device type.
• Recommended phone size: 1080 x 1920 px portrait or 1920 x 1080 px landscape, with at least four screenshots, to qualify for screenshot-based recommendation formats.
• Other required graphics: a 512 x 512 px app icon (32-bit PNG, up to 1024 KB) and a 1024 x 500 px feature graphic.
• Content rules matter as much as pixels: Google asks for real in-app screens and no ranking, price or "download now" wording.

Google separates its rules into "requirements" and "highly recommended" guidelines. The preview assets documentation states that requirements are mandatory and that failing to meet them may result in removal or suspension from Google Play, while ignoring the recommended guidelines does not affect your store listing page but may limit how your assets appear and reduce promotional opportunities.

The mandatory screenshot requirements are short:

• Number: at least two screenshots across different device types to publish the store listing; up to 8 for each supported device type.
• File type: JPEG or 24-bit PNG with no alpha channel.
• Minimum dimension: 320 px.
• Maximum dimension: 3,840 px.
• Aspect limit: the maximum dimension cannot be more than twice as long as the minimum dimension.

The aspect limit is the rule that catches people out. Apply it to a common raw phone capture and the arithmetic is simple: a 1080 x 2400 px capture has a long side 2.22 times the short side, which is over the 2:1 limit, while 1080 x 1920 px (1.78 times) and 1080 x 2160 px (exactly 2 times) are within it. If your phone or emulator produces a taller image, crop it or place it on a canvas that fits the limit before uploading.

Meeting the minimum is not the same as giving your listing its best chance. Google explains in the same help article that some sections of Google Play show groups of recommended apps and games in a large format built from screenshots, and that stricter guidelines apply if you want to be eligible for those formats:

• Apps: at least four screenshots with a minimum 1080 px resolution; 9:16 for portrait (minimum 1080 x 1920 px) and 16:9 for landscape (minimum 1920 x 1080 px).
• Games: at least three 16:9 landscape screenshots (minimum 1920 x 1080 px) or three 9:16 portrait screenshots (minimum 1080 x 1920 px) that show the in-game experience.

For most small business apps, the practical choice is therefore four to eight portrait images at 1080 x 1920 px. That size satisfies the mandatory range, the 2:1 limit and the recommendation guideline at once. Note that eligibility is not a promise: Google does not say that meeting these guidelines guarantees your app will be featured.

Google also describes where screenshots appear. They may be shown in search and on the homepage as well as on your store listing, and when a preview video is present the screenshots follow it, ordered left to right starting with the ones best suited to the device the person is browsing on.

Google Play supports separate screenshot sets for phones, 7-inch and 10-inch tablets, Chromebooks, Android TV, Wear OS watches, Android Automotive OS cars and Android XR headsets. The device-specific rules in the Play Console documentation are:

• Tablets and Chromebooks (large screens): a minimum of 4 screenshots to demonstrate the in-app experience, between 1,080 px and 7,680 px, using 16:9 for landscape and 9:16 for portrait. Google advises leaving out extra text that is not part of the app, because it can be cut off on some Play homepages.
• Wear OS apps: at least one screenshot of the current version on Wear OS, 1:1 aspect ratio, minimum 384 x 384 px, showing only the app interface, with no device frames, added text, extra backgrounds, transparency or masking.
• Wear OS watch faces: at least one 1:1 screenshot of at least 384 x 384 px, and more than one permutation if the watch face is customizable.
• Android TV: at least one Android TV screenshot before you can publish, plus a TV banner of 1280 x 720 px (JPEG or 24-bit PNG, no alpha). TV screenshots are only displayed on Android TV devices.
• Android Automotive OS: if you provide screenshots, at least 2 portrait (800 x 1,280 px) and 2 landscape (1,024 x 768 px) images that show the generic system UI rather than a specific vehicle model.
• Android XR: between 4 and 8 screenshots, PNG or JPEG, up to 8 MB each, 8:5 aspect ratio; 3840 x 2400 px recommended, 1920 x 1200 px minimum.

If your app only targets phones, you can ignore most of this list. If it also runs on tablets, add the large-screen set: phone screenshots stretched onto a tablet listing do not show what the app really looks like there.

Screenshots are not the only graphics Google asks for. The preview assets page says you must also provide an app icon, a short description and a feature graphic to publish a store listing:

• App icon: 512 x 512 px, 32-bit PNG with alpha, maximum file size 1024 KB.
• Feature graphic: 1024 x 500 px, JPEG or 24-bit PNG with no alpha.
• Short description: 80 characters maximum.
• Preview video (optional): one YouTube URL, set to public or unlisted, not age-restricted, embeddable, and with ads turned off.

Google's icon design specifications add that the icon should be a full square in the sRGB color space, without rounded corners or a drop shadow of its own, because Google Play applies the rounded mask and shadow automatically after upload.

The feature graphic doubles as the cover image for your preview video when you have one. Google recommends keeping the focal point near the center, avoiding fine detail that will not be visible on phone screens, and avoiding pure white, black or dark gray, which can blend into the Play Store background. Only the first 30 seconds of a preview video may autoplay, muted, so the app experience should appear early.

Correct pixel dimensions will not help if the content breaks the rules. Google's Metadata policy does not allow misleading, irrelevant, excessive or inappropriate metadata, and it names screenshots and promotional images explicitly. The policy lists images or text that indicate store performance or ranking, price and promotional information, or Google Play programs as common violations. The preview assets guidelines add the following for screenshots:

• Show the real product: screenshots must demonstrate the actual in-app or in-game experience, using captured footage of the app itself.
• No ranking or price claims: avoid words such as "Best", "#1", "Top", "New", "Discount", "Sale" or "Million Downloads".
• No calls to action: avoid "Download now", "Install now", "Play now" or "Try now".
• Keep taglines small: add them only if needed, and they should not take up more than 20% of the image.
• No hands or device imagery: do not show people interacting with the device unless the app is used off-device, and avoid device frames, which Google says can become obsolete quickly or alienate some users.
• Clean status bar: remove notifications and carrier names; battery, WiFi and cell service icons should be full.
• No distortion: do not upload blurry, pixelated, stretched, compressed, sideways or upside-down images.
• No store badges or unlicensed logos: leave out Google Play or other store badges and third-party trademarks you do not have permission to use.

Google also asks for alt text on each screenshot and graphic, in 140 characters or less, and without phrases like "photo of" or "image of" because screen readers already announce that. It is a small job that makes the listing usable for people who rely on assistive technology.

If you are launching on both stores, you cannot reuse one set of images without checking. Apple works from exact pixel sizes per device family rather than a flexible range. Apple's screenshot specifications for App Store Connect say you must include at least one screenshot and can upload up to 10 per device size in .jpeg, .jpg or .png format, and that images cannot include alpha channels or transparencies.

• Number allowed: Google Play up to 8 per device type; App Store up to 10 per device size.
• Minimum to publish: Google Play two screenshots; App Store at least one for each required display size.
• Dimensions: Google Play any size from 320 px to 3,840 px within a 2:1 limit; App Store fixed sizes, for example 1179 x 2556 px or 1206 x 2622 px portrait for iPhone with Dynamic Island (medium display).
• Required sets: Apple currently lists iPhone with Dynamic Island (medium display) as the required iPhone size, plus iPad 13-inch if the app supports iPadOS, and scales screenshots down for smaller devices.
• Transparency: not allowed in screenshots on either store.

A typical iPhone screenshot is taller than 2:1 (1179 x 2556 px is about 2.17 times as tall as it is wide), so by Google's rule it would need to be cropped or re-composed before it could be used on Google Play. Plan two export sizes from the same design file rather than one. Store graphics are a small line in a launch budget, but they are easy to forget; our mobile app development cost breakdown for 2026 covers the larger items.

• Step 1 - Choose the screens: pick four to eight screens that show the core features. Google recommends prioritizing real UI in the first three screenshots.
• Step 2 - Capture real screens: take captures from the app itself on a device or emulator, with a clean status bar and no notifications.
• Step 3 - Export at 1080 x 1920 px: use portrait 9:16 for a portrait app, or 1920 x 1080 px for a landscape app. Save as JPEG or 24-bit PNG with no transparency.
• Step 4 - Check the limits: confirm each side is between 320 px and 3,840 px and the long side is no more than twice the short side.
• Step 5 - Add a short tagline only if it helps: keep it under 20% of the image, readable at phone size, and free of ranking, price or call-to-action wording.
• Step 6 - Upload in Play Console: go to Grow users > Store presence > Main store listing and add the images in the Graphics section, under the right device type.
• Step 7 - Add alt text and the other assets: write alt text for each image, then upload the 512 x 512 px icon and the 1024 x 500 px feature graphic.
• Step 8 - Localize: Google recommends localizing taglines and text overlays for each market and language you target.

Google notes that assets appear on your store listing across all test tracks once you add them, so it is worth getting them right before testers see the page. If you would rather hand the design work to a team, our UI/UX design service and mobile app development service cover app interfaces and store launches.

Use this short checklist against Google's published rules before you press save:

• Too tall: a raw capture from a modern tall phone is often over the 2:1 limit and must be cropped.
• Transparent PNG: screenshots and the feature graphic must have no alpha channel; only the app icon uses a 32-bit PNG with alpha.
• Too few images: two is the minimum to publish, but four at 1080 px or more is the guideline for screenshot-based recommendation formats.
• Marketing claims in the image: ranking, award, price, discount and "download now" wording goes against Google's guidelines.
• Mock-ups instead of the app: screenshots should reflect the actual experience of the current version.
• Out-of-date screens: Google asks you to avoid time-sensitive content and to swap seasonal images in and out promptly.
• Wrong device section: tablet, Wear OS, TV, car and XR screenshots each have their own section and rules.

All sources were opened and checked on November 10, 2026. Store requirements change, so confirm the current figures in Play Console and App Store Connect before a launch.

Play Console Help: Add preview assets to showcase your app (screenshot, feature graphic, icon, short description, video and TV banner requirements).

Android Developers: Google Play icon design specifications (512 x 512 px icon, sRGB, masking and shadows).

Play Console Help: Metadata policy (what is not allowed in titles, icons, screenshots and promotional images).

Apple Developer: Screenshot specifications (App Store Connect Help) (App Store screenshot counts, formats and device sizes).