PNG / JPG / WebP and more, up to 300 at once
What this tool does
Shipping an app usually means exporting the same screenshots in several sizes: App Store iPhone 6.9″ (1320×2868), 6.5″ (1284×2778) and iPad 13″ (2064×2752), plus 1080×1920 for Google Play and most Android stores. When we prepare store assets ourselves, the slow part isn't design — it's the repetitive resizing, format conversion and removing the alpha channel. Neither App Store Connect nor Google Play accepts screenshots with transparency, and finding out at upload time wastes a round trip. This batch tool follows that workflow: drop in many screenshots, tick the store sizes you need (any combination; landscape images get landscape sizes automatically), and choose whether a mismatched aspect ratio is padded or cropped — padding uses the screenshot's edge color by default. Output PNG, JPG, WebP or keep the original format. With alpha removed, PNGs are written as true 24-bit RGB PNGs with no alpha channel; JPG and WebP are encoded with the open-source MozJPEG and libwebp, which are smaller than the browser's built-in encoders at the same quality, and smart palette PNG compression is optional. File names accept {name}, {n}, {w}, {h} and {size} templates, the list shows every image's before/after dimensions and file size, and one click downloads a ZIP with a folder per size. Everything runs in your browser; images are never uploaded, and re-encoded files carry no EXIF, GPS or other metadata. Sizes come from the same data as our App Store screenshot size guide — always confirm against each store's official specs.
How to use
- Click or drop multiple screenshots (PNG, JPG, WebP…, up to 300 at once).
- Choose how to size them: store sizes (multi-select), keep size, custom W×H, fit to width or a percentage; pick pad or crop for mismatched ratios.
- Choose the output format and quality, remove alpha and set a file-name template if needed, click Process, then check the before/after sizes and download single files or the ZIP.
FAQ
Are my images uploaded?
No. Reading, resizing, encoding and zipping all happen in your browser. The encoders load from this site's /vendor/ folder and run locally; the page never sends your images to a server.
Why remove the alpha channel?
App Store Connect rejects screenshots with an alpha channel, and Google Play asks for JPEG or 24-bit PNG without transparency. With this on, transparent areas are filled with the background color and PNGs are written as 24-bit RGB with no alpha channel, so uploads aren't rejected for transparency.
What if my screenshot ratio doesn't match the store size?
For example, turning a 9:19.5 iPhone screenshot into 1080×1920 (9:16): Fit (pad) keeps the whole image and fills the sides with the background color; Fill (crop) trims the overflow from the center; Stretch distorts and is rarely a good idea. The pad color defaults to the screenshot's edge color, or you can pick one.
Does it strip EXIF and GPS data?
Yes. Every image is redrawn on a canvas and re-encoded, so the output holds only pixels — no EXIF, camera details, GPS location or other metadata from the original.
How many images can I process, and how fast?
Up to 300 at once. Each image is exported once per checked size. Speed depends on image size and your computer; typical screenshots take under a second each. Smart PNG compression is slower, and you can press Stop at any time.
Which open-source projects are used, and under what license?
JPG and WebP encoding uses MozJPEG (libjpeg-turbo's IJG / BSD-3-Clause licenses) and libwebp (BSD-3-Clause) via jSquash (Apache-2.0); smart PNG compression uses pngdeer (MIT); ZIP files are built with JSZip (dual MIT / GPLv3, used here under MIT). All allow commercial use; see the jSquash / MozJPEG / libwebp licenses and the pngdeer licenses.
Related guides & tools
More tools in thedeveloper toolbox. For store preview shots, try theApp Store screenshot maker.