Use Cases
There are two ways to get screenshots into App Store Connect: drag them in by hand, size by size and language by language, or automate the whole thing with fastlane. This guide covers both, and the free tool that exports fastlane-ready folders so the upload takes seconds instead of an afternoon.
%2FOlivia%20Rhye.webp&w=64&q=75){kind=small}
%2FPhoenix%20Baker.webp&w=64&q=75){kind=small}
%2FLana%20Steiner.webp&w=64&q=75){kind=small}
%2FDemi%20Wilkinson.webp&w=64&q=75){kind=small}
%2FDrew%20Cano.webp&w=64&q=75){kind=small}
Loved by 2,000+ creators
App Store Connect accepts screenshots two ways: the web uploader and the API. The uploader is fine for a first submission in one language. The moment you support several device sizes across several markets, the manual grind (open a size, drag files, switch language, repeat) turns into real time, and every file still has to be a pixel-exact accepted resolution. fastlane deliver and the App Store Connect API solve the upload; the images themselves still have to be correct first. Screenhance produces those images at every required size and, when you want it, in the exact folder layout fastlane expects.
Upload is the easy part once every image is an exact accepted size. These tools produce them.
Make every required iOS and Android size from one design.
Sizes, the framework that converts, and localization.
Localize one design into 80+ languages for per-locale folders.
Confirm every image is an exact accepted resolution.
Resolve the App Store Connect dimensions rejection.
iOS-specific screenshot sets and current device frames.
This is manageable for one language and one size. For a localized launch it is dozens of drag-and-drops, which is exactly why the next two options exist.
fastlane deliver uploads a whole screenshot set to App Store Connect in one command. It reads a folder of images where each subfolder is named for an App Store Connect locale code, such as en-US, de-DE, or zh-Hans, and infers the device from each image's resolution. Run it once and every size and language lands in the right place.
The catch is producing that folder. Screenhance exports it directly: turn on the fastlane folder option and your set comes out as one folder per locale code, at the exact accepted sizes, ready to drop into your screenshots directory. No renaming, no per-locale exports, no dimension roulette.
If you would rather script it, the App Store Connect API uploads screenshots in three steps: reserve the asset, upload the bytes, then commit with an MD5 checksum. You authenticate with an API key created under Users and Access, Integrations, App Store Connect API, with at least the App Manager role. That key is three parts: an issuer id, a key id, and a downloaded .p8 private key you sign a short-lived token with. Keep the .p8 out of source control.
One-click direct upload from Screenhance, where you paste that key once and push your set straight into a version, is on the way. Until then, the fastlane-ready export above gets you the same result with a single deliver command.
Create professional mockups in three simple steps. No design skills required.
Drag and drop or select any screenshot, design, or image from your device.
Pick from iPhone, iPad, MacBook, browser frames and beautiful gradient backgrounds.
Download as PNG, WebP, JPEG, GIF, or video. Ready for marketing in seconds.
In App Store Connect, open your app, choose the version you are preparing, scroll to the Previews and Screenshots section, pick a device size, and drag the images in. Repeat for every device size and every language. Each image must match an exact accepted resolution or the upload is rejected. Teams that ship often automate this step with fastlane deliver or the App Store Connect API instead.
Yes. The App Store Connect API reserves an asset, uploads the bytes, and commits it with a checksum, and fastlane deliver wraps that flow for you. Both need an App Store Connect API key (issuer id, key id, and a .p8 private key) with at least the App Manager role. The screenshots still have to be the exact accepted sizes before you upload them.
One folder per App Store Connect locale code, such as en-US, de-DE, or zh-Hans, with the screenshots inside. fastlane deliver infers the device from each image's resolution. Screenhance can export in exactly this layout, so a multi-language set drops into your screenshots directory without any renaming.
Apple allows up to 10 screenshots per device size, per language. The first two or three carry almost all of the conversion weight because they are visible before anyone scrolls, so lead with your strongest benefit slides and use the rest for depth and social proof.
Almost always wrong dimensions. App Store Connect validates against an exact allow-list and rejects anything even one pixel off, along with images that show features not in the build or that bake in pricing and promo text. Export at an exact accepted size and keep the screenshots truthful to the live app.
Explore more ways to create stunning visuals with Screenhance.
Showcase apps in iPad Pro and Air frames
Try it freeCreate iOS and Android store visuals
Try it freeAndroid-ready Google Play visuals
Try it freeLatest iPhone 16 and 16 Pro frames
Try it freeShowcase websites in MacBook frames
Try it freeSeries 11 frames for watchOS apps
Try it freeDesign once, export every required size, localized and framed, in plain folders or fastlane-ready ones. Then upload in seconds.
