App Store Screenshot Designer

Screenshots are the largest conversion lever on a listing and the hardest thing to make without a designer. Add a caption and a background to your raw captures and export them at the exact pixel sizes App Store Connect accepts.

Screenshots

Upload your own captures, or pull the ones already on your listing. Apple accepts one to 10.

Style

Size

Apple’s own dimensions. The full specification.

The primary iPhone size — 6.5" is only "required if app runs on iPhone and screenshots for 6.9" display aren't provided".

Apple scales these down for every smaller iPhone, so this size alone covers the iPhone requirement.

Upload your screenshots, or search for your app, and the preview appears here.

Exported as JPEG, not PNG, and that is Apple’s rule rather than a preference: the specification says images “can’t include alpha channels or transparencies”, and a canvas exported to PNG carries an alpha channel even when every pixel in it is opaque.

Nothing is uploaded. The images are drawn in your browser and the ZIP is built there too — local files never leave the page, and only the App Store URLs are kept in your draft.

Why do screenshots decide more than the description does?

Screenshots are the largest piece of a product page a visitor actually looks at, and most people decide from the first two without scrolling. They are also the hardest asset for a solo developer to produce, because a raw capture from the simulator is a picture of a screen rather than a reason to install.

This adds the part that is missing: a caption saying what the screen is for, a background, and a frame — then exports everything at the exact pixel dimensions App Store Connect accepts. It runs entirely in your browser, so nothing you upload leaves the page.

How it works

  1. 1Upload your own captures, or pull the ones already on your listing. Uploaded files stay in the page and are never sent anywhere; only App Store URLs are kept in the saved draft.
  2. 2Write a caption per screenshot. The text is measured against the canvas rather than estimated, so a long caption wraps instead of running off the edge.
  3. 3Pick a background. Loading an app from its listing seeds the colour from the icon where the browser allows the pixels to be sampled — the same measurement /icons uses — and picks a readable text colour by relative luminance rather than defaulting to white.
  4. 4Choose a size and export. You get a ZIP of JPEGs named for the device family and dimensions, in the order you arranged them.

What it cannot tell you

  • It exports JPEG, not PNG, and that is Apple’s rule rather than a preference. The specification says images “can’t include alpha channels or transparencies”, and a canvas exported to PNG carries an alpha channel even when every pixel in it is opaque — so a PNG from a tool like this is rejected at upload with nothing on screen to explain why.
  • An App Store listing serves the developer’s original upload and nothing larger. Measured against a real listing, asking Apple’s image host for 1290, 2000, 3000 and 4000 pixels wide returned the identical 1242×2688 file every time. So screenshots pulled from a listing made for an older iPhone cannot supply a genuine 1320×2868 image, and the page says so rather than quietly enlarging them.
  • The frame is a neutral rounded rectangle, never an iPhone. Apple licenses its product images, requires them used “as is and without modification”, and forbids any use that “falsely suggests an association with Apple”. A developer who wants a real device bezel gets it from Apple and composites it themselves.
  • No claim is made that any of this lifts conversion. Whether a caption helps is measurable only in a Product Page Optimization test inside your own account, and this page has no access to that.
  • It is a layout tool, not an art director. It will not tell you whether the caption is any good, and there is no score — a number over a judgement call only teaches people to design for the checker.

Frequently asked questions

How many screenshots does Apple accept?

One to 10, in .jpeg, .jpg or .png. The size picker only offers the families worth rendering, because Apple states that if screenshots for a given size are not provided, scaled versions of the 6.9" iPhone images are used — so the largest iPhone size covers every smaller iPhone on its own.

Which size do I actually need?

For an iPhone app, the 6.9" size. Apple words the 6.5" requirement as “required if app runs on iPhone and screenshots for 6.9" display aren’t provided”, so supplying the larger one satisfies it. If the app runs on iPad, the 13" iPad size is separately required.

Are my uploaded images sent to a server?

No. They are read into the page, drawn onto a canvas and zipped in your browser. The draft saved between visits contains captions, colours and App Store URLs — never image data, which is a rule this codebase learned the hard way when storing images in local storage filled the origin.

Why is my exported screenshot soft?

Almost always because the source was smaller than the target and had to be enlarged. The page warns when that is about to happen and names both sizes. Export from the simulator at the device resolution you are targeting and it disappears.

Can I use a real iPhone frame around the screenshot?

Not from here. Apple’s device images are licensed artwork with their own rules, so this draws a neutral rounded frame instead. You can download Apple’s product images yourself and composite them if you want the real bezel.