Apple Watch Screenshots: Pick 1 of 6 Sizes, No Fallback

Apple Watch takes exactly one screenshot size per app, chosen from six accepted pairs that run from 312 x 390 up to 422 x 514 pixels [1]. Unlike iPhone and iPad, Apple documents no scaling fallback for the sizes you skip. The canvas you upload is the one every watch owner sees.

The decision table further down works out which of the six to pick from the models you actually support, including the aspect-ratio arithmetic that stops a Series 11 frame from being a clean scale of an Ultra one.

TL;DR:

• Watch screenshots are required, iOS ones might not be. Apple's spec marks the watch row "Required for Apple Watch apps" [1], while the submission docs note that "iOS screenshots are also required for apps with an iOS component, but not for watch-only apps" [2].
• Six sizes, one slot. Apple lists the watch dimensions as "One of the following" [1]. You are not uploading a set per model.
• The scaling fallback is not documented for watch. Every sub-primary iPhone and iPad size carries an explicit note that scaled screenshots from a larger class get used instead [1]. The Apple Watch row carries no such note.
• The canvas is locked across languages. "You must use the same screenshot size for Apple Watch consistently across all localizations for the app" [1].

Table of contents

• Do you actually need Apple Watch screenshots?
• Why does Apple Watch take only one screenshot size?
• Does Apple scale watch screenshots to other models?
• Which of the six sizes should you upload?
• Why isn't a Series 11 frame a clean scale of an Ultra one?
• What does the localization lock change?
• Pick the canvas once, then iterate on what fills it

Do you actually need Apple Watch screenshots?

If your app ships a watchOS app, yes. Apple's screenshot specification marks the Apple Watch row "Required for Apple Watch apps" [1], and the submission guidance is blunt about the assets: "Provide screenshots of Apple Watch and an app icon" [2]. There is no skip-it path for a watch app.

The part that catches people out runs the other way. A watch-only app still needs an App Store Connect record built around an iOS app: "To prepare watchOS apps for distribution on the App Store, add an iOS app to App Store Connect and then include additional information specific to your app" [2]. You create the iOS-shaped record either way.

What you do not need, if the app is watch-only, is a set of iPhone screenshots to go with it. Apple states it directly: "iOS screenshots are also required for apps with an iOS component, but not for watch-only apps" [2]. So the two cases split cleanly:

• Watch app with an iOS companion. Both sets. Watch screenshots plus the iPhone screenshots your iOS app would need anyway.
• Watch-only app. Watch screenshots alone, sitting inside an iOS app record.

Apple's own framing for the two shapes is that you can build "either as iOS apps with a watchOS app or as watchOS-only apps" [2]. Which one you are determines how much of the iPhone required-versus-optional size question applies to you at all.

Why does Apple Watch take only one screenshot size?

Because Apple's spec presents the watch dimensions as a choice rather than a ladder. The Apple Watch entry reads "Screenshot size: One of the following" and then lists six pixel pairs [1]. iPhone and iPad rows are structured as a primary size plus fallbacks. The watch row is structured as a menu.

Here is the full accepted list, straight from the specification [1]:

The count limit is the same as everywhere else on the store: "You can upload one to 10 screenshots" [1]. So the watch slot behaves like a normal gallery. It is only the sizing that works differently, and the full reference table of accepted sizes across every device class is worth keeping open next to App Store Connect while you upload.

Does Apple scale watch screenshots to other models?

Apple does not document that it does, and this is the detail most guides get wrong. Read the specification row by row and the pattern is unmistakable: every iPhone and iPad size below the primary one carries its own explicit fallback sentence, and the Apple Watch row carries none [1].

The iPhone 6.5-inch entry says "If screenshots with the accepted sizes aren't provided, scaled screenshots for 6.9" displays are used." The 6.3-inch entry points at 6.5-inch. The 6.1-inch entry points at 6.5-inch. The iPad 12.9-inch and 11-inch entries both point at 13-inch [1]. Apple wrote the fallback down eight separate times for iPhone and four times for iPad.

For Apple Watch it wrote a different note entirely, about localization consistency, and no fallback sentence at all [1].

