How to Make an App Screenshot, From Clean Capture to Store-Ready Asset

"App screenshot" means two different jobs. First you capture the interface — a truthful image of a screen your app really shows. Then you build an asset — that screen inside a composition with a caption, at a size the store accepts. Most listing problems come from doing only the first job.

Job one: capture a screen worth using

From the iOS simulator. Run your app on the device class you need (for a current flagship set, that is a 6.9-inch or 6.5-inch iPhone). Press Cmd+S to save a raw screenshot at the display's native resolution. Use a demo account with realistic content — named contacts, dated events, actual photos — because lorem ipsum reads as unfinished. Turn off notifications and battery-charging overlays, and hide anything that ages the image, like yesterday's date in a header.

From a real iPhone or Android device. Take the screenshot normally, then crop the status bar and home indicator unless you want them. Real-device captures are the right call when the simulator cannot show a feature: camera previews, NFC flows, hardware keys.

From the Android emulator. Pick a phone and tablet AVD whose resolution you can export within Google Play's range rules, and disable the status-bar clock before capture so the set stays consistent.

One rule across all three: the screen must exist in the current build. Do not stage interfaces the app does not have.

Job two: turn the capture into an asset

A raw screenshot is not a listing image. Three additions make it work:

1. A caption that promises something. One line, sized to read at search-result scale. "Find a parking spot you'll actually remember" works; "GPS-enabled" does not. The first screenshot has one job — decide that job before you design around it.
2. A frame or background that holds the screen. A device frame is optional; a consistent background and margin are not. Keep text and the useful part of the interface away from the edges, since storefront previews crop and shrink.
3. The right canvas. Place your capture into an export size the store accepts, not a stretched copy of whatever you designed first. Apple wants exact dimensions per display class, PNG or JPEG with no alpha; Google Play validates within a range. The details are in App Store Screenshot Sizes.

Assemble before you export

Make five or six assets this way, then read them as a strip. Each image should add a new reason to keep looking. Fix repeats by choosing a different screen, not by rewording the same caption. Then export every file against the store's current rules and check dimensions one last time before upload — Apple's specifications for the App Store, Google Play's asset requirements for Android.

If you would rather not manage canvases per device, an app screenshot generator workflow does the sizing; the capture and the caption stay your job. You can also start from a template in the editor and drop your real screens in.