App Store screenshot generator

What this App Store screenshot generator does differently

The output pair is always a row from Apple’s own table — 1320 by 2868 and the two other accepted 6.9-inch sizes, 1284 by 2778 for a 6.5-inch iPhone, the two 13-inch iPad pairs, and 2880 by 1800 for Mac. No arbitrary canvas is available. Each of those was read from App Store Connect’s screenshot specifications on September 7, 2026, and the line under the preview repeats Apple’s own requirement wording for whichever row you have selected.

Supplying the 6.9-inch row is usually all an iPhone app needs. Apple attaches the same kind of note to every smaller display: when screenshots at those sizes are absent, scaled versions of a larger row are used instead, and the chain runs downward. The 6.5-inch row is required only when 6.9-inch is not provided, which their wording states as a condition rather than a rule.

The alpha channel, which is why this is not a canvas export

Apple’s specification carries one sentence in a box of its own: images cannot include alpha channels or transparencies. It rejects more uploads than any dimension does, and the cause is invisible — a browser canvas emits RGBA every time, so a picture with nothing transparent anywhere still ships a fourth channel of solid 255s. The file looks right, opens right, and is refused.

So the PNG here is not produced by the canvas at all. The pixels are read out and handed to an encoder that inspects them, finds them opaque, and writes a PNG color type with no transparency channel in the format. That work happens in a background thread because the smallest canvas offered is over three and a half megapixels, and the progress bar underneath counts rows actually written rather than guessing at a duration. JPEG is the alternative and needs no such care, since the format has no alpha channel to leave out.

A composition satisfies the specification as well as a capture

Nothing Apple publishes says the image must show your app unaltered. The requirement is a file of the right dimensions, in one of three formats, without transparency. That is the whole reason store listings look the way they do: a headline, a background, and the app screen inset inside it, scaled so the words survive being shown at a fraction of full size in search results.

The caption band here is a reserved fraction of the height rather than text floated over the picture, which means the screen never slides underneath your own words. Position it above or below, or switch it off entirely and use the full canvas for the screen.

The caption the page starts with is a template, not a limit. It fits itself to two lines, shrinking the type before it clips anything, because two lines is what stays readable at thumbnail size — a design choice rather than a technical one. The moment you set its size yourself, your size holds and the text wraps as far as it needs to. Add more text layers for a kicker or a second line, each with its own size, color, weight, typeface and anchor; layers on the same anchor stack instead of overlapping, and with no band reserved they sit over the canvas itself.

What is not offered here

No device frames. The bezels around a phone in most store listings are Apple artwork with rules attached, and shipping a copy of them from a page like this one would be careless. What you get instead is a rounded rectangle at a radius you set, which reads as a screen without pretending to be a specific product.

No Apple Watch either, and that omission is deliberate: their Watch row carries a rule the others do not, requiring the same screenshot size across every localization of the app, and a page that hands you a size without being able to hold that rule would be answering half the question. Apple TV and Vision Pro are both 3840 by 2160, which is a plain resize rather than a composition, so the image resizer covers them. The rest of the table, with sources and dates, is in App Store screenshot size.

Related jobs

Android is a different job, not the same job with other numbers. Play Console asks for one mandatory promotional banner at a single size — 1024 by 500 — and puts a play button over the middle of it when your listing has a preview video, which is a constraint Apple’s table has no equivalent for. The Google Play feature graphic generator covers that one, including the center zone the button lands on.

A capture from the wrong simulator is the usual starting problem; image dimensions tells you what you actually have, reporting stored and displayed sizes separately. For framing that is not aimed at Apple’s table at all — a blog post, a changelog, a slide — screenshot beautifier is the simpler page. An existing RGBA PNG that just needs to lose its alpha can go through PNG to JPG, which flattens against a background you pick. And if a finished file is heavier than you want to store, compress image hits a byte target while the dimensions stay exactly where Apple needs them.

Your capture stays here. It is decoded, composed and encoded inside this tab, and this site has no endpoint that could receive an image even if something tried to send one. Verify rather than believe: watch the network panel while you build a set, or read how to verify local processing.