- URL: https://asomaster.app/docs/screenshots/ - Updated: 2026-10-31 - Summary: Design store screenshots in ASOMaster: slides, devices, AI headings in every language, live screenshot import, checks, zip export and upload to the stores. # Screenshots Updated 31 October 2026 The Screenshots tab (⌘4, next to Studio in the app's tabs) turns your app's screens into store screenshots for every device and language of the selected app. This page walks through it from the first slide to the upload. The [screenshot generator page](https://asomaster.app/app-store-screenshot-generator/) has the overview and the device sizes. ## Slides and devices A slide is one screenshot position: a heading in your main language and an image for each device you make. Switch devices on under Devices: iPhone 6.9″, iPad 13″ and Apple Watch Ultra for the App Store; phone, 10″ tablet and the feature graphic for Google Play. The App Store allows 10 slides and Google Play 8; the feature graphic uses slide 1 only. Use the arrows on a slide to change the order. Images are PNG or JPEG up to 15 MB. They don't have to be the device size: ASOMaster fits each image under the heading and rounds its corners. ## Start from your live screenshots **Import from store** fetches the screenshots on your public listing for the selected language: iPhone and iPad from the App Store, phone screenshots and the feature graphic from Google Play. In your main language they fill the slides in order and add slides when the store has more. In another language they become that language's own images on the slides you already have. Images are downloaded only from Apple's and Google's image servers. ## Headings Each slide has one heading line. Keep it within 34 characters, or 40 for scripts without capitals (Japanese, Chinese, Korean, Arabic, Hebrew, Hindi, Thai and similar); the counter under the field shows where you are. Wrap one or two words in `*asterisks*` to show them in the highlight colour. - **Write headings** asks the AI for every slide without a heading. When all slides have one, the button becomes **Rewrite headings**. **Rewrite** on a slide replaces just that one. - The AI gets your listing, the phrases you track and the devices each slide shows, and writes one benefit per slide, starting with an action word. ## Other languages **Translate** adapts every heading to the other languages of the app (its tracked markets and Studio languages), five languages per AI call. Each language uses its own name, subtitle and keywords, so its screenshots repeat its search words. Pick a language above the slides to see and edit its headings and images; anything you set there applies to that language only. A badge on a language counts headings that are missing or were translated from an older main heading. ## Look Choose the background (flat or a top-to-bottom gradient), the heading and highlight colours, the font, capitals and whether the heading sits at the top or the bottom. Capitals leave scripts without case as written. ## Checks The Checks list updates as you edit. Errors block export and upload; warnings don't. - Error: no slides, no device, or a device without a single image. - Warning: a slide without an image for one device (it is left out there), a missing or long heading, missing or outdated translations, and text with a colour contrast below 4.5:1 against the background (3:1 for highlighted words). ## Render and export **Render** draws every slide for every language and device at the exact store size and keeps the result. Any later change to the design or the languages marks the renders as outdated, and Render shows how many are left. **Export** saves a zip with a folder per language (`screenshots/de-DE/01_iphone.png` and so on) and a `manifest.json` with a SHA-256 checksum for each file. ## Upload **Upload to App Store Connect…** or **Upload to Play Console…**, the tab's main action in the app header, is available when the renders are current and a store console is connected ([App Store Connect](https://asomaster.app/docs/app-store-connect/), [Google Play](https://asomaster.app/docs/google-play/)). It replaces, per language and device: - **App Store:** the screenshot set of your editable version. New screenshots are uploaded first and the old ones removed after, so a failure leaves the live set as it was. Languages your version doesn't have yet are reported, not created. - **Google Play:** phone and tablet screenshots and the feature graphic, in one edit committed without sending it for review. If any set fails, nothing is committed. Nothing is submitted for review. AI agents using the [MCP server](https://asomaster.app/docs/mcp/) can read the design (`get_screenshots`) and write or translate headings (`screenshots_write_headings`, `screenshots_translate`), but cannot start an upload.