Upload App Store Screenshots for Every Language at Once

Why App Store Connect makes localized screenshots slow

The slowness is a multiplication problem. Screenshots are required per localization and per device display size: iPhone 6.9-inch and 6.5-inch, iPad 13-inch, and Mac, each as its own set. Multiply device sizes by localizations and a modest app localized to 15 languages can face dozens of separate upload slots, each populated by hand in a separate locale page. App Store Connect's web Media Manager uploads into one localization at a time, so the honest per-locale workflow is: pick a language, pick a device size, drag in up to 10 images, repeat. There is no 'apply to all languages' button for a localized set. That per-slot manual grind is why teams either skip localizing screenshots entirely or reach for the API.

• Screenshots are required per device size AND per localization
• Up to 10 screenshots per device size per locale
• The web Media Manager uploads into one localization at a time

Apple's screenshot inheritance rules — upload less, cover more

Inheritance is the single biggest time-saver Apple gives you. Any localization that has no screenshots of its own inherits the screenshots from your app's default localization. So if your imagery has no on-screen text — or text you are comfortable showing worldwide — you can upload one set to the default locale and every other language displays it automatically, with zero per-locale work. The moment you upload even one screenshot to a specific locale, that locale stops inheriting and you own its full set. The practical rule: localize screenshots only for the markets where translated on-image text meaningfully lifts conversion, and let everything else inherit. This turns a 15-locale job into one default set plus three or four genuinely localized sets.

• Locales with no screenshots inherit from the default localization
• Uploading one screenshot to a locale breaks inheritance for that locale
• Localize images only where translated on-screen text moves conversion

Media Manager and the API: what bulk options Apple gives you

The App Store Connect web interface gives you the Media Manager — drag-and-drop into a single localization's device set, with automatic size validation. It is fine for one locale and painful for twenty. The App Store Connect API is the real bulk lever: it exposes app screenshot sets and screenshot resources you can create, upload, and reorder programmatically, across every locale and device size, in one automated pass. This is what fastlane's deliver and native Mac tools build on. Note the constraints the API still enforces: exact pixel dimensions per device size, a maximum of 10 screenshots per set, and the same inheritance behavior. The API removes the clicking, not the rules — you still supply correctly sized images for each device.

Organizing localized screenshot sets so uploads stay sane

Before you touch upload, get your files organized by device size and locale, because a disorganized folder is where wrong-size and wrong-locale mistakes happen. A reliable structure is a folder per locale, and inside it a subfolder or clear naming per device size, with a consistent order prefix (01_, 02_) so the sequence is deterministic. Keep the exact required pixel dimensions handy — Apple rejects anything off by a pixel — and generate each device size from the same source frames so your five iPhone shots and five iPad shots tell the same story. Auto-categorizing images by device group as you add them (rather than sorting after) prevents the classic error of an iPad image landing in an iPhone slot, which App Store Connect will reject on upload.

• One folder per locale, subfoldered or named by device size
• Prefix filenames (01_, 02_) so screenshot order is deterministic
• Match Apple's exact pixel dimensions per device size or uploads are rejected

Downloading your existing screenshots back out

A step teams forget: to update or re-localize screenshots, you often need the current ones first, and App Store Connect's web UI has no clean bulk download. The API can read your existing screenshot sets so you can pull down what is live, edit or re-caption it, and push it back — useful when you are adding a new locale that should mirror an existing one, or auditing which locales still show last year's images. Being able to download the current state also makes inheritance visible: you can see exactly which locales have their own set and which are inheriting from the default, so you localize the right ones instead of guessing.

FAQ