Apple Watch, Apple TV & Vision Pro App Store Screenshot Sizes (2026)

Beyond iPhone and iPad

Most screenshot guides stop at iPhone and iPad. If your app also ships a watchOS, tvOS, or visionOS experience, App Store Connect asks for platform-specific screenshots—and each platform has its own sizes and design constraints.

All sizes below come from Apple's screenshot specifications. The general rules apply everywhere: up to 10 screenshots per platform, .jpeg/.jpg/.png, and no alpha channels or transparency. Apple updates this page when new hardware ships, so double-check it before each major release.

For iPhone, iPad, and Mac, see our App Store screenshot sizes guide and Mac App Store screenshot sizes.

Apple Watch screenshot sizes

Screenshots are required for Apple Watch apps. Upload one of the following sizes:

One important rule: you must use the same Apple Watch screenshot size consistently across all localizations of your app. Pick one size and stick to it for every language.

Which watch size to choose

Choosing a recent, larger size (such as the Ultra or newest Series size) usually gives you the most pixels to work with. Whatever you choose, capture all screenshots on the same simulator or device so the set is consistent.

Designing watch screenshots

Watch screenshots are tiny. On the product page they appear in a separate Apple Watch section, and every pixel counts.

• Show one glanceable thing per screenshot. A ring, a timer, a single number, a short list. That's what people use a watch for.
• Prioritize complications and Smart Stack widgets if they're central to your app; many users experience watch apps mainly through them.
• Use the watch's own dark aesthetic. watchOS interfaces are designed on black; screenshots with bright full-bleed backgrounds can look off-platform.
• Keep sample data realistic and short. Long names truncate; use short, believable values.
• Don't try to fit marketing captions into the image. At 400-something pixels wide, text overlays become unreadable. Let your iPhone screenshots and description carry the narrative.

Capture straight from the watchOS Simulator in Xcode for pixel-exact output, then verify dimensions with our screenshot checker.

Apple TV screenshot sizes

Screenshots are required for Apple TV apps. Accepted sizes:

Use 3840 × 2160 if you can produce it cleanly; 1920 × 1080 is fine for UI-heavy apps rendered at 1080p.

Designing for the 10-foot experience

tvOS screenshots should look like what people see from the couch:

• Show focus states. The focused item, with its lift and parallax effect, is how people navigate tvOS. A screenshot with a clearly focused tile reads as "real tvOS."
• Feature content, not chrome. For media apps, big artwork and rows of content sell the experience. Make sure you have rights to any artwork shown.
• Keep it simple. tvOS interfaces are sparse by design; screenshots crowded with text look unlike the platform.
• Mind the safe area. TV interfaces keep important content away from the edges, and your screenshots should reflect that.
• Avoid baked-in captions. If you add any text, keep it large and minimal—though many top tvOS listings use pure in-app captures.

For games on Apple TV, show actual gameplay with the controller-driven UI, not just a title screen. Guideline 2.3.3 applies here too: screenshots must show the app in use.

Apple Vision Pro screenshot sizes

Screenshots are required for Apple Vision Pro apps. Accepted size:

Designing visionOS screenshots

Spatial apps are hard to communicate in a flat image. A few practices help:

• Capture from the device or simulator so windows, volumes, and materials render as they actually appear—glass, depth, and shadows included.
• Show the app in context. A window floating in a believable room or environment communicates "spatial" better than a flat window on a plain background.
• Make interactions understandable. Where appropriate, show a moment that implies interaction, such as an object being manipulated, while keeping it honest to the real experience.
• Use the full 16:9 frame thoughtfully. Don't leave a small window floating in a big, empty capture; compose so the app is the clear subject.
• Pair with an app preview. Spatial experiences often benefit from video; see app preview video vs screenshots.

Workflow tips for multi-platform apps

1. Plan the story once, adapt per platform. Use the same feature order and vocabulary across iPhone, iPad, Mac, Watch, TV, and Vision Pro—tailored to each device.
2. Capture from simulators for exact sizes. Simulators output the correct pixel dimensions for each device; real-device captures are better for visionOS realism.
3. Batch-check everything. Before upload, confirm sizes and that every file is opaque. Our screenshot checker catches size mismatches, and the PNG converter helps you flatten exports.
4. Keep sizes consistent within a platform. Mixed sizes inside one set look sloppy, and for Apple Watch they're explicitly required to be consistent across localizations.
5. Keep a source-of-truth spreadsheet. List each platform, the size you chose, the number of frames, and the localizations; it saves time on every release.

For iPhone and iPad marketing frames, you can still compose captions and device mockups in our screenshot editor—just keep Watch and TV captures closer to raw UI.

Quick reference

Bottom line

Watch, TV, and Vision Pro screenshots are required for their respective apps and each follows different design logic: glanceable and dark on the wrist, focus-driven and content-forward on TV, spatial and contextual in visionOS. Get the exact pixel sizes right, keep sizes consistent, and let each platform's screenshots look native to that platform.