Updated: July 27, 2026
To compress images for App Store and Google Play listings, first export each asset at a platform-approved pixel size. Use JPEG as a starting format for photo-heavy artwork and lossless-optimized PNG for screenshots with small text or flat UI. Remove alpha from Apple screenshots and from Google Play screenshots and feature graphics, but preserve the Google Play app icon's required 32-bit PNG format with alpha. Google Play assets that specify 24-bit PNG must not be submitted as indexed palette PNGs. Finally, verify dimensions, color type, channels, and visual quality before uploading.
Key Takeaways
- Resize from a high-resolution master to an accepted platform size before compression.
- Apple accepts JPEG, JPG, and PNG screenshots without alpha. It allows one to ten screenshots.
- For iPhone, provide an accepted 6.9-inch screenshot size or use an accepted 6.5-inch size as the required fallback.
- General Google Play screenshots can use ratios other than 16:9 and 9:16 if they satisfy the 320–3840 pixel and 2:1 long-side limit.
- Google Play screenshots and feature graphics require JPEG or 24-bit PNG without alpha. Its app icon is the important exception: 32-bit PNG with alpha.
- Inspect compressed files locally at 100% zoom. Use store previews to check cropping, order, and overall presentation.
App Store vs Google Play: What to Check Before Compression
A file can be small and still fail validation. Compression does not correct the wrong pixel dimensions, an unsupported PNG color type, or an unwanted alpha channel.
Use this comparison before creating export presets:
| Platform asset | Dimensions | Format and color rules | Quantity or limit | Rule type |
|---|---|---|---|---|
| App Store iPhone screenshot | Accepted 6.9-inch or 6.5-inch fallback size | JPEG, JPG, or PNG; no alpha | 1–10 screenshots | Required for an iPhone app |
| App Store iPad screenshot | 2064 × 2752 or 2048 × 2732 portrait; landscape equivalents accepted | JPEG, JPG, or PNG; no alpha | 1–10 screenshots | Required if the app runs on iPad |
| Google Play app icon | 512 × 512 | 32-bit PNG with alpha | Maximum 1024 KB | Required |
| Google Play feature graphic | 1024 × 500 | JPEG or 24-bit PNG; no alpha | One graphic | Required |
| General Google Play screenshot | Each side 320–3840 px; long side no more than twice the short side | JPEG or 24-bit PNG; no alpha | At least 2 across device types; up to 8 per device type | Required |
| Google Play tablet or Chromebook set | 1080–7680 px; 16:9 landscape or 9:16 portrait | JPEG or 24-bit PNG; no alpha | At least 4 in the device-specific set | Device-specific |
Apple's current screenshot specification page does not state a universal screenshot file-size ceiling. Do not treat an arbitrary target such as 1 MB or 3 MB as an App Store rule. Optimize until further reductions would visibly damage text, gradients, or interface details.
App Store Screenshot Requirements
Apple accepts one to ten screenshots in .jpeg, .jpg, or .png format. Screenshots cannot include alpha channels or transparency. The complete list varies by Apple platform and device class, so consult Apple's current screenshot specifications before every release.
Current iPhone and iPad Sizes
| Display class | Portrait sizes | Landscape sizes | How Apple uses the set |
|---|---|---|---|
| iPhone 6.9-inch | 1260 × 2736, 1290 × 2796, or 1320 × 2868 | 2736 × 1260, 2796 × 1290, or 2868 × 1320 | Preferred high-resolution iPhone set |
| iPhone 6.5-inch | 1242 × 2688 or 1284 × 2778 | 2688 × 1242 or 2778 × 1284 | Required fallback when a 6.9-inch set is not supplied |
| iPad 13-inch | 2048 × 2732 or 2064 × 2752 | 2732 × 2048 or 2752 × 2064 | Required if the app runs on iPad |
If the interface is the same across device sizes, Apple recommends supplying the required highest-resolution screenshots and lets App Store Connect scale them for smaller devices. You can upload device-specific alternatives through Media Manager when scaling would make the composition, text, or device framing unsuitable.
Do not invent a generic “2×” or “3×” canvas and expect App Store Connect to accept it. Export an exact size from Apple's table, directly from your high-resolution master.
Apple App Icons Follow the Build Workflow
Do not treat the Apple app icon as another listing screenshot. Apple currently directs developers to create the icon with Icon Composer or add it to an Xcode asset catalog, then upload it with the app build. Follow Apple's app icon workflow when changing the icon.
Google Play Listing Image Requirements
Google Play applies different channel and color-type rules to its icon, feature graphic, and screenshots. A “PNG” export is not automatically compliant.
| Asset | Required output | Alpha | Other requirements |
|---|---|---|---|
| App icon | 512 × 512, 32-bit PNG | Required by the specified format | Maximum 1024 KB |
| Feature graphic | 1024 × 500, JPEG or 24-bit PNG | Not allowed | Keep important content near the center and outside Google's illustrated cutoff zones |
| General screenshot | JPEG or 24-bit PNG, 320–3840 px per side | Not allowed | Long side cannot exceed twice the short side |
| Tablet or Chromebook screenshot | JPEG or 24-bit PNG, 1080–7680 px | Not allowed | 16:9 landscape or 9:16 portrait |
Google requires at least two screenshots across device types to publish a store listing. You can add up to eight screenshots for each supported device type.
Required Rules vs Recommended Display Specs
The general upload rules and the requirements for additional promotional visibility are not identical:
| Use case | Number | Resolution and ratio |
|---|---|---|
| Publish a general listing | At least 2 screenshots across device types | 320–3840 px; long side no more than 2× the short side |
| Make an app eligible for recommended placements that use screenshots | At least 4 app screenshots | At least 1920 × 1080 landscape at 16:9 or 1080 × 1920 portrait at 9:16 |
| Submit a tablet or Chromebook screenshot set | At least 4 screenshots in that set | 1080–7680 px; 16:9 landscape or 9:16 portrait |
Therefore, a 4:3 screenshot can satisfy the general geometric upload rule, while 16:9 or 9:16 assets are needed for the specified recommendation formats. Review Google's preview asset requirements for additional rules covering Wear OS, Android TV, Automotive, and Android XR.
PNG or JPEG: Which Format Should You Use?
Choose a format by both image content and platform requirements.
| Image content or asset | Starting format | Compression approach | Inspect for |
|---|---|---|---|
| UI screenshot with small text or thin lines | PNG | Preserve truecolor PNG24 for a cross-store Google Play-compatible output; apply lossless optimization | Altered colors, missing lines, incorrect color type |
| Photo-heavy screenshot | JPEG | Test several quality settings rather than assuming one universal value | Blocking, ringing, lost texture |
| Gradient-heavy onboarding artwork | JPEG or PNG24 | Compare both formats at the same dimensions | Banding and color shifts |
| Google Play feature graphic | JPEG or PNG24 | Use PNG24 for especially sharp text; JPEG may be smaller for photographic art | Cutoff risk, alpha, text clarity |
| Google Play app icon | 32-bit PNG with alpha | Optimize without removing its required alpha channel | File size above 1024 KB |
| Apple screenshot | JPEG, JPG, or PNG | Choose by content, but always remove alpha | Transparency, soft text, wrong dimensions |
JPEG quality values around 85–90 can be a useful starting range, but they are not store requirements. Encoders and image content differ, so compare more than one result. A lower setting may be acceptable for a photograph yet visibly damage high-contrast text.
Indexed palette PNGs can be efficient for flat graphics, but Google Play explicitly calls for 24-bit PNG for screenshots and feature graphics. Tools such as pngquant normally generate palette output, so their result should not be used directly for those Google Play assets.
Step-by-Step Compression Workflow
1. Keep an Untouched Master
Maintain the original design export separately from every compressed derivative. Use filenames that make the platform, device class, orientation, and format obvious:
dashboard-master.png
dashboard-ios-69-1320x2868.png
dashboard-play-phone-1080x1920.png
dashboard-play-phone-1080x1920.jpg
Never upscale a compressed screenshot to create another store size. Return to the master and export every target independently.
2. Export at an Accepted Size
For Apple, select an exact pixel size from the official device table. For Google Play, distinguish between the flexible general screenshot rules and the stricter ratios used by tablet sets or recommended placements.
Convert the document to sRGB before export, then confirm that the exported dimensions—not merely the design-tool canvas label—match the target.
3. Remove Alpha Only Where Required
Flatten Apple screenshots, Google Play screenshots, and the Google Play feature graphic onto an intentional background color. Do not apply this step to the Google Play app icon.
The following ImageMagick command flattens transparency onto white and creates a separate truecolor PNG24 file:
magick screenshot-master.png \
-background white \
-alpha remove \
-alpha off \
-colorspace sRGB \
-strip \
PNG24:screenshot-google-png24.png
Replace white with the background color intended by the design. Keeping a separate output protects the master file.
4. Compress Without Changing Compliance-Critical Properties
For a photo-heavy asset, create a JPEG candidate:
magick screenshot-master.png \
-background white \
-alpha remove \
-alpha off \
-colorspace sRGB \
-strip \
-sampling-factor 4:4:4 \
-interlace Plane \
-quality 88 \
screenshot-q88.jpg
Create additional candidates at nearby quality settings and compare them locally. The smallest file is not necessarily the best result.
For a Google Play PNG24 asset, use lossless optimization while preventing automatic conversion to a palette color type:
oxipng -o 3 \
--strip safe \
--nx \
--out screenshot-google-optimized.png \
screenshot-google-png24.png
File-size reduction varies with the source. A truecolor UI screenshot may remain larger than JPEG, but it can preserve text and flat-color edges better.
For a browser-based option, LessMB can compress JPEG and PNG files locally in your browser. Use it for the compression step, then verify dimensions, PNG color type, and alpha-channel compliance separately; it does not replace the platform checks below.
5. Check Dimensions, Bit Depth, and Alpha
Use ImageMagick to display the properties that matter:
magick identify \
-format '%f | %wx%h | depth=%z | colorspace=%[colorspace] | channels=%[channels] | type=%[type] | class=%[class]\n' \
screenshot-google-optimized.png
For a Google Play PNG24 screenshot, look for:
- The intended width and height.
- Eight bits per RGB channel.
- RGB or sRGB channels without
a. TrueColorandDirectClass, rather thanPaletteorPseudoClass.
ImageMagick's labels can vary by version. As a second check, run:
file screenshot-google-optimized.png
A typical PNG24 result is described as 8-bit/color RGB. That means three eight-bit channels, or 24 bits in total. Watch for these failure signals:
RGBA,srgba,TrueColorAlpha, orPaletteAlpha: an alpha channel is present.Palette,PseudoClass, orcolormap: the file is indexed rather than truecolor PNG24.16-bit/color: the export is not the expected eight-bits-per-channel PNG24 output.
6. Perform a Visual and Upload Check
Inspect each local file at 100% zoom and check:
- Small text remains readable.
- One-pixel lines and icons remain intact.
- Gradients do not show distracting bands.
- JPEG edges do not have obvious halos.
- Brand colors match the source.
- No unintended background appeared when alpha was removed.
After uploading, use App Store Connect or Play Console to confirm sequence, orientation, cropping, and the relationship between adjacent screenshots. The console preview can be scaled or cropped for different surfaces, so do not use it as a substitute for the local pixel-level inspection.
Upload-Ready Verification Checklist
- Every asset was exported from an untouched high-resolution master.
- Apple screenshots use an exact accepted device size.
- The iPhone set contains an accepted 6.9-inch size or an accepted 6.5-inch fallback size.
- An iPad app includes an accepted 13-inch screenshot set.
- Apple screenshots contain no alpha channel.
- The Google Play icon is 512 × 512, 32-bit PNG with alpha, and no larger than 1024 KB.
- The Google Play feature graphic is exactly 1024 × 500.
- Google Play screenshots and the feature graphic are JPEG or truecolor PNG24 without alpha.
- General Play screenshots stay within 320–3840 px, with the long side no more than twice the short side.
- Assets intended for Play recommendation formats or large-screen sets meet their separate ratio, resolution, and count rules.
- Every file was visually inspected locally at 100% zoom.
- Store previews were checked for crop, order, orientation, and overall composition.
Why Compressed Listing Images Still Fail Validation
| Symptom | Likely cause | Fix |
|---|---|---|
| Apple rejects a correctly named PNG | It contains alpha or uses an unsupported pixel size | Flatten transparency and export an exact accepted Apple size |
| The Play feature graphic fails | It is not 1024 × 500, contains alpha, or is an indexed PNG | Export JPEG or truecolor PNG24 without alpha |
| A Play screenshot fails despite using PNG | The compressor converted it to palette PNG | Re-export as PNG24 or use JPEG |
| The Play app icon fails | It lacks the specified 32-bit alpha format or exceeds 1024 KB | Restore the alpha-capable PNG and optimize within the official limit |
| UI text looks fuzzy | JPEG compression is too aggressive | Raise quality or use PNG where permitted |
| A gradient develops bands | The quality or color reduction is too aggressive | Compare a higher JPEG setting with PNG24 |
| A screenshot has the right ratio but fails on Apple | Apple requires exact device-class pixel dimensions | Export an exact size from Apple's current table |
| A Play screenshot is valid but misses promotional placements | It meets general rules but not the recommendation specifications | Supply the required number of 16:9 or 9:16 high-resolution screenshots |
| Colors change after export | The source and output color spaces differ | Convert the master to sRGB before exporting and compare the result |
FAQ
Does the App Store accept transparent PNG screenshots?
No. Apple accepts JPEG, JPG, and PNG screenshots, but its screenshot specifications prohibit alpha channels and transparency. Flatten the screenshot onto the intended solid background before upload.
This rule applies to screenshots. Apple app icons follow the separate Icon Composer or Xcode asset-catalog build workflow.
What size is the Google Play feature graphic?
The feature graphic must be exactly 1024 × 500 pixels. Export it as JPEG or 24-bit PNG without alpha.
Google advises keeping the focal point and important elements near the center and outside the cutoff zones shown in its official guidance. It does not define those zones as a fixed “central 60%.”
Should I use PNG or JPEG for app screenshots?
Start with PNG for small text, thin lines, icons, and flat UI colors. Start with JPEG for photography and complex continuous-tone artwork.
Then compare the candidates at 100% zoom. Format choice is a starting decision, not a guarantee: gradients may favor a carefully encoded JPEG, while text-heavy screens often remain cleaner as PNG.
What aspect ratio should Google Play screenshots use?
General screenshots do not have to be 16:9 or 9:16. Both dimensions must be between 320 and 3840 pixels, and the long side cannot be more than twice the short side.
Google uses stricter 16:9 or 9:16 guidance for recommended placements and for tablet or Chromebook screenshot sets. Apply the rule that matches the intended device section and placement.
Does Google Play require 24-bit PNG screenshots?
Yes, when you choose PNG for general screenshots or the feature graphic. In this context, 24-bit PNG means truecolor RGB with eight bits per channel and no alpha.
A PNG identified as palette, indexed, colormap, or PseudoClass is not the same format.
Can I use pngquant for Google Play screenshots?
Do not use its normal output as the final Google Play screenshot or feature graphic. pngquant typically converts images to an indexed palette, while Google requires 24-bit PNG for these assets.
If palette reduction is part of an Apple-only workflow, verify the resulting Apple screenshot still has an accepted size, supported format, no alpha, and acceptable visual quality.
What is the maximum file size for App Store screenshots?
Apple's current screenshot specifications do not list one universal public megabyte limit. Follow the accepted dimensions and formats, remove alpha, and compress only as far as visual quality allows.
Do not present an internal team target as an Apple limit.
How many screenshots do App Store and Google Play require?
Apple allows a minimum of one and a maximum of ten screenshots. If the same interface is used across device sizes, Apple can scale the supplied required high-resolution screenshots to smaller sizes.
Google Play requires at least two screenshots across device types and permits up to eight for each supported device type. Tablet, Chromebook, Wear OS, Android TV, Automotive, Android XR, and promotional-placement rules may require additional assets.
Sources
- Apple Developer, Screenshot specifications
- Apple Developer, Upload app previews and screenshots
- Apple Developer, Add an app icon
- Google Play Console Help, Add preview assets to showcase your app