Start with the device families you actually need
Apple accepts screenshots for different iPhone and iPad display families. Most teams should begin with the largest current iPhone size they support, then prepare smaller iPhone and iPad variants only when the app experience genuinely benefits from separate framing. A smaller checklist beats a perfect-looking set that never ships.
Plan the first three screenshots as a sequence
The first screenshot should state the core promise. The second should prove the main workflow. The third should answer a practical question: speed, privacy, compatibility, reporting, sharing, or another reason a visitor would hesitate. Later screenshots can cover secondary features.
Use captions that survive cropping
Keep the main caption short enough to read at thumbnail size. Put the important noun early: "Track every workout" reads faster than "The easiest way to track every workout." In Frame Launch, test captions with the side previews and export a small draft before committing to the whole set.
Export order checklist
- Choose the output device size before detailed text tuning.
- Create the first screenshot style, then transfer style to the rest of the set.
- Review line breaks in every language you plan to publish.
- Export one PNG first, inspect it, then export the full ZIP.
Good screenshots do not show every feature. They make the next tap feel obvious.
Next step
Open Frame Launch, choose an App Store output size, and create a rough five-screen sequence before polishing colors or 3D device angles.