How to upload screenshots to App Store Connect

Instead of manually uploading PNG images in App Store Connect, ButterKit can upload your screenshots for you using the ASC API (similar to Fastlane, but without the manual setup). What used to take hours or even days (creating, exporting, uploading, and manually organizing in ASC) can be done in seconds with the ButterKit upload feature. Your credentials are stored securely in your Keychain and only used to connect directly with the App Store Connect API from your machine. It’s easy to get started.

What are all the ways to upload screenshots to App Store Connect?

There are four ways to get screenshots into App Store Connect. They all end up in the same place (the media manager on your app’s version page) and differ only in how much manual work is involved:

1. The App Store Connect website (manual). Open App Store Connect app, go to your app and version, and drag PNGs into each display-size slot. Fine for one device size in one language; it breaks down fast once you localize (10 screenshots × 3 device sizes × 30 languages is 900 hand-uploads). App previews (videos) upload through the same interface.
2. fastlane deliver (the upload_to_app_store action). Free and scriptable, and a good fit if you already run fastlane in CI; but it needs a working Ruby environment, an API key config, and a specific screenshots folder convention.
3. The App Store Connect API. Apple’s REST API gives you full control (create a screenshot set, reserve an upload, send the file, commit), at the cost of the most code to write and maintain.
4. ButterKit (one click). ButterKit exports every artboard at the exact pixel dimensions each slot requires and uploads them into the right display-size slots and localizations via the ASC API; no Ruby, no scripts. Set up in minutes below.

How do I set up App Store Connect credentials?

Login to App Store Connect

1. Go to App Store Connect and log in with your Apple Developer account.
2. Navigate to Users & Access > Integrations > App Store Connect API

Create a Team Key

1. Click the + button to create a new key.
2. Enter a name for the key (e.g. “ButterKit App”) and select the App Manager role. App Manager role is required for ButterKit to have proper permissions to manage your screenshots and localizations.
3. Download the .p8 file and save it securely (you won’t be able to download it again).
4. Note down the Issuer ID and Key ID displayed on the page.

Configure ButterKit

1. Open ButterKit > Settings > Upload tab
2. Enter your Issuer ID, Key ID, and select your .p8 file
3. Save credentials
4. Press the “Test Connection” button to ensure it works

How do I upload screenshots from ButterKit?

Once your credentials are saved, uploading is a single export:

Voila! It’s that easy.

ButterKit does the heavy lifting for you, capturing directly from Xcode Simulator, framing it into a realistic 3D device, translating, formatting, and uploading directly to App Store Connect. Share your screenshots and app launch on the ButterKit Discord or subreddit for feedback and support from fellow builders/designers/devs.

FAQ

If I leave a field empty (e.g. Promotional Text) and publish, will it overwrite the existing content in App Store Connect?

No. Uploads are deliberately non-destructive: ButterKit only sends the fields you’ve actually filled in. Any field you leave empty is skipped entirely, so whatever you already have in App Store Connect stays exactly as-is. You can safely publish a partial set of changes without worrying about wiping out existing metadata.

Can I use ButterKit instead of fastlane’s upload_to_app_store?

Yes. ButterKit’s upload is an alternative to fastlane’s upload_to_app_store (deliver) action: it talks to the same App Store Connect API, but runs natively on macOS with no Ruby environments, gem conflicts, or brittle CI scripts to maintain.

Why does App Store Connect say my screenshot dimensions are wrong?

Each display-size slot only accepts specific pixel dimensions, and a screenshot rendered for a different display class gets rejected. See Fix “The dimensions of one or more screenshots are wrong” for causes and fixes, or the full App Store screenshot size guide for every accepted dimension.