Table of contents
- Quick nav
Batch Export App Store Screenshots: Multi-Size ZIP, No Alpha
After you finish a screenshot set, the slow part is rarely the headline copy. It is exporting the same frames at several pixel sizes and making sure none of them still carry an alpha channel. App Store Connect and Google Play both reject transparent screenshots; discovering that at upload time costs a full round trip.
We built that workflow into a local tool: the batch image processor. Drop up to ~300 images, multi-select store sizes, choose pad or crop, pick an output format, optionally force opaque 24-bit PNG, then download a ZIP with one folder per size. Everything runs in the browser; source files are not uploaded.
Size presets stay aligned with our store screenshot size guide. Specs cited here were checked on October 29, 2026 against Apple’s screenshot specifications and Google Play preview assets. If Console UI and the help page disagree, trust the Console for that submission.
How this splits from strategy posts and single-image tools
| Job | Where |
|---|---|
| China Android multi-store size/count strategy | Multi-channel Android batch workflow |
| Already-designed frames → many pixel sizes + no alpha + ZIP | /en/tools/batch-processor (this article) |
| Design store frames from scratch | /en/preview |
| Recheck pixels / format / file size after export | /en/tools/screenshot-check |
This page does not rewrite channel strategy. It covers which presets to tick, how padding works, and how we strip alpha.
Required vs optional sizes (do not pitch optional sizes as required)
| Slot | Common portrait pixels | Required? (as of Oct 29, 2026) |
|---|---|---|
| App Store iPhone Dynamic Island medium | 1206×2622 or 1179×2556 | Required (at least one) |
| App Store iPhone 6.9″ large | 1320×2868 / 1290×2796 / 1260×2736 | Optional; Connect may scale from other sets |
| App Store iPad 13″ | 2064×2752 or 2048×2732 | Required if the app supports iPadOS |
| Google Play phone screenshots | Often 1080×1920 (9:16); sides 320–3840, longer ≤ 2× shorter | At least two screenshots across device types to publish |
| Google Play Feature Graphic | 1024×500 | Required to publish, but not a screenshot slot |
Live presets in the batch tool today: iPhone 6.9″ / 6.5″ / 6.3″ / 5.5″, iPad 13″, Android 1080×1920, tablet 1440×2560, Honor-style 720×1280. Landscape sources export landscape dimensions automatically.
Hands-on: drop files → ZIP
- Open /en/tools/batch-processor and drop finished PNG/JPG/WebP frames (simulator captures or /en/preview exports).
- Choose store sizes and tick what you will upload. A practical minimum: 6.3″ (required) + 6.9″ (optional large) + Android 1080; add iPad 13″ when you ship iPad.
- When aspect ratios differ, prefer Fit (pad)—edge color fill keeps the full UI. Use Fill (crop) only when you designed with crop room. Avoid stretch.
- For store uploads, export PNG with remove-alpha enabled (true 24-bit RGB, no alpha) or JPEG. Both stores reject transparent screenshots.
- Optionally enable smart PNG compression or switch to JPG/WebP for size. Name templates accept
{name},{n},{w},{h},{size}. - Run processing, check before/after dimensions and bytes in the list, then download the ZIP (folder per size).
- Spot-check a few files in /en/tools/screenshot-check before App Store Connect or Play Console.
Pad vs crop vs redesign
| Approach | Best for | Watch-outs |
|---|---|---|
| Batch pad | iPhone 9:19.5 → Play 9:16 while keeping full UI | Color bars; match pad color to the art |
| Center crop | Layouts with intentional edge margin | Can clip status bar or tab bar |
| Recompose on the target canvas, then batch | Headlines near the edge | Extra step, fewest surprises |
If frames still include device chrome or busy backgrounds, finish them in /en/preview at the target preset first, then batch only aligned finals.
What we shipped for alpha and metadata
- Remove alpha: transparent pixels are filled; PNG is written as 24-bit RGB so “looks solid but still has alpha” does not slip through.
- Re-encode: outputs drop EXIF/GPS and related metadata (canvas redraw + encode).
- Local: resize, encode, and JSZip packaging stay in the browser; encoders load from
/vendor/on this site.
Background removal for cutouts belongs in /en/tools/remove-bg—that is matting, not store opaque export. Listing screenshots should sit on a solid base first; then batch-remove alpha as a safety net.
Common failure modes we see in practice
| Symptom | Likely cause | Fix in this tool |
|---|---|---|
| Connect rejects “alpha channel” | Designer exported 32-bit PNG | Enable remove-alpha; re-export PNG or JPEG |
| Play says dimensions invalid | Long side > 2× short, or outside 320–3840 | Prefer 1080×1920 preset; avoid ultra-wide crops |
| Wrong display class in Connect | 6.9″ file dropped into medium slot | Keep ZIP folders; upload folder contents to matching buckets |
| Soft edges after pad | Pad color clashes with art | Use auto edge color or set an explicit brand fill |
Pair with /en/tools/compress only after dimensions are correct—shrinking a wrong-size file does not fix the slot.
30-second upload checklist
- Required buckets present: iPhone medium; iPad 13″ when applicable.
- Spot-check that pixel sizes match the folder names (do not upload a 6.9″ file into the 6.3″ slot).
- Compliance check: no alpha, sane file size.
- Feature Graphic still goes through /en/tools/feature-graphic—do not force a portrait screenshot into 1024×500.
Need a looping demo for a landing page or README? Use images to GIF. That is off-store marketing—not a substitute for an App Store app preview video.