An App Store screenshot generator that exports the exact sizes Apple accepts
Upload the screens you already have. Get back a finished App Store gallery — device framing, benefit headlines, and files rendered at 1290 × 2796 and 2064 × 2752, flattened RGB, laid out inside the crop margins the store applies. Free to try, no card.
Three free credits on signup · one credit per rendered screenshot · no card required.
What is an App Store screenshot generator?
An App Store screenshot generator is a tool that turns raw captures from your app into the marketing images that appear in your store listing. It handles three jobs you would otherwise do by hand: placing the screen inside a device frame, setting a headline above it, and exporting the result at the exact pixel dimensions App Store Connect will accept.
The reason the category exists is that store screenshots are not screenshots. Apple expects finished marketing images at fixed sizes, flattened with no transparency, laid out so nothing important falls inside the crop the gallery applies. A raw capture from the Simulator satisfies none of that, and a design tool will happily let you export a file that fails at upload.
This generator adds a step most do not: before anything is composed, a vision pass reads your screens together and works out your palette, product category and visual tone. That analysis is what keeps five frames looking like one set, and it is what lets the tool draft headlines about your app rather than leaving you an empty text box.
The two sizes you actually have to produce
App Store Connect asks for one set per device family, but it scales larger sets down. That collapses the whole matrix into two uploads.
1290 × 2796
Required. Exports land here, which is one of the three sizes the 6.9" slot accepts — 1320 × 2868 and 1260 × 2736 are the others. Apple scales this down to every smaller iPhone family.
2064 × 2752
Required only if you ship an iPad build. Covers 12.9" and 11" by scaling.
Every other dimension, upload limit and rejection rule is collected on the screenshot sizes & safe zones reference.
Raw screen in, submittable gallery out
- 01
Upload the raw screens
PNG or JPG straight out of the iOS Simulator, a device, or a Figma export. Up to 10 MB per file. Nothing needs cropping or resizing first — the generator reads the full screen.
- 02
The model reads your app
A vision pass looks at every screen together and writes a description of your palette, product category and visual mood. That description is what keeps all five screenshots looking like one set instead of five unrelated posters.
- 03
Pick target, language and variations
Choose Apple App Store, then iPhone, iPad, or both. Add up to five store languages per batch, and ask for up to four art directions of the same screen.
- 04
Render, refine, export
Each render costs one credit. Refine any frame by talking to the AI agent — asking costs nothing, applying a change costs one credit. Export as a ZIP already foldered as AppStore/iPhone-6.9 and AppStore/iPad-13.
Six things you no longer have to check by hand
Most rejected screenshot uploads fail on a technicality rather than on design. These are enforced at export time.
- Exact pixel dimensions
- Every file leaves at the size App Store Connect expects for the family you picked. A one-pixel mismatch is the single most common upload rejection.
- Flattened RGB, no alpha
- Apple rejects PNGs that still carry a transparency channel. Exports are flattened onto a solid background before they are zipped.
- Safe-zone layout
- Headlines sit in the top band, nothing critical enters the outer 8% gutters, and the framed device stays in the middle 60–70% so the gallery crop never eats your copy.
- Current hardware only
- Device shells are rendered as current Apple hardware. Screenshots showing a discontinued bezel are a documented review flag.
- Thumbnail legibility
- Headlines are laid out at a cap height that still reads at roughly 150 px wide — the size your first two screenshots appear at in search results.
- One set, one look
- Colour, typography and framing carry across the whole batch, including across languages, because every render shares the same theme analysis.
What to look for in a screenshot generator
Six things worth checking in any tool you evaluate, including this one. Where we do not do something, it says so.
| Criterion | Why it matters | Where we land |
|---|---|---|
| Exact export dimensions | A one-pixel mismatch is the most common upload rejection. A tool that exports "roughly iPhone-sized" hands you the problem back. | Rendered at the target canvas, never resized afterwards. |
| Copy, not just framing | Device framing is the easy half. The headline above the frame is what actually moves conversion, and most tools leave it to you. | A vision pass reads your screens and drafts headlines you can rewrite. |
| One coherent set | Five screenshots designed one at a time look like five posters. The set has to share a palette, a typeface and a framing rhythm. | Every frame in a batch shares one theme analysis, including across languages. |
| Localisation that is not retyping | Translating headlines is the highest-yield ASO work there is, and doing it by hand per locale is where teams give up. | Up to five store languages per batch on paid plans. |
| Iteration without starting over | The first draft is never the one you ship. Re-briefing a designer or re-exporting a template is where the days go. | Talk to the agent to refine a frame — asking is free, applying costs one credit. |
| Direct upload to App Store Connect | Some tools publish to the store for you, which saves a manual step at submission time. | Not yet. You get a ZIP foldered by device family and upload it yourself. |
Against the two usual alternatives
| Freelance designer | Template in Figma | This generator | |
|---|---|---|---|
| Time to first draft | 2–5 days | 2–4 hours of your own | Under two minutes |
| Cost of one gallery | $300–$900 | Your afternoon | One credit per frame |
| Correct export sizes | Usually | If the template is current | Enforced at export |
| Extra language set | Re-brief and re-bill | Manual retype per locale | Up to five per batch |
| Iterating a headline | New round trip | Re-export by hand | Ask the agent, re-render |
App Store screenshot questions
How do I generate App Store screenshots?+
Export your app screens as PNG or JPG — from the iOS Simulator, a device, or Figma — then upload them, choose Apple App Store and your device families, and render. The generator frames each screen, writes a headline above it, and exports at the dimensions App Store Connect expects. From upload to a downloadable ZIP is about a minute for a five-frame set.
Is there a free App Store screenshot generator?+
This one has a free tier: three credits on signup, one credit per rendered screenshot, and no card required. That is enough to produce three finished frames and judge the output on your own screens. Paid plans start at $10 a month for 50 credits if you need a full gallery or multiple languages.
What size do App Store screenshots need to be in 2026?+
App Store Connect requires one 6.9" iPhone set — 1320 × 2868, 1290 × 2796 or 1260 × 2736 are all accepted in that slot — plus 2064 × 2752 for the 13" iPad family if your app ships on iPad. Upload those and Apple scales them down for the smaller families. Apple folded the old separate 6.7" slot into 6.9", so guides still listing it are out of date. The 6.5" (1284 × 2778 or 1242 × 2688) and 5.5" (1242 × 2208) slots remain optional.
How many screenshots can I upload per app?+
Up to 10 per device family, per localisation. In practice five to seven deliberate screenshots convert better than ten filler ones, because almost nobody scrolls past the third frame.
Do I need a separate set for every iPhone size?+
No. Supplying the 6.9" set is enough for the whole iPhone lineup — App Store Connect down-scales it. You only need a second set if you want genuinely different artwork on smaller devices.
Can I use the generated screenshots commercially?+
Yes. You keep full ownership of the screens you upload and the mockups generated from them, with a commercial licence covering store listings, landing pages, ads and press kits.
Does it work if my app is not built yet?+
It needs real screens. If you only have Figma frames, export them as PNG at any resolution and upload those — the generator treats a Figma export exactly like a device capture.
Keep reading
Uploading to App Store Connect
Where the screenshot slots live and the order they publish in.
Screenshot requirements & rejections
The rules Apple enforces, and what trips people up.
Google Play screenshots
The same set, sized for Play Console.
Headline formulas
Twelve patterns for the line above the device.
A/B testing your gallery
Product Page Optimization, run properly.
Screenshot best practices
What to put on the first two frames.
Your screens are already good enough
The gallery is what is missing. Upload three screens and see the whole set in about a minute.
Start with 3 free credits