That absence is worth taking seriously, because the third-party guidance is a mess. A sweep of the current crop of 2026 size guides turns up confident claims that Apple "will automatically scale" watch screenshots from the largest model, and at least one page that asserts both positions in the same breath: pick one size because "Apple scales for the rest," followed a few lines later by "there is no fallback: ship the right size for every model class you support." When the secondary sources contradict themselves inside a single article, the safe read is the primary one.

The practical stance: treat the canvas you choose as the canvas that ships. Design it so it holds up at the size you picked rather than assuming a resampling step you cannot find documented.

Which of the six sizes should you upload?

Pick the size matching the newest watch class in your supported range, then check that your minimum-supported model is not several generations below it. The six sizes are not evenly spaced, and the gap between the modern classes is small enough that one canvas serves most apps well.

Two constraints narrow this further. Guideline 2.3.3 applies to the watch gallery exactly as it does to the phone one: "Screenshots should show the app in use, and not merely the title art, login page, or splash screen" [3]. On a canvas roughly 400 pixels wide, that rules out most of what you would be tempted to do with the space.

And whatever you pick has to survive the store at thumbnail scale. Our own Apple Watch Ultra 2 and Ultra generator produces the 410 x 502 canvas, which is the right target if that pair is your top supported model. It is one of the six, not all of them, so check your model range against the table above before you commit.

Why isn't a Series 11 frame a clean scale of an Ultra one?

Because the aspect ratios differ. Divide height by width across the six and they do not land on a constant: Ultra 2 sits at 1.224, Ultra 3 at 1.218, Series 9 at 1.222, and Series 11 at 1.192 [1]. The newest non-Ultra class is the shortest of the modern set, proportionally speaking.

Work the arithmetic and the consequence shows up fast. Take a design composed for the Ultra 2 canvas at 410 x 502 and scale it to the Series 11 width of 416. The height comes out at 509 pixels. The Series 11 slot takes 496. You are 13 pixels over, about 2.6% of the frame, and something has to give.

Thirteen pixels sounds like nothing until you remember what it costs on a canvas this small. A caption band on a watch frame is maybe 60 to 80 pixels tall. Losing 13 is losing a fifth of it, which is the difference between a two-line headline and a clipped one.

The same arithmetic run the other way is reassuring. Scaling that 410 x 502 design up to the Ultra 3 width of 422 gives a height of 517 against the 514 required, so those two canvases are within 3 pixels of proportional. Ultra to Ultra transfers cleanly. Ultra to Series does not.

This is the same class of problem as the iPad 13-inch versus 12.9-inch decision, where two canvases that look interchangeable on a spec sheet behave differently once a layout is sitting on them.

What does the localization lock change?

It turns the canvas choice into a one-time, app-wide decision. Apple's note on the watch row is explicit: "You must use the same screenshot size for Apple Watch consistently across all localizations for the app" [1]. No other device family carries that constraint in the specification.

For a single-language listing this changes nothing. For a localized one it changes the order of operations. You cannot ship the German listing on one watch canvas and the Japanese listing on another, so the size gets locked before any translation work starts, and every locale inherits whatever headroom that canvas has.

That matters most where text expansion is worst. A German caption running 30% longer than its English source has to fit the same watch frame the English version used, on a canvas already tight enough that the phone-sized tricks are unavailable. Worth settling the canvas first if market prioritization is on your roadmap, because reversing it later means re-rendering every locale rather than just the new one.

Pick the canvas once, then iterate on what fills it

The mechanical part of an Apple Watch listing is a short list: confirm whether you owe iOS screenshots too, pick one canvas from the six, and hold it across every localization. Apple's own specification answers all three, and the complete size reference keeps the numbers in one place.

The part that takes longer is what goes on the canvas, because 400-odd pixels wide punishes anything that reads as decoration and Guideline 2.3.3 rules out the splash-screen shortcut [3]. That is a few rounds of looking at options rather than a spec to follow, and you can work through watch frames the same way you would a phone set, adjusting the crop and caption until the thing is legible at the size it will actually be seen.