Guide

How to upload App Store screenshots

Jul 19, 2026 Upload, reorder, and validate App Store screenshots by device size. Covers required displays, alpha channels, app previews, and how Helm keeps assets in the right locale and order.

Screenshots do more selling than your description for most browsers. This guide covers device requirements, a clean upload order, preview videos, and how Helm screenshots keep sizes, locales, and sequences under control.

Know which sizes you need

Apple requires screenshots for the device sizes your app supports. Exact slots change over time as new displays ship, so always confirm the current list in App Store Connect or Helm for your version. Typical families include:

iPhone (largest required size for your supported phones)
iPad if you support iPad
Mac if you ship a Mac app
Apple TV or visionOS when those platforms apply

If you only upload for one iPhone size, Apple may derive others, but dedicated assets almost always look sharper for ASO and featuring reviews.

Design for the first three frames

Most people never swipe far. Put the clearest value props in positions one through three:

Core outcome or hero workflow
Differentiator
Social proof, platform perk, or secondary workflow

Captions should be short enough to read at thumbnail size. Avoid walls of marketing copy inside the image.

Prepare files before upload

Export the correct pixel dimensions for each slot
Remove unexpected alpha channels when the storefront rejects them
Keep a consistent safe area so cropped derived sizes do not clip captions
Name files so humans can sort them (locale, device, order)
Match UI language to the locale you are uploading into

If you localize listings, plan screenshot sets per priority market. See localize your App Store listing.

Upload workflow that avoids chaos

Open the version you are shipping.
Select the locale and device group.
Upload in final display order, or upload then reorder immediately.
Add app preview videos where they help, and set poster frames.
Spot-check the product page preview.
Repeat for the next locale or device family.

Doing all iPhone locales before you touch iPad reduces context switching when captions differ by language.

How Helm helps

Screenshots in Helm give you groups by device, upload and reorder flows, and preview video support with a fuller editor on Mac. Marketing “Magic upload” behavior routes images toward the right size, locale, and order so a dropped folder is less likely to land in the wrong slot.

You can also download all or delete all assets for a version when you are resetting a release, open a large preview window on Mac, and manage poster frame timing for previews.

On iOS, screenshot management is available in a lighter form. Use Mac for heavy media days. With helm-asc on Pro, agents and scripts can upload, download, and delete screenshots and previews as part of an automated release pipeline.

App previews without the pain

Previews should demonstrate the app, not a cinematic brand film. Keep them short, silent-friendly with captions, and aligned to the first screenshot’s promise. Set the poster frame to a recognizable UI moment, not a black transition.

Common rejection and QA issues

Wrong resolution for the slot
Alpha channel problems on images that must be opaque
Placeholders or debug UI visible in captures
Mismatched locale (English screenshots under a German listing)
Order that buries the actual product behind abstract lifestyle art

ASO tips that stay honest

Screenshots are part of ASO, but clarity beats keyword stuffing in captions. Show the real product. If you claim a feature on slide two, it should exist in the binary you submit.