Responsive layouts
Adapt one design across all 17 named export targets in 7 stores, plus custom canvases from 200 to 7680 px per side.
Exact sizes, alpha channels, and the 2:1 aspect-ratio cap
Fix Screenshot Wrong Dimensions on App Store Connect and Play Console
Match your screenshot to the size the store expects, strip the alpha channel that causes most App Store Connect rejections, and stay inside Google Play's 2:1 aspect-ratio cap.
223Unique template sets
146Built-in app screens
85Caption languages
Exact sizes, alpha channels, and the 2:1 aspect-ratio cap
Match the size the store expects, then upload again
Each store rejects for a different reason: Apple wants one of a short list of exact pixel sizes and no transparency, Google accepts a range of sizes but caps how tall a screenshot may be relative to its width.
Responsive layoutsLocalizationDevices and backgroundsPreview and export
Template library
Start with a responsive screenshot template
Choose from 223 unique template sets covering 1,784 pages, replace the sample screens and captions, then adapt the same design across supported export targets.
Exact sizes, alpha channels, and the 2:1 aspect-ratio cap
Match the size the store expects, then upload again
Each store rejects for a different reason: Apple wants one of a short list of exact pixel sizes and no transparency, Google accepts a range of sizes but caps how tall a screenshot may be relative to its width.
1App StoreSelect your app
Select your app
Add your app metadata to begin.
App StoreSelect your appThe store rules, verified
Store requirements, checked against the source
Three rejections stop almost every screenshot upload: the file is not one of the exact sizes Apple accepts, it carries an alpha channel, or it is taller than Google's aspect-ratio cap allows. Here are the numbers each store enforces and how to recover from each failure. Check Apple and Google's current requirements before export because both can change them.
The three rejections, and what each one means
The error text differs between the two consoles, but the underlying causes do not.
- Wrong pixel size, on Apple. App Store Connect accepts only the exact dimensions listed for each display class. A file that is one pixel out in either direction fails validation — there is no tolerance and no automatic resize.
- An alpha channel, on both stores. Apple's rule is that images can't include alpha channels or transparencies; Google specifies JPEG or 24-bit PNG with no alpha. Most design tools write an alpha channel into a PNG even when the artwork is completely opaque, which is why this rejection is the most common and the hardest to see.
- Aspect ratio, on Google. The longest side may be no more than twice the shortest. 1080×2400 — the native resolution of a great many Android phones — is 2.22 times taller than it is wide and is refused. 1080×2160 sits exactly on the limit and 1080×1920 is comfortably inside it.
The sizes App Store Connect accepts
| Display class | Accepted pixel sizes (portrait) | When Apple requires it |
|---|---|---|
| iPhone 6.9-inch class | 1290×2796, 1260×2736, or 1320×2868 | Required when the app runs on iPhone |
| iPhone 6.5-inch class | 1284×2778 or 1242×2688 | Required when the app runs on iPhone and no 6.9-inch set is provided |
| iPhone 6.3-inch class | 1179×2556 or 1206×2622 | Optional — Apple scales the 6.5-inch set down |
| iPad 13-inch class | 2064×2752 or 2048×2732 | Required when the app runs on iPad |
How to fix each one
Wrong size: re-export at the target size rather than scaling the file you already have. Scaling 1284×2778 up to 1290×2796 softens every caption baked into the image and often still lands a pixel out, so the second upload fails for the same reason as the first.
Alpha channel: flatten the artwork onto an opaque background and export again, or export JPEG. Deleting the transparent layer in the design is not enough on its own — the encoder can still write an alpha channel into the file.
Aspect ratio: crop or pad to a permitted shape such as 1080×2160 or 1080×1920. Stretching to fit distorts the device frame and the type, and reviewers notice.
Colour: export in a standard RGB colour space. Shipshot embeds an sRGB profile, which both stores accept.
Which sizes you actually have to supply
Only two Apple sets are strictly required: the iPhone 6.9-inch set when the app runs on iPhone, and the iPad 13-inch set when it runs on iPad. Apple scales those down for the smaller classes, so a missing 6.5-inch set is not a rejection.
Scaling is safe for full-bleed artwork and unkind to text. If your captions are part of the image, export the 6.5-inch set as well so the iPhone Pro Max class renders at native resolution instead of a resized approximation.
How Shipshot handles this
Shipshot exports at exactly the dimensions each store lists, flattened, with no alpha channel and an embedded sRGB profile, so the files pass validation as downloaded rather than after a round of repairs. You upload them yourself in App Store Connect or Play Console. Pro and Scale can also push a saved ZIP into a listing version.
Everything you need for the next screenshot set
Localization
Qwen translates missing editable captions across all 85 caption languages, with 8 curated core languages featured in the editor; review and edit every result before export. Translation and non-English preview need Pro or Scale; free projects stay in English.
Devices and backgrounds
Use real device frames, frameless screens, soft clay renders, and angled poses.
Preview and export
Export store-ready files for manual upload to App Store Connect and Google Play Console. Pro and Scale can also push a saved ZIP into those listing versions.
Editable caption workflow
Write and refine benefit-led captions for each supported preview language.
Plans that match your workflow
Basic includes 1 project, up to 5 screenshots per size, and watermarked exports for all 17 store targets. Pro includes 10 projects, 10 screenshots per size, and English + 5 additional locales (6 total). Scale includes unlimited projects, 25 screenshots per size, all 85 caption languages, and an extended licence. Every plan exports the same 17 store targets for manual upload.
Frequently asked questions
Screenshot workflow questions
App Store Connect says my screenshot has the wrong dimensions — what size does it want?
One of the exact sizes for that display class: 1290×2796, 1260×2736 or 1320×2868 for iPhone 6.9-inch; 1284×2778 or 1242×2688 for iPhone 6.5-inch; 2064×2752 or 2048×2732 for iPad 13-inch. Portrait and landscape are both accepted — swap the two numbers for landscape.
What does "images can't include alpha channels or transparencies" mean?
The PNG carries a transparency channel, whether or not anything in the image is actually transparent. Flatten onto an opaque background and re-export, or export JPEG. Shipshot's exports are flattened with no alpha channel.
Why was my 1080×2400 Google Play screenshot rejected?
Because 2400 is more than twice 1080 and Google caps the longest side at twice the shortest. Re-export at 1080×2160 or 1080×1920.
Can I just resize the screenshot I already have?
You can, but re-exporting at the target size is better. Upscaling softens text baked into the image and rounding during the resize can leave the file a pixel out, which fails validation again.
Do I have to upload a screenshot for every iPhone size?
No. Supply the 6.9-inch set and Apple scales it down for the smaller classes. Add the 6.5-inch set only if text-heavy captions need to render at native resolution there.
Which file format should I upload?
PNG or JPEG for Apple; JPEG or 24-bit PNG for Google. Whichever you choose, the file must not carry an alpha channel.