App Store Connect and the Play Console both accept enormous image files without complaint — right up until slow uploads, a bloated app bundle, or a rejected listing tell you otherwise. Compressing images before submission isn't optional busywork; it's the difference between a snappy listing and one that quietly hurts your conversion rate. Here's how to do it without the screenshots looking noticeably worse.
Which images actually need compressing
Three categories, each with a different target:
- Store screenshots — the images shown in the App Store or Play Store listing itself. These are usually PNG exports from a design tool and can easily run 3-8 MB each before compression.
- In-app image assets — icons, illustrations, and photos bundled inside the app binary. These directly add to your download size.
- Marketing/feature graphics — the Play Store's feature graphic, promotional images, and anything used outside the app itself.
The setting that matters most: quality, not just format
Switching to a modern format helps, but the single biggest lever is the quality setting on export. Most screenshots and photos hold up fine at 70-85% JPEG or WebP quality — the difference from 100% is invisible at normal viewing size, but the file size difference is often 60-80%.
Which format to export as
| Use case | Best format | Why |
|---|---|---|
| App Store / Play Store screenshots | PNG or high-quality JPEG | Both stores accept PNG and JPEG; PNG is required for some transparent overlays. |
| In-app photos | WebP or AVIF | 20-50% smaller than JPEG at equal visual quality, supported on modern Android/iOS. |
| In-app icons and flat-color graphics | PNG | Lossless, and flat colors compress well without needing a photo-oriented format. |
Step by step with a batch tool
- Open the image compressor and drop in every screenshot or asset you need to prepare — it accepts a full batch at once, not one file at a time.
- Pick a target format: JPEG for universal compatibility, WebP or AVIF for smaller files on modern platforms.
- Adjust the quality slider while watching the live before/after preview — stop as soon as you can no longer tell the difference at normal zoom.
- Compress the whole batch and download it as a single ZIP.
If you also need to resize (many screenshot tools export at a higher resolution than the store requires), the compressor's resize option handles that in the same pass — no need for a separate step.
Compress your screenshots and assets now
Batch JPEG, PNG, WebP, and AVIF compression with a live before/after preview — free.
Don't forget the screenshots themselves
If you haven't generated your store screenshots yet, doing it with the right tool avoids the compression problem at the source — the screenshot generator exports directly at the exact pixel sizes App Store Connect and the Play Console require, so there's no oversized export to compress down in the first place.
FAQ
What's the maximum screenshot file size for the App Store?
Apple accepts screenshots up to 500 MB each, but that's not a target to hit — under 1-2 MB per screenshot is plenty for full quality and uploads far faster.
Does compressing images affect app review?
No — reviewers judge screenshots on how they represent the app, not file size. Compression only affects upload speed and, for in-app assets, your final download size.
Should I compress images before or after resizing?
Resize first, then compress — compressing an oversized image and then shrinking it wastes the compression pass, since resizing changes the pixel data again.