Screenshots in ASO: what they are, design rules and how they affect conversion for mobile projects

What Are App Screenshots in ASO

App screenshots are images of mobile application screens that are placed in the store listing and show users what the app looks like and how it works. Unlike text-based ASO elements, screenshots provide visual proof of the product’s design quality and functionality.

Screenshots are the most influential element of the app page in terms of conversion. A SplitMetrics study (2024) showed that users spend 80% of their time on the app page looking at screenshots, and only 20% reading the text description. This makes screenshot design critically important for the success of an ASO strategy.

Unlike the icon, which attracts attention in search results, screenshots work at the persuasion stage: the user has already navigated to the app page and is evaluating whether to install it. High-quality screenshots with clear captions and a logical sequence significantly increase the likelihood of installation.

The Role of Screenshots in Conversion

The role of screenshots in conversion is determined by their ability to quickly and visually demonstrate the app’s key features. According to App Radar (2025), apps with professionally designed screenshots have a 35% higher install conversion rate than apps with simple unprocessed screenshots without captions or design elements.

The first 3 screenshots are viewed by 90% of users, while only 30% reach the last screenshots. This means that the most important features and benefits should be presented in the first screenshots of the set. Each subsequent screenshot should maintain interest and reinforce the desire to install the app.

Screenshot Requirements in Google Play and App Store

Technical requirements for screenshots differ between platforms in terms of size, quantity, and format. Complying with these requirements is mandatory for app publication and correct display of screenshots on all user devices.

Comparison of screenshot requirements across the two platforms:

Google Play Technical Specifications

Google Play allows uploading up to 8 screenshots for phones and up to 8 for tablets. Recommended sizes: 1080×1920 px for phones (16:9 aspect ratio) and 1920×1080 px for tablets (9:16 aspect ratio). Format — PNG or JPEG, minimum side — 320 px.

Google Play also supports screenshots for Android TV, Wear OS, and Chromebooks. Each platform requires separate image sets with appropriate sizes and aspect ratios. Incorrect screenshot sizes result in cropped or stretched images on users’ devices.

App Store Technical Specifications

App Store requires separate screenshot sets for each screen size: 6.5-inch (iPhone 14 Pro Max), 5.5-inch (iPhone 8 Plus), and 4.7-inch (iPhone SE). For iPad, separate screenshots must be uploaded for 12.9 and 9.7 inches. Maximum — 10 screenshots per size.

Minimum resolution for App Store is 1080×1920 px for portrait orientation and 1920×1080 px for landscape. Apple recommends uploading screenshots at the highest available resolution for sharp display on all devices. Low-resolution images pass moderation but look poor on Retina displays.

How to Design Effective Screenshots

Designing screenshots is the process of adding visual elements on top of the original app screen image: captions, arrows, device frames, backgrounds, and color accents. Professionally designed screenshots are significantly more effective than unprocessed ones.

Visual Hierarchy

Visual hierarchy of a screenshot should guide the user’s eye from the most important element to the secondary one. The main element — the app interface screenshot — should occupy 60–70% of the image area, with the remaining space dedicated to captions explaining the on-screen function.

A device frame (phone body around the screenshot) increases user trust and makes the image more realistic. A StoreMaven study (2024) showed that screenshots with a device frame receive 12% more engagement than screenshots without a frame. The frame must accurately match the device shape of the target platform.

Text and Captions

Text on screenshots should be brief — no more than 5–7 words per screenshot. Font — large, contrasting, sans-serif. The text should describe the user benefit, not just name the feature. For example: “Track progress in real time” instead of “Statistics screen.”

For App Store, text on screenshots must be localized for each region. Apple allows text on screenshots, but it must match the app’s functionality and not mislead users. Google Play also recommends localizing screenshot text for each target market.

Color Schemes

The color scheme of screenshot design should match the app’s brand and be contrasting relative to the screen content. It is recommended to use 1–2 accent colors for captions and background to avoid overwhelming the image. The background color should provide sufficient contrast for text readability.

Example of screenshot styling using CSS-like parameters for image generation:

class ScreenshotTemplate:
    def __init__(self, app_color: str):
        self.frame = "device_frame.png"
        self.font_size = 32
        self.text_color = "#FFFFFF"
        self.bg_color = app_color

    def render(self, screenshot: str, caption: str):
        layout = self._build_layout(screenshot)
        layout.add_text(caption, self.font_size, self.text_color)
        return layout.to_image()

This class defines a screenshot design template with customizable parameters: brand color, font size, text color, and background color. Using programmatic screenshot generation allows quickly creating sets for different platforms and localizations without manually designing each image.

Screenshot Order and Storytelling

Screenshot order is a sequence of images that tells a story about the app and guides the user from initial interest to the decision to install. Visual storytelling through screenshots is significantly more effective than simply listing features.

Screenshot Set Structure

The first screenshot is the most important, as it appears in search results next to the icon and app name. It should showcase the main app screen or the most impressive feature. The second and third screenshots reveal key capabilities, giving users an understanding of the app’s value.

The fourth and fifth screenshots show additional features that differentiate the app from competitors. The sixth and seventh screenshots can demonstrate premium features or unique capabilities. The last screenshot often contains a call to install or social proof in the form of ratings and user count.

Storytelling Through Sequence

The screenshot sequence should tell a story: problem → solution → result. The first screenshot shows the user’s problem or need, the second and third show how the app solves this problem, and the fourth shows the result the user gets. This approach increases conversion by 15–20% according to AppTweak.

Example of an effective sequence for a fitness app: welcome screen with a workout plan → run tracking screen → monthly progress statistics → achievements and rewards screen. Each subsequent screenshot strengthens the user’s desire to achieve the same result.

A/B Testing of Screenshots

A/B testing of screenshots allows determining which images and in what order most effectively convert visitors into installs. Google Play Console provides A/B experiment functionality for screenshots, including the ability to test different orders and image sets.

Metrics and Duration

The primary metric for testing screenshots is the CVR (conversion rate) for each variant. Additional metrics include page view time, scroll percentage to a specific screenshot, and clicks on each image.

For statistical significance, a minimum of 7–14 days of testing and 10,000–15,000 impressions per variant is required. Screenshots are sensitive to seasonality: during holiday periods, users may react to visual elements differently than on regular days, which must be considered when planning the experiment.

What to Test in Screenshots

It is recommended to test one element at a time: screenshot order, design color scheme, caption text, presence or absence of a device frame. Testing multiple changes at once makes it impossible to determine which specific change affected the result. Start with screenshot order — this is the simplest change that often yields the greatest effect.

Example A/B test: variant A — first screenshot with the app’s main screen and a caption about the key feature; variant B — first screenshot with the registration screen and a caption about free access. After 14 days of testing, variant B showed 22% more installs, because users value free access information at first glance.

Tools for Creating Screenshots

Among tools for creating designed screenshots, StoreMaven, AppLaunchpad, and Screenshot Studio stand out. StoreMaven provides A/B testing of screenshots with Google Play Console integration. AppLaunchpad automates the generation of localized screenshots for different markets. Screenshot Studio offers ready-made templates for device frames and color schemes.

To automate the process, you can use a Node.js command-line tool for mass screenshot generation:

const config = {
  screenshots: ["main.png", "features.png", "stats.png"],
  captions: ["Home screen", "All features", "Your statistics"],
  deviceFrame: "iphone14",
  primaryColor: "#6200EE"
};

async function generateScreenshots(config) {
  for (const [i, src] of config.screenshots.entries()) {
    const output = await renderScreenshot({
      source: src,
      caption: config.captions[i],
      frame: config.deviceFrame,
      color: config.primaryColor
    });
    await saveImage(output, "screenshot_" + (i + 1) + ".png");
  }
}

This script automates generating a screenshot set with a unified design style and captions. Integrating such a tool into a CI/CD pipeline allows automatically creating up-to-date screenshots for all target platforms and localizations with every app update.

Localizing Screenshots for Different Markets

Localizing screenshots means adapting the text on images for each target market. Users in different countries react differently to colors, symbols, and visual imagery. Localized screenshots are significantly more effective than universal ones.

Text and Language

Text on screenshots must be translated into the target market’s language. App Store and Google Play rank apps higher if screenshots are localized for the user’s language. According to App Radar (2025), localizing screenshots increases conversion by 15–25% for each additional language.

Cultural Adaptation

Cultural differences affect how colors and symbols on screenshots are perceived. Red is associated with danger in Western countries but with luck in China. Images of people should match the ethnic composition of the target market. These factors must be considered when localizing visual elements.

App Store supports separate screenshot sets for each region, allowing full visual design adaptation for each market. Google Play also allows uploading localized screenshots through the developer console.