Shipshot guide
How to fix a screenshot size mismatch before upload
A size error at upload is usually one of a handful of causes, and you can identify which in about two minutes. The important thing is that Apple's display-size groups accept more than one pixel pair, so the fix is rarely to guess a new number — it is to find out which accepted pair your file was actually meant to be.
Read the exact pixel size of the rejected file
Start with the file, not the tool that made it. Open the rejected image and read its true width and height. Very often the file is a few pixels off in one dimension because it was cropped, resized to fit a layout, or exported at a scale factor the design tool applied silently. A near-miss is still a rejection.
- Read the actual pixel width and height from the file itself.
- Compare it against the accepted pairs for the display size you intended.
- Note whether the mismatch is a near-miss or an entirely different device class.
Check you targeted the right display group
Apple groups devices by display size and each group lists its own accepted dimensions. The 6.5-inch group accepts 1284×2778 or 1242×2688. The 6.3-inch group accepts 1179×2556 or 1206×2622. The 13-inch iPad group accepts 2064×2752 or 2048×2732 and is required when the app runs on iPad. Several groups list alternates, so confirm which pair you were aiming for on Apple's current specification page before changing anything.
- Identify which display group the upload slot belongs to.
- Look up that group's accepted pairs on Apple's current specification page.
- Pick one accepted pair and make the file match it exactly.
Rule out orientation, alpha, and format
Not every rejection labelled as a size problem is only about size. Landscape files use the reversed width and height of the portrait pair, so a rotated export can land outside the accepted set. Apple accepts .jpg, .jpeg, and .png and does not allow alpha channels, so a PNG exported with transparency from a design tool can fail even at correct dimensions.
- Confirm the orientation matches the pair you are targeting.
- Export without an alpha channel; flatten transparency before saving.
- Check the file extension and encoding are among the accepted formats.
Fix at the source rather than by resampling
Resizing a finished image to force it into an accepted pair distorts the layout and softens the text, and it usually produces a second problem that is harder to see than the first. Change the canvas in the project and re-export. If the underlying capture is smaller than the target, recapture at the larger device class instead of enlarging.
- Set the project canvas to the accepted pair and re-export cleanly.
- Recapture rather than upscale when the source screen is too small.
- Re-check the caption layout, because a changed canvas can move line breaks.
Review checklist
Questions to ask before handoff
Why did a file that looks right get rejected?
Usually it is a few pixels off, carries an alpha channel, or belongs to a different display group than the slot it was uploaded to. Read the file's real dimensions first.
Is there one correct size per iPhone?
No. Apple groups devices by display size and several groups list more than one accepted pair. Check the group, then match one pair exactly.
Can I just resize the image to fit?
Avoid it. Resampling a finished frame distorts the layout and softens text. Change the canvas in the project and export again.
Does a transparent background cause a size error?
It causes a rejection at upload because alpha channels are not allowed, which is easy to mistake for a dimension problem. Flatten before exporting.
