Free App Store Screenshot Generator for iPhone and iPad
Turn raw simulator captures into an upload-ready App Store screenshot set. Add up to five screens, edit each value proposition, choose a template and device frame, then export exact iPhone or iPad PNG dimensions. Every image stays in your browser.
Choose the right App Store screenshot size
Most current iPhone listings should begin with Apple’s 6.9-inch screenshot category. If the app supports iPad, prepare a separate set using genuine iPad UI for the 13-inch category. A phone layout stretched into a tablet frame may fit the pixels, but it does not accurately represent the product.
App Asset Kit includes accepted dimensions and selects one practical high-resolution default per device. Landscape mode swaps the canvas dimensions while preserving the selected device category.
- iPhone 6.9-inch default: 1320 × 2868
- iPhone 6.5-inch options including 1284 × 2778
- iPad 13-inch default: 2064 × 2752
- Matching official landscape dimensions
| Device category | Pixel size | When to use it |
|---|---|---|
| iPhone 6.9″ | 1320 × 2868 | Primary current iPhone set |
| iPhone 6.5″ | 1284 × 2778 | Fallback category when 6.9″ is unavailable |
| iPad 13″ | 2064 × 2752 | Apps that support iPad |
Build a five-screenshot story instead of five feature cards
The first two images carry most of the communication work. Use the first to answer what outcome the app creates and the second to show how quickly or clearly it delivers that result. Later images can explain a distinctive workflow, a trust signal, and a supporting feature.
Keep one headline and one short supporting sentence per screen. Repeating a generic claim such as “easy to use” across all five panels wastes space; each panel should add a new reason to understand or trust the product.
- Screen 1: the main result or use case
- Screen 2: the core workflow or speed advantage
- Screen 3: the most differentiated feature
- Screen 4: privacy, compatibility, or a secondary capability
- Screen 5: a useful summary without a download call to action
Write captions that remain readable in search results
A store visitor often sees the screenshots as small thumbnails before opening the full product page. Short, concrete benefit statements work better than dense feature lists. Start with a verb or outcome, and let the visible interface prove the claim.
Use strong contrast between text and background, keep critical words away from canvas edges, and avoid covering status bars, controls, charts, or navigation that help someone understand the screen. Test the full five-image rail at a reduced browser width before export.
- Aim for one or two headline lines
- Prefer “Plan a week in minutes” over “Powerful planning”
- Avoid unverified awards, rankings, or user counts
- Keep the most important UI in the upper, easily scanned area
Device frame or frameless layout?
A recognizable iPhone or iPad frame gives immediate platform context and can make raw captures feel more polished. A frameless composition dedicates more pixels to the actual interface and is often better for information-dense apps. Neither approach is automatically more persuasive.
Choose the format that keeps the UI honest and legible. If the source ratio differs substantially from the selected device, the renderer must crop the image. Follow the aspect-ratio warning and recapture the correct simulator device when important controls would be lost.
Localize the screenshot set, not only the caption
Translated text changes length, line breaks, and emphasis. Recheck every panel instead of pasting translated copy into an unchanged font size. The interface shown inside the device should also match the language of the App Store localization whenever that version is available.
Keep an uncaptioned source set so future translations do not require reconstructing screenshots. Names, dates, currencies, and example content should feel natural for the target market, while personal data and test credentials should never appear.
Export and submission checklist
Before generating the ZIP, verify the device family, orientation, ordering, and selected pixel presets. After download, open at least the primary size folder and inspect every PNG at full resolution. This final pass catches cropped navigation, typographic errors, stale screens, and accidental transparency before App Store Connect does.
- Use genuine screens from the submitted app version
- Remove debug overlays and personal information
- Confirm every PNG’s dimensions and orientation
- Check spelling and line breaks at full size and thumbnail size
- Upload the files in the intended story order
Frequently asked questions
Do exports contain a watermark?
No. Generated PNG files contain no App Asset Kit branding.
Are images uploaded?
No. Decoding, Canvas rendering and ZIP creation all happen in your browser.
Can every caption be customized?
Yes. Each of the five positions has its own headline and supporting copy.
Are exactly five App Store screenshots required?
No. Five is a useful storytelling set, not a fixed requirement. Check the current App Store Connect rules and use the number needed to explain the product clearly.
Can an iPhone screenshot be reused for iPad?
Do not stretch phone UI into an iPad frame. Apps that support iPad should show a genuine large-screen layout.
Should I use a device frame?
Use one when platform context helps. Choose a frameless layout when showing more real UI is more important; both exports can be store-ready.