How do you capture clean iOS Simulator screenshots?

Key points

• Match the device to the display class: iPhone 17 Pro Max and iPhone 16 Pro Max capture natively at 1320 × 2868, and iPhone Air at 1260 × 2736² (source 2)³ (source 3) — both are accepted 6.9-inch App Store sizes, so nothing needs resampling before upload.
• xcrun simctl status_bar <device> override sets a fixed time, battery level and signal state in one call — flags include --time, --batteryLevel, --batteryState, --cellularBars and --wifiBars⁶ (source 6).
• A resized Simulator window is a display convenience, not a resample. simctl io screenshot reads the device’s rendering directly, so a window shrunk to fit your monitor still produces a full-resolution file.
• Status bar overrides are undocumented outside --help output and have had version-dependent glitches on past Xcode releases, by report on Apple’s own developer forums⁷ (source 7). Verify one screenshot from a fresh capture run before batching the rest.
• The simulator is not the device: it has no real camera, no access to your photo library, and does not run every GPU path a physical phone does. Camera previews, AR and some Metal-heavy screens still need a hardware capture.

Choosing the right simulator

Pick a simulator whose native pixel size already lands on an accepted App Store size¹ (source 1) — see the accepted size table for the full list. Get this right and every raw capture is upload-ready at full resolution; get it wrong and you are resizing images before you have even opened a design tool.

Confirm what is actually installed before you plan a shoot — device availability depends on which Simulator runtimes your Xcode has downloaded:

• xcrun simctl list devices available — every booted or bootable device, grouped by iOS runtime.
• xcrun simctl list devicetypes — every device model Xcode knows how to create, including ones with no runtime installed yet.

Cleaning the status bar before you capture

A raw simulator screenshot carries whatever the clock read when you tapped, plus a battery level and signal state that changes between runs. A marketing set built from ten screenshots with ten different times and battery levels looks assembled, not designed. Fix all three before you capture anything.

There is no public Apple web page for simctl status_bar; the flags below come straight from xcrun simctl status_bar booted override --help on a current Xcode install. A worked example using the same flags is documented independently by developer Jesse Squires⁶ (source 6).

1. xcrun simctl status_bar booted override --time "9:41" --batteryState charged --batteryLevel 100 --cellularMode active --cellularBars 4 --wifiMode active --wifiBars 3
2. Capture as many screenshots as you need — the override holds until you clear it or shut the device down.
3. xcrun simctl status_bar booted list to confirm the override is actually active, if a screenshot still looks wrong.
4. xcrun simctl status_bar booted clear when you are done, so your own day-to-day testing on that simulator is not stuck on a 9:41 clock and a full battery.

Capturing at native resolution

Dragging the Simulator window smaller does not shrink what a screenshot captures. xcrun simctl io booted screenshot reads the booted device’s own framebuffer and writes it out at full size — it has no concept of the host window’s zoom level, because the window is just a viewer onto that framebuffer, not the source of it.

1. xcrun simctl bootstatus "iPhone 17 Pro Max" -b — boots the device if needed and blocks until it has finished booting.
2. xcrun simctl launch booted com.example.yourapp — launch your app, then navigate to the screen you want.
3. xcrun simctl status_bar booted override --time "9:41" --batteryState charged --batteryLevel 100 --cellularMode active --cellularBars 4 --wifiMode active --wifiBars 3
4. xcrun simctl io booted screenshot 01-onboarding.png
5. xcrun simctl status_bar booted clear before you shut down or move to the next screen, unless you are about to capture another shot that wants the same override.
6. xcrun simctl shutdown booted once a device is done, so a stray booted simulator does not answer to booted on your next run.

Dark mode, light mode and locale variants

If you ship more than one appearance or language, capture every variant from the same script rather than by hand — it is the only way the set stays consistent when a screen changes six months later.

• Appearance: xcrun simctl ui booted appearance dark or xcrun simctl ui booted appearance light switches the whole device immediately — no reboot, no relaunch required.
• Locale: relaunch with -AppleLanguages and -AppleLocale as launch arguments, e.g. xcrun simctl launch booted com.example.yourapp -AppleLanguages "(de)" -AppleLocale "de_DE". Apple documents these two flags as the standard way to force a language and region without changing the simulator’s system settings⁵ (source 5).

Name files so the variant is legible from the filename alone, before you have opened a single one: device, appearance, locale, then an ordered screen number and a short slug — iphone17promax-dark-de-01-onboarding.png. A batch script that loops devices × appearances × locales and writes files in that pattern is worth the half hour it takes to write the first time.

What the simulator can’t show you

The Simulator is a device model running on your Mac’s hardware, not an emulated iPhone. Two consequences matter for a screenshot set: there is no camera, so any screen behind a live camera preview shows either a black frame or a static placeholder image instead of what a customer sees; and rendering runs through your Mac’s GPU rather than the phone’s, so a small number of Metal-heavy effects and some AR content do not look the same as they do on hardware.

For those screens, capture from a real device instead — the device’s own screenshot gesture (side button and volume up, on current hardware) — and drop the resulting file into the same batch alongside your simulator captures. Everything else in this guide still applies: same target resolution, same status bar convention, same naming pattern.

Once the raw set is clean and at the right resolution, the next step is turning it into an actual marketing set — see building the marketing set. Shotluma is a free, MIT-licensed, browser-based tool built for exactly that handoff — it takes raw captures like these and turns them into an editable, store-ready set, exporting at 1290 × 2796 and 1242 × 2688.

Frequently asked questions

Sources

1. 1Screenshot specifications — App Store Connect Help — Apple Developer, iPhone 6.9-inch display class, accepted portrait sizes. Read 22 August 2026.
2. 2iPhone 17 Pro Max - Tech Specs — Apple Support, Display section, resolution figure. Read 22 August 2026.
3. 3iPhone Air - Tech Specs — Apple Support, Display section, resolution figure. Read 22 August 2026.
4. 4iPhone 15 Pro Max - Tech Specs — Apple Support, Display section, resolution figure. Read 22 August 2026.
5. 5Testing Your Internationalized App — Apple Developer, -AppleLanguages and -AppleLocale launch argument syntax. Read 22 August 2026.
6. 6Overriding status bar display settings in the iOS simulator — Jesse Squires, Worked `simctl status_bar override` example command. Read 22 August 2026.
7. 7Simulator not reflecting simctl override --time command as expected — Apple Developer Forums, Thread replies describing version-dependent regressions. Read 22 August 2026.