visionOS App Store Screenshots: Sizes and Requirements (2026)
visionOS is the only Apple platform whose App Store screenshot does not look like a phone or a tablet. There is no portrait device, no notch, no home indicator — a Vision Pro screenshot is a wide 4K frame of your app's windows floating in a spatial environment. That single difference trips up a lot of submission workflows, because the tooling people already use for iPhone and iPad assumes a portrait device frame and a fixed simulator resolution that happens to match the store. On visionOS, neither assumption holds.
This post covers the exact requirement, why the obvious capture method produces the wrong dimensions, how to get a correctly-sized frame, the window-vs-immersive nuance for spatial apps, and the honest gap where most screenshot tooling leaves you on your own.
The visionOS screenshot requirement
On Apple's App Store Connect screenshot specifications page, Apple Vision Pro has a single listed size:
- Apple Vision Pro screenshot size: 3840 × 2160 pixels.
- Aspect ratio: 16:9 (this is standard 4K / UHD).
- Orientation: landscape. There is no portrait option.
- Formats: PNG, JPG, or JPEG. WebP, HEIC and TIFF are not accepted.
- Quantity: 1 to 10 screenshots, plus up to 3 app previews — the same limits as every other platform.
Unlike iPhone and iPad, there is only one display size to support. Vision Pro has no "6.9-inch vs 6.5-inch" split, no separate iPad set. One size, 3840 × 2160, and it is required for any app that ships to visionOS. If you submit a visionOS build without a screenshot at this exact size, App Store Connect will reject the upload.
For how this slots in next to every other size Apple accepts, the full reference is on the App Store screenshot sizes guide, and the broader rules (formats, alpha, file limits) are on the App Store screenshot requirements page.
Why the simulator screenshot is the wrong size
Here is the part that surprises people. The reflexive way to grab a screenshot — run your app
in the visionOS simulator and press Cmd + S (or use the screenshot button) —
does not give you a 3840 × 2160 file. The standard visionOS simulator
screenshot comes out at roughly 2732 × 2048 pixels, a 4:3 aspect ratio.
That is neither the right resolution nor the right shape for the store.
So a simulator screenshot taken the obvious way will be rejected on dimensions. You have a few ways to fix that:
- Reality Composer Pro Developer Capture. This is the method Apple's own developer materials point to. The capture it produces records at the native 3840 × 2160, so the output already matches the store requirement with no resizing. If you have Xcode and Reality Composer Pro installed, this is the cleanest path.
- Upscale and crop the simulator screenshot. Take the 2732 × 2048 capture, scale it to 3840 wide (which lands around 2879 tall while keeping proportions), then crop the height down to exactly 2160. It works, but it is fiddly — you are stretching pixels and hand-cropping, and you have to repeat it for every screenshot.
- Capture from a real Vision Pro. Screenshots taken on-device can be brought up to the required frame, though you will still want to verify the final dimensions land exactly on 3840 × 2160.
The practical takeaway: do not assume the simulator hands you a store-ready file the way it roughly does on iPhone. On visionOS, capture and "correctly-sized asset" are two separate steps, and the gap between them is real. This is the same class of mistake that produces rejected uploads on other platforms too — we wrote about the most common version of it in when App Store Connect says your screenshot dimensions are wrong.
How to capture from the simulator or device
A workable end-to-end flow for a typical visionOS app:
- Run the app in the visionOS simulator from Xcode. Drive it to the state you want to show — the main window open, the relevant content visible, any immersive scene presented.
- Use Developer Capture in Reality Composer Pro if you have it, so the recording is natively 3840 × 2160. Pull a still frame from that capture.
- If you only have the plain simulator screenshot, upscale it to 3840 wide and crop the height to 2160. Confirm the final pixel dimensions before you upload — App Store Connect checks them exactly.
- Repeat for each app state you want in the carousel, up to ten screenshots.
One detail that matters: a visionOS App Store screenshot does not have to be a fully spatial, stereoscopic image. A flat 2D frame is accepted, as long as it is exactly 3840 × 2160 and shows the app running inside the visionOS environment. You are not uploading a 3D file — you are uploading a regular image that happens to depict a spatial app.
Spatial-app nuances: window captures vs immersive scenes
This is where visionOS asks you to make a judgement call that iPhone screenshots never do. A visionOS app can present its UI in two broad modes, and what the screenshot should show depends on which one defines the experience:
- Window-based apps. Many visionOS apps are essentially floating windows — a 2D interface presented in space, sometimes with depth and ornaments. For these, the screenshot is mostly about the window content and how it sits in the environment. The composition question is the same as on any platform: which screen, which state, what is the user looking at.
- Immersive apps. Apps that open a full or mixed immersive space fill the user's field of view with content. A single flat screenshot can only capture a slice of that — one viewpoint, one moment. You have to choose the frame that best represents an experience that is inherently 360-ish, which is genuinely harder than picking a phone screen.
There is also the background to think about. A visionOS capture includes the surrounding environment — the passthrough or virtual scene behind your windows — which becomes part of the screenshot whether you intend it or not. That environment is doing real work in how the screenshot reads, so it is worth being deliberate about what is behind your app when you capture, rather than letting whatever the simulator defaults to leak into your store listing.
None of this is captured for you automatically. Deciding what to show, which immersive viewpoint, and what environment sits behind it is a human composition decision — and it is the part that most affects whether the screenshot actually sells the app.
The honest gap: most tools ignore visionOS
Here is the part nobody advertises. The large ecosystem of App Store screenshot tools — the device-frame generators, the carousel builders, the "drop your screenshot in and we'll mock it up" services — is overwhelmingly built around iPhone and iPad. They have polished phone frames, tablet frames, sometimes a watch. Vision Pro support ranges from "an afterthought" to "doesn't exist".
Why? A few honest reasons. The visionOS install base is small relative to iPhone, so the commercial incentive is weak. The 3840 × 2160 landscape frame breaks the portrait-device template these tools are built on. And there is no clean "device frame" to wrap a Vision Pro screenshot in the way you wrap a phone screen in an iPhone bezel — the device is on your face, not in the frame. So most tools simply leave a hole where visionOS should be, and developers are left doing the capture, resizing, and composition by hand.
If you ship to visionOS, plan for that gap. Budget the capture work, expect to verify dimensions manually, and do not assume the tool you use for iPhone screenshots has a visionOS path. Many do not.
Where Mokbi fits (and where it does not)
Straight answer first: Mokbi does not capture your visionOS screenshots. It does not run the simulator, it does not record from a Vision Pro, and it cannot pull a frame out of an immersive space for you. The capture step — getting a 3840 × 2160 image of your app running in visionOS — is on you, via Developer Capture or the upscale-and-crop route described above. Anyone claiming a browser tool can magically capture a spatial app is overselling.
Where it does help is afterward, in composition and localization. Once you have a correctly sized visionOS frame, Mokbi is a browser editor for laying it out into a store carousel: adding captions, arranging multi-panel layouts, translating those captions in one click across Apple's full list of App Store languages, and exporting at the right dimensions. It is designing on top of a screenshot you already captured — not capturing it. Designing is free; export and publishing come with a subscription (Solo €29.99/mo or Studio €49.99/mo). For a landscape 4K visionOS frame specifically, the value is the caption and localization workflow, not a device frame — there is no bezel to wrap Vision Pro in.