Upload through App Store Connect's web interface, or organize a repeatable fastlane workflow for a larger set. This guide covers both routes and the checks to make before either one.
Loved by 3,000+ creators
App Store Connect accepts screenshots two ways: the web uploader and the API. The web uploader is direct and visible. A fastlane workflow can reduce repetitive uploads across several supported device slots and localizations. Neither route fixes the source files: prepare the selected Apple size presets, inspect each layout, and verify the final files against the current slot before uploading.
Choose the tool for the job: build the set, review the current size list, check an existing file, or fix a dimension mismatch.
Build an editable set and export the selected device presets.
Current size references, layout guidance, and localization review.
Localize one design into 16 locales 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.
The manual route is often enough for a small release. A repeatable upload workflow becomes useful when you maintain several supported device slots and localizations. Before submission, check Apple's current upload instructions.
fastlane deliver can deliver a screenshot directory to App Store Connect. Its metadata structure groups images in locale folders such as en-US, de-DE, or zh-Hans and uses the file dimensions to map screenshot types. Review fastlane's current setup and command options before using it in a release pipeline.
Screenhance can organize selected device-size and locale exports into that folder structure. Review every generated file, then place the resulting folders in the fastlane screenshots directory used by your project.
For the Screenhance export controls and the checks to make after transfer, follow the step-by-step App Store Connect upload guide. It covers the standard ZIP, Fastlane folders, and direct upload when your export panel offers it.
If you need direct automation, use Apple's current App Store Connect API documentation. Screenshot asset upload, authentication, permissions, and version relationships are implementation details that should be read from Apple at the time you build the integration. Keep private keys out of source control and use the narrowest role your workflow supports. Start with Apple's App Store Connect API documentation.
Screenhance prepares organized screenshot files and optional locale folders for App Store Connect or fastlane. Use direct upload when it is available for your iOS configuration, or publish through Apple's workflow with the organized ZIP.
In App Store Connect, open the app version you are preparing, find Previews and Screenshots, choose one of the device slots shown for that build, and add the images in order. Repeat for the supported device slots and localizations you intend to publish. Check Apple's current upload guidance before submission.
Yes. Apple provides App Store Connect API endpoints for screenshot assets, and fastlane deliver can automate screenshot delivery. Authentication, roles, and API behavior can change, so use Apple's and fastlane's current documentation rather than copying credentials or commands from an old guide.
fastlane's metadata structure uses a screenshots directory with locale folders such as en-US, de-DE, or zh-Hans. Screenhance can organize selected size and locale exports into that layout. Check fastlane's current deliver documentation before running an upload.
Apple currently allows from one to ten screenshots per supported device size and localization. Use only the images needed to explain the product clearly, place the most important message early, and review the final order in App Store Connect.
Read the error shown in App Store Connect first. For a dimension error, compare the failed file with Apple's current accepted pixel pairs for that device slot and re-export it exactly. Also keep the images truthful to the submitted product and review Apple's current submission rules.
Continue preparing the same App Store, Google Play, or Chrome listing.
Create iOS and Android store visuals
Start creatingAndroid-ready Google Play visuals
Start creatingiOS-specific screenshot sets
Start creatingValidate screenshots before App Store Connect rejects them
Start creatingCheck screenshots against Google Play's accepted range
Start creatingResolve the App Store Connect wrong-dimensions error
Start creatingBuild the set, choose the device slots and locales needed for the release, inspect the files, then upload through App Store Connect or your own fastlane workflow.
%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}