The latest articles on DEV Community by Clican (@_a262dc67fe8e7bf5c7a897). https://dev.to/_a262dc67fe8e7bf5c7a897 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4179060%2F615fa4c1-b85a-4570-b83b-10713209ea5d.png https://dev.to/_a262dc67fe8e7bf5c7a897 en Clican Mon, 12 Oct 2026 10:28:18 +0000 https://dev.to/_a262dc67fe8e7bf5c7a897/app-store-screenshot-sizes-what-you-actually-have-to-upload-k10 https://dev.to/_a262dc67fe8e7bf5c7a897/app-store-screenshot-sizes-what-you-actually-have-to-upload-k10 <p>App Store Connect doesn't scale your screenshots and doesn't check proportions.<br> It matches your file against a list of allowed pixel sizes - if the width or<br> height is off by a few pixels, the upload is simply flagged invalid. A wrong<br> size usually means a blocked release and a fresh wait in the review queue.</p> <p>Here's the size list as it actually stands, plus the three mistakes that cause<br> most rejections.</p> <h2> The sizes you have to provide </h2> <p><strong>iPhone</strong> - you need at least one set for the large Dynamic Island display:</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Native size</th> <th>Also accepted</th> <th>Notes</th> </tr> </thead> <tbody> <tr> <td>1320 x 2868 (portrait)</td> <td>1290 x 2796, 1260 x 2736</td> <td>6.9" class - this is the required set</td> </tr> </tbody> </table></div> <p>The 6.7" class no longer exists on its own; older 1290 x 2796 shots fall into<br> this slot. The 6.5" size (1284 x 2778 or 1242 x 2688) is required <em>only</em> if you<br> don't supply the 6.9" set.</p> <p><strong>iPad</strong> - if your app supports iPadOS, a 13" set is required:</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Native size</th> <th>Also accepted</th> </tr> </thead> <tbody> <tr> <td>2064 x 2752</td> <td>2048 x 2732 (12.9")</td> </tr> </tbody> </table></div> <p>If the UI is identical across sizes and locales, upload only the<br> highest-resolution set - App Store Connect downscales it for smaller devices<br> automatically.</p> <h2> The 3 most common mistakes </h2> <ol> <li> <strong>Dimensions a few pixels off.</strong> Almost always the wrong device canvas, or manual cropping in a graphics tool.</li> <li> <strong>A leftover alpha channel.</strong> PNGs exported from Figma, Sketch or a canvas can keep transparency data even when every pixel is opaque, and App Store Connect rejects them outright. Export as JPEG, or flatten onto a solid background.</li> <li> <strong>Missing screenshots for some locales.</strong> Every region you publish should carry screenshots in its language.</li> </ol> <p>Two smaller traps worth knowing: a status bar showing a real carrier, full<br> signal or a nearly-empty battery looks unprofessional; and screenshots that show<br> features not actually in the build will draw questions at review.</p> <h2> Exporting every size in one pass </h2> <p>Placing and exporting each size by hand is slow and error-prone. A screenshot<br> studio ships with device canvases and official colored frames, so you drop in a<br> UI capture and it snaps to the exact pixels.</p> <p>Store Connect Management (my app, macOS) exports at the official sizes and<br> includes a magnifier for pixel-level checks. Screenshots and multilingual copy<br> live in the same workspace, then sync in one click via your own App Store<br> Connect API key.</p> <p>Full walkthrough: <a href="https://anaxkg.com/en/store-connect-management/app-store-screenshot-sizes/" rel="noopener noreferrer">https://anaxkg.com/en/store-connect-management/app-store-screenshot-sizes/</a></p> ios storeconnect appstore indiedev