Skip to content

App Store and Google Play screenshot guides

Choose the next step for your app release: plan the design, check store requirements, create a set, or prepare localized versions.

Design the story and layout

Choose the first app moment, write useful headlines and build a sequence that stays clear at listing size.

Browse editable screenshot templates — Choose a layout for your app, then replace its sample screens and copy.

Choose the right store sizes

Check the device slot, image dimensions and format before building the artwork.

Check a screenshot file — Measure an exported image in your browser and compare it with an upload slot.

Create, repair and export a set

Follow the editor workflow, fix file or text problems and review the actual downloaded images.

Fix an App Store screenshot size error

Diagnose a rejected screenshot by measuring pixels, checking its upload slot, orientation and alpha channel. Try reproducible passing and failing image files.

Your screenshot release checklist

Review device coverage, current app content, screenshot dimensions, image formats and the final exported files before updating your store listing.

Explore the screenshot editor — See how templates, editable artwork and screenshot exports fit together.

Prepare repeat releases and locales

Keep captures, translations and release files organized as your app and supported languages change.

Plan a client screenshot handoff — Define the app captures, review steps and deliverables for a repeatable release.

Compare workflows and test a change

Choose a tool against your release needs and separate a design hypothesis from a measured outcome.

Compare Skir export plans — Review the free allowance and paid full-set exports before choosing a workflow.

Compare screenshot workflows

Compare editing, exports and plan limits before choosing a workflow. These pages distinguish our verified behavior from vendor documentation and untested claims.

How we maintain these guides

Apple and Google are the primary sources for their store requirements. Each guide records when those sources were checked. We distinguish file checks from store approval and avoid publishing unsupported product capabilities. Send a correction when a rule or example needs attention.