How to Capture Mobile Responsive Screenshots with an iPhone Simulator and Xcode

To capture a screenshot of a running app, run it on an iPhone simulator from Xcode, navigate to the screen and state you want, then click the Screenshot button below the device in Device Hub. Xcode saves the image to your Mac’s Desktop at the simulated device’s full resolution, regardless of the Mac display resolution. To check responsive behavior, resize the simulated iPhone or change settings such as appearance and text size, then capture each meaningful state. Apple’s Device Hub screenshot instructions cover the capture step and save location.

1. Run your app in an iPhone simulator

Open your project in Xcode.
In the toolbar, choose a build scheme that includes your app target.
Choose an iPhone simulator as the run destination. If the simulator you need is not available, use Xcode’s device management to add or install a compatible simulator runtime.
Click Run. Xcode builds and launches the app in Device Hub.
Navigate the running app to the screen you want to document. Recreate the relevant state too: for example, open a menu, load representative content, or show a validation message.
Click the Screenshot button below the simulated device. Find the captured image on your Mac’s Desktop.

The capture represents the app running in the simulator. The size of the Xcode window or the simulator’s on-screen zoom does not set the screenshot’s pixel resolution. Device Hub captures at the simulated device’s full resolution. Apple’s guide to running an app on a simulated or physical device describes selecting a run destination and launching the app.

2. Check responsive layouts in the simulator

A useful responsive review compares meaningfully different conditions rather than collecting several nearly identical images. Start with a compact and a larger screen configuration, then add the states that matter to your interface: orientation, dark appearance, enlarged text, or a relevant language.

Resize the simulated iPhone

Run your app in Device Hub.
Click Enter resize mode in the canvas toolbar.
Drag a handle at the top, bottom, or sides of the simulator, or enter screen dimensions using the controls below it.
Inspect how the app responds. Device Hub snaps the entered or dragged dimensions to the nearest valid size.
When you have a useful configuration, capture it with the Screenshot button. Exit resize mode when finished.

Resizing is a quick way to expose constraints, wrapping, and layout transitions without launching a separate simulator for every size. It does not mean every arbitrary dimension corresponds to a physical iPhone model. For details, see Apple’s simulator environment and screen resizing documentation.

Change appearance, text size, and orientation

Device Hub’s settings inspector can change simulated environment settings, including appearance and text size. Set a configuration, run or return to the app, inspect the screen, and take a separate capture if the state is important to your review. Use the same app content and navigation state when comparing images so that the environment change is the main difference.

For a repeatable comparison, record the conditions alongside each screenshot—for example, “compact portrait, light appearance” and “larger landscape, dark appearance, extra-large text.” The exact set depends on the interface; Apple documents the available environment settings, but does not prescribe a universal screenshot matrix.

3. Choose between a running-app screenshot and a preview

Capture path	Use it for	Important distinction
Device Hub screenshot	A screen from the app running in the simulator, including the app’s current navigation and runtime state.	Run the app, navigate to the desired state, and capture from Device Hub.
Xcode preview screenshot	Inspecting a configured view or comparing preview variants during development.	Capture the preview from the canvas; it is not a screenshot of the full running app session.

To capture a preview, select a source file that contains a preview, show the canvas, and choose the preview device or settings you need. Xcode previews support variant inspection such as light and dark appearance, orientation, and Dynamic Type. Click the canvas Screenshot button, choose a filename and location in the save sheet, then save. Apple explains preview interaction and capture in its Xcode preview documentation.

Use a preview when you want to inspect a view quickly across configured variants. Use Device Hub when the evidence needs to show the state of the running app. A preview can help find a layout issue, but it does not replace capturing the app state that reproduces the issue.

4. Make the screenshots useful evidence

Capture the relevant state. Include the content, navigation, and interaction state involved in the design review or bug report.
Vary one condition at a time when comparing. Keep the same app state while changing size, orientation, appearance, or text size where possible.
Include accessibility cases that affect layout. If the interface relies on text fitting, include a larger text size; if it adapts to appearance, compare light and dark.
Keep the original capture. If you crop or annotate a copy for a report, retain the original screenshot so reviewers can distinguish the source capture from later edits.
Check the artifact before sharing. Confirm that it shows the intended screen and state, and that sensitive or account-specific information is not visible.

Device Hub’s full-resolution capture is useful for development and review. Do not assume that a simulator screenshot automatically matches current App Store Connect image requirements: consult Apple’s current Screenshot Specifications for the target device and submission.

5. What simulator screenshots can and cannot show

A simulator lets you run and inspect an interface under simulated device configurations without having every physical device on hand. Its screenshot records that simulated app state and resolution. It does not establish how the app performs on physical hardware, and some hardware-specific features may be unavailable in the simulator. Validate performance-sensitive behavior and hardware-dependent features on real devices. Apple discusses these limits in its Simulator testing guidance and recommends device profiling for higher-fidelity performance measurements in its performance documentation.

6. Troubleshooting

Symptom	Likely cause	What to do
The app does not launch in the simulator.	The selected scheme, run destination, build, or simulator runtime is not suitable for the app.	Choose the app’s scheme and a compatible iPhone simulator, then build and run again. Read the build or launch error in Xcode before changing project settings.
The screenshot is not in the folder you expected.	Device Hub saves its screenshot to the Mac Desktop by default.	Check the Desktop. For preview screenshots, use the save location you selected in the preview save sheet.
The captured image appears smaller or larger than the simulator window.	The window’s display scale and the simulated device’s capture resolution are different.	Check the image dimensions and remember that Device Hub captures at the simulated device’s full resolution, independent of the Mac display resolution.
The resized screen does not match the exact dimensions entered.	Device Hub snaps the simulated screen to the nearest valid size.	Use the resulting size as the actual test condition, and note it when comparing captures.
A preview screenshot does not show the screen reached in the running app.	The canvas captured a configured view preview, not the Device Hub app session.	Run the app in the simulator, navigate to the state, and capture in Device Hub.
Simulator behavior or speed differs from an iPhone.	The simulator does not reproduce all physical hardware behavior or performance.	Verify the hardware-specific behavior and performance-sensitive result on physical devices.
A screenshot is the wrong size for a store listing.	Simulator resolution alone does not guarantee compliance with current submission specifications.	Check Apple’s current Screenshot Specifications for the destination and required device sizes before submitting.

7. When this workflow is not the right capture tool

Xcode and the iPhone simulator are suited to capturing an iOS app running in a simulated device. They do not capture a website as rendered in a desktop or mobile browser. If the subject is a web page, use a browser-based capture workflow or a screenshot API instead. If you need screenshots from an iPhone app, stay with Device Hub so the capture shows the app’s actual simulated runtime state.

Or skip the browser setup

For website screenshots, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF; this example requests a WebP screenshot of a web page. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. These are website captures, not screenshots of an iPhone simulator app.

FAQ

How do I take a screenshot in iPhone Simulator?

Run the app, navigate to the desired screen in Device Hub, and click the Screenshot button below the simulated device. The image is saved to your Mac’s Desktop.

Does resizing the simulator window change screenshot resolution?

No. Device Hub captures at the simulated device’s full resolution regardless of your Mac display resolution or the simulator’s displayed size.

Can I test a responsive layout without launching several iPhone simulators?

Yes. Device Hub lets you resize a simulated iPhone screen to check how the interface adapts. The screen snaps to the nearest valid size.

Are Xcode preview screenshots equivalent to screenshots of a running app?

No. Previews are useful for inspecting configured views and variants. Capture from Device Hub when you need the running app’s current state.

Can an iPhone simulator screenshot prove how the app performs on a real iPhone?

No. Use physical devices to validate performance-sensitive behavior and hardware-specific features.