AppScreenshots DocsUser Guide
A task-focused guide to planning, creating, exporting, and maintaining app-store screenshots with AppScreenshots.
Create app-store screenshots from brief to delivery
This guide follows the work as it actually happens: turn a release or marketing brief into a coherent screenshot set, export the files, publish them, and keep the set current.
A finished screenshot should communicate one benefit at a glance. The product screen remains the evidence behind the claim.
Choose your starting point
Create your first set
Start from a blank project or a template, then make one complete screenshot.
Map languages correctly
Match website locale, screenshot-project language, and market review without confusing their different codes.
Plan a complete release
Turn a screenshot requirement into a frame-by-frame story before you start designing.
Use AI to get a draft
Supply product information, review the analysis, choose a template, and continue in the editor.
Edit and design
Learn the canvas, devices, text, assets, background, and frame controls.
Export and publish
Package individual frames or localized sets and perform a final review.
The end-to-end workflow
| Phase | Outcome | Start here |
|---|---|---|
| 1. Define | A target store, audience, release goal, and a message for each frame | Plan a complete set |
| 2. Build | A master set with real product screens, device frames, copy, and brand treatment | Screenshot Editor |
| 3. Localize | A reviewed variant for every target market | Localization |
| 4. Deliver | Clearly named PNG files or a ZIP ready for review and store upload | Export screenshots |
| 5. Maintain | A reusable source project and an update cadence for releases and experiments | Publish and maintain |
What to prepare
Bring these items before you begin. They prevent late redesigns and make localization much easier.
- Current, high-resolution app screens with no confidential data.
- A single purpose for the screenshot set: launch, feature update, seasonal campaign, or conversion test.
- One short audience benefit per frame; do not try to explain the whole app in every image.
- Brand assets: logo, colors, fonts, and any approved illustrations or badges.
- The platforms, device classes, and languages you need to deliver.
- The working website language, the project master language, and the target-market locales; these are separate choices. See Language support and locale mapping.
Important: AppScreenshots helps you design and export the images. Always confirm the latest file count, dimensions, content, and policy requirements in the store console where you will submit them.
Product areas covered here
The core workflow is built around the Screenshot Editor, with optional help from AI Screenshot Generator, the template library, and related tools such as Mockup Creator and Screenshot Resizer. The guide deliberately separates the source project from the exported files, so a later product update does not force you to start again.
Continue with Create your first screenshot set.