DEV Community: Shotlingo

What are Apple Custom Product Pages (CPP) and How to Use Them

Shotlingo — Thu, 30 Apr 2026 10:28:12 +0000

What are Apple Custom Product Pages (CPP) and How to Use Them

If you are running paid campaigns or social promotions for your iOS app and still sending every visitor to the same App Store listing, you are leaving installs on the table. Apple Custom Product Pages let you build up to 35 different versions of your product page, each tailored to a specific audience, channel, or campaign. In this guide we break down what Apple Custom Product Pages are, how they work, how they differ from A/B testing, and the exact steps to set them up in App Store Connect so your marketing finally matches the message users see when they land on the App Store.

By the end of this article you will know how to plan, build, ship, and measure CPPs without wasting review cycles or budget. If you are new to App Store Optimization in general, start with our pillar guide on what ASO is in 2026 and then come back here.

What are Apple Custom Product Pages?

Apple Custom Product Pages (CPP) are alternate versions of your App Store product page that you can create inside App Store Connect. Each custom page can have its own screenshots, app preview videos, and promotional text, while the app name, subtitle, icon, description, and keywords stay the same as your default listing. Each variant gets its own unique URL that you point traffic to from ads, social posts, emails, influencers, or QR codes.

Apple introduced this feature with iOS 15 in December 2021, and it is now a standard part of any serious iOS marketing stack. You are allowed up to 35 active custom product pages per app, which is more than enough to cover most personas, ad creatives, and seasonal campaigns.

The key idea is simple: the right message to the right person. Instead of one generic page trying to please everyone, you build focused pages that speak directly to a specific use case, demographic, or campaign theme.

How Apple Custom Product Pages Differ from the Default Listing

Your default product page is the one users land on when they search the App Store, tap your app from a chart, or follow a generic share link. It needs to appeal to your broadest audience. A Custom Product Page, on the other hand, is reached only through its unique URL, so it can be hyper-targeted.

Here is what you can and cannot change inside a CPP:

You can change: screenshots (all sizes), app preview videos, and the promotional text.
You cannot change: app name, subtitle, icon, full description, keywords, category, price, or in-app purchase details.

This matters for two reasons. First, the parts you can change are exactly the visual assets that drive conversion, so CPP gives you leverage where it counts. Second, because the metadata stays consistent, your organic search ranking is not split or diluted. You keep one strong default page for ASO and add tactical variants for paid and social.

If you want inspiration for what to put in those variant screenshots, our roundup of App Store screenshot examples that convert shows patterns that work across categories.

Apple Custom Product Pages vs Product Page Optimization (PPO): Key Differences

People often confuse Custom Product Pages with Product Page Optimization. They are both Apple features and both involve alternate visuals, but they solve different problems. CPP is about targeting different audiences with different content. PPO is about testing which content converts best on your default page.

  | Feature 
  | Custom Product Pages (CPP) 
  | Product Page Optimization (PPO) 




  | **Primary purpose** 
  | Targeting different audiences with different creatives 
  | A/B testing variants against the default listing 


  | **Number of variants** 
  | Up to 35 active 
  | Up to 3 treatments per test 


  | **Traffic source** 
  | You drive traffic via unique URLs 
  | Apple splits organic traffic automatically 


  | **What you change** 
  | Screenshots, preview videos, promo text 
  | Icon, screenshots, or preview videos 


  | **Measurement** 
  | Per-page conversion in App Analytics 
  | Statistical winner declared by Apple 


  | **Best used for** 
  | Paid ads, social campaigns, partnerships 
  | Improving the default organic listing

The two features are complementary. Many teams run PPO to find the strongest default listing and use CPP to build variants of that listing for paid channels. If you are unsure how testing actually works in practice, our walkthrough on screenshot A/B testing covers methodology and pitfalls.

Apple Custom Product Pages Use Cases by App Category

Almost every category benefits from CPP, but the highest-leverage use cases tend to fall into a few buckets. Below is a quick map of what to build first based on your app type.

  | App Category 
  | Suggested Custom Product Pages 




  | Fitness 
  | One page for runners, one for yoga, one for strength training, one for beginners 


  | Finance 
  | One for budgeting, one for investing, one for crypto, one for couples or families 


  | Games 
  | One per game mode, one per featured character, one per seasonal event 


  | Productivity 
  | One for students, one for freelancers, one for teams, one for power users 


  | Travel 
  | One per destination cluster, one for business travelers, one for family trips 


  | Food and recipes 
  | One for vegan, one for keto, one for meal prep, one for quick weeknight meals 


  | Education 
  | One per language, one per skill level, one for parents, one for self-learners 


  | Shopping 
  | One per product category, one for deal hunters, one for gift season

You can also use CPP for localization-style campaigns, where you push a market-specific page to a specific country audience without touching your global default. If you are scaling internationally, our localization hub walks through the related decisions on languages, currencies, and screenshot translation.

How to Set Up Apple Custom Product Pages

Setting up a CPP is straightforward, but a few details trip up first-time users. Here is the full flow.

Step 1: Create the variant in App Store Connect

Sign in to App Store Connect, open your app, and go to the Custom Product Pages section under the General sidebar. Click the plus icon to add a new page. Give it a clear internal name like Runners-Q2-Meta so you can find it later among many variants. The internal name is never shown to users.

Step 2: Customize screenshots, video, and promotional text

Upload the screenshot set for every device size you support, including iPhone 6.7 inch, iPhone 6.5 inch, iPad Pro, and any others required. You can also replace the app preview video and the promotional text. Treat each variant like its own creative brief: the message, copy on the screenshots, and hero shot should align with the audience that will land on this page.

If you need fast, on-brand screenshot variants without rebuilding everything in design software, our free ASO tools can generate localized and audience-specific sets in minutes.

Step 3: Submit for review

Each Custom Product Page goes through App Review, just like the default listing. Review usually takes 24 to 48 hours, sometimes faster, sometimes longer around major iOS releases. You can submit a CPP independently of an app build, which means you can launch new variants without shipping new code. Apple's official documentation on this flow lives in the Apple Developer site.

Step 4: Get the unique URL

Once approved, your CPP is assigned a unique URL of the form https://apps.apple.com/app/idXXXXXXXX?ppid=YYYYYYYY, where the ppid parameter is what tells Apple to serve this specific variant. This URL is safe to share publicly. Visitors who do not have iOS 15 or later will see your default page, and the rest will see the custom variant.

Step 5: Drive targeted traffic

Now route the right audience to the right URL. Use the ppid link in:

Apple Search Ads campaigns (you can attach a CPP directly to an ad group).
Meta, TikTok, and Google ad creatives that match the variant theme.
Influencer codes, newsletters, and partnership landing pages.
QR codes on offline marketing or events.
Push messages and emails segmented by user interest.

Tracking Performance of Custom Product Pages

Tracking is where CPP earns its keep. Inside App Store Connect, open App Analytics and look at the Sources panel, then drill into Custom Product Pages. For every variant you can see impressions, product page views, conversion rate, and downloads. Compare each CPP against your default page to know whether the targeting is working.

Some practices that pay off:

Always compare conversion rate, not just total downloads. A CPP that gets less traffic but converts at twice the rate is a winner.
Tag each ppid URL with UTM parameters in your ad platform so you can join data across MMP, ad network, and App Store Connect.
Give each variant at least 1,000 to 2,000 page views before drawing conclusions, otherwise you are reading noise.
Refresh creatives every quarter. Ad fatigue applies to product pages too.

Apple's full data model for this is documented in the App Store Connect API reference if you want to pull metrics into your own dashboard.

Common Mistakes with Apple Custom Product Pages

Here are the patterns we see hurt teams most often when they roll out CPP for the first time.

Treating CPP like A/B testing. CPP does not split traffic for you. If you want statistical winners on the default page, use PPO instead.
Building too many variants too fast. Start with three to five high-intent audiences. Thirty-five pages you cannot maintain is worse than five sharp ones.
Forgetting localization. A CPP is per locale, just like the default page. If you serve multiple markets, plan translations from day one.
Ignoring the first screenshot. Most users decide based on the first one or two screenshots. If those do not change between variants, you are barely customizing anything.
Not aligning ad creative with the page. The hook in the ad and the hero shot on the CPP must match. Mismatched messaging tanks conversion.
Skipping measurement. If you do not check App Analytics, you cannot tell which variants to keep or kill.

FAQ

How many Apple Custom Product Pages can I have per app?

You can have up to 35 active Custom Product Pages per app, in addition to your default product page. Each one needs to be submitted to App Review individually.

Do Apple Custom Product Pages affect my App Store ranking?

No. Custom Product Pages do not influence keyword ranking on the default App Store search results. Only your default listing's metadata, name, subtitle, and keywords feed into search ranking. CPPs only change what users see after they click your unique URL.

Can I use Custom Product Pages with Apple Search Ads?

Yes. You can attach any approved CPP to a specific Apple Search Ads ad group, so users who tap that ad see a tailored page instead of the default listing. This is one of the highest-ROI ways to use CPP.

Ready to Build Your First Custom Product Page?

Apple Custom Product Pages turn a single static listing into a flexible storefront that speaks to every audience in their own language. Map your top three customer personas, build one CPP per persona, point your strongest paid channel at each, and measure conversion in App Analytics. That is the entire playbook.

If you want help producing the screenshot sets that make each variant convert, create a free Shotlingo account and generate audience-specific screenshots in minutes instead of weeks.

Originally published on Shotlingo

What is ASO and Why It Matters in 2026

Shotlingo — Mon, 27 Apr 2026 16:12:44 +0000

What is ASO and Why It Matters in 2026

If you have ever wondered what is ASO and why every mobile growth team keeps talking about it, this guide is for you. ASO stands for App Store Optimization, and in 2026 it has quietly become the single most cost-effective way to acquire users for a mobile app. With more than 5 million apps competing for attention across the App Store and Google Play, getting found is no longer optional.

This pillar post walks through the definition, the ranking factors, the differences between platforms, and a practical playbook you can start using this week. By the end, you will know exactly how to evaluate, plan, and ship an ASO strategy that compounds over time.

What is ASO? A Simple Definition

ASO (App Store Optimization) is the process of improving an app's visibility and conversion rate inside mobile app stores like the Apple App Store and Google Play. The goal is to rank higher for relevant search queries and to convert more of those store visitors into installs.

Think of ASO as SEO's mobile cousin. Where SEO targets Google Search, ASO targets the search and discovery surfaces inside app stores. The mechanics are different, the ranking signals are different, and the user intent is much closer to a purchase decision.

A complete ASO strategy covers three layers: textual metadata (title, subtitle, keywords, description), visual assets (icon, screenshots, preview videos), and performance signals (downloads, ratings, retention, and reviews). Strong apps optimize all three at once.

Why App Store Optimization Matters More Than Ever in 2026

Paid user acquisition costs have climbed every year since the iOS 14.5 privacy changes. Average cost per install on iOS now sits well above 5 dollars in many western markets, and even higher for finance and dating verticals. ASO, by contrast, is owned media. Once you rank, the traffic keeps flowing without paying per click.

Organic search is also where most installs still come from. Apple has reported that roughly 65 percent of App Store downloads happen after a search, and Google has shared similar numbers for the Play Store. If you ignore app store optimization, you are leaving the majority of your potential users untouched.

Three trends make ASO even more important in 2026:

AI-driven discovery. Both stores are leaning harder on machine learning to personalize search and Today tab recommendations. Clean metadata and high conversion rates feed those models.
Custom Product Pages and Store Listing Experiments. You can now test different screenshots and value propositions per audience without shipping a new build.
Localization at scale. Apps that localize properly grow installs by 25 to 40 percent in non-English markets. Tools have made this dramatically cheaper than it was even two years ago.

How ASO Actually Works

Both stores run a ranking algorithm that takes a search query and returns an ordered list of apps. The algorithm scores each candidate app on relevance (does the metadata match the query?) and authority (is this app good enough to recommend?).

Relevance is largely about words. The App Store reads your title, subtitle, and keyword field. Google Play indexes your full long description and short description. Match the right phrases, and you become eligible to rank.

Authority is about behavior. Apps with high install velocity, strong ratings, low uninstall rates, and engaged users get promoted. This is why a beautiful listing alone is not enough. The store wants to recommend products users will keep.

Conversion rate ties it all together. If 100 people see your listing and 35 install, you have a 35 percent conversion rate. Higher conversion means the store earns more revenue per impression, so the algorithm shows your app to even more people. This is the flywheel ASO unlocks.

The Key ASO Ranking Factors

Not every signal matters equally, and the weighting differs between Apple and Google. The table below summarizes the main ranking factors and their relative impact on each store.

  | Factor 
  | App Store (iOS) 
  | Google Play (Android) 
  | Impact on rankings 




  | App name / title 
  | 30 characters indexed 
  | 30 characters indexed 
  | Very high 


  | Subtitle / short description 
  | 30 characters indexed 
  | 80 characters indexed 
  | High 


  | Keyword field 
  | 100 characters, hidden 
  | Not used 
  | High on iOS 


  | Long description 
  | Not indexed for search 
  | 4000 characters indexed 
  | High on Android 


  | Ratings and reviews 
  | Strong factor 
  | Strong factor 
  | High 


  | Install velocity 
  | Yes 
  | Yes 
  | High 


  | Retention and engagement 
  | Yes 
  | Yes 
  | Medium to high 


  | Icon, screenshots, video 
  | Conversion only 
  | Conversion only 
  | Indirect but huge

On-metadata factors (title, subtitle, keywords, description)

These are the words you write in App Store Connect or Google Play Console. They are the foundation of relevance. Use them to cover your most important keywords without stuffing or repeating phrases. Our guide on ASO keyword optimization walks through how to research and pick these terms.

Off-metadata factors (downloads, ratings, reviews, retention)

You cannot edit these directly, but you can influence them. Smart in-app review prompts, fast bug fixes, and a focus on day 7 retention all push these signals in the right direction. A 4.6-star app with 10,000 reviews will almost always outrank a 4.2-star app with 1,000 reviews for the same query.

Visual factors (icon, screenshots, preview video)

Visuals do not directly change your search ranking, but they decide whether someone taps install after they find you. A polished icon and clear screenshots can lift conversion by 20 to 30 percent, which feeds back into install velocity and rankings. See our breakdown of screenshots that convert for proven layouts.

ASO vs SEO: What's the Difference?

People often ask whether ASO is just SEO for apps. The answer is yes and no. The intent is similar, but the playing field is very different.

  | Dimension 
  | SEO (Google Search) 
  | ASO (App Stores) 




  | Index size 
  | Hundreds of billions of pages 
  | Around 5 million apps 


  | Primary unit 
  | Web page 
  | App listing 


  | Keyword research source 
  | Google Keyword Planner, Ahrefs 
  | Apple Search Ads, Google Play autosuggest 


  | Conversion event 
  | Click to website 
  | Tap install 


  | Off-page signal 
  | Backlinks 
  | Installs, ratings, retention 


  | Iteration speed 
  | Hours 
  | Days, due to store review

The biggest practical difference is the smaller universe in app stores. With only a few million apps total, ranking on page one is more achievable than ranking on Google for a competitive query, especially for niche categories.

How to Get Started with ASO

You do not need a giant team to do ASO well. Most of the impact comes from doing four things consistently.

Keyword research

Start by listing every word a user might type to find your app. Then check search volume and difficulty using Apple Search Ads suggestions or a tool like Sensor Tower. Aim for terms with real volume and reasonable competition. You can experiment with our free ASO tools to brainstorm and validate keywords without paying for a full subscription.

Optimize your screenshots

Your first three screenshots do most of the conversion work. Lead with your strongest value proposition, use bold caption text, and keep visuals consistent across the gallery. New publishers often ask how many screenshots they should upload, and the short answer is at least 6 to 8 to fill the carousel and tell a complete story.

Localization

Localizing your listing into 5 to 10 languages can unlock entirely new markets. Translation alone is not enough. You also need localized keywords, screenshots, and cultural references. Our localization hub covers what to translate first and how to prioritize markets by potential ROI.

Track and iterate

ASO is a loop, not a one-time launch. Watch your impression-to-install ratio every week. When a screenshot variant wins, ship the change. When a keyword starts trending, update your metadata. Small weekly improvements compound into significant gains over a year.

ASO Mistakes to Avoid

Most apps lose more from common mistakes than they gain from clever tactics. Watch out for these.

Keyword stuffing. Repeating the same word in title, subtitle, and description does not help and can look spammy to users.
Generic screenshots. Bare device frames with no captions waste your most valuable real estate. Read our list of screenshot mistakes to avoid to skip the obvious traps.
Ignoring reviews. Unanswered one-star reviews quietly drag down your rating. Reply, fix, and ask happy users for feedback.
Launching once and walking away. Stores reward freshness. Apps that update their metadata and creative every month tend to outperform those that do not.
Skipping localization. English-only listings cap your growth at maybe 30 percent of the global market.

Frequently Asked Questions

How long does ASO take to show results?

Metadata changes can move rankings within 24 to 72 hours. Bigger gains from improved ratings, retention, and conversion usually take 4 to 8 weeks to compound. Treat ASO as a quarterly discipline, not a one-week sprint.

Is ASO free?

The work itself is free. You can do strong ASO with no budget if you have time to research and iterate. Paid tools speed things up, and tests like Custom Product Pages can require some traffic to reach significance, but the core practice is accessible to indie developers.

What's the difference between ASO and Apple Search Ads?

ASO is organic. Apple Search Ads is paid. They are complementary. Search Ads data, especially Search Match impressions, is one of the best free sources of keyword research for organic ASO.

Do I need different ASO strategies for iOS and Android?

Yes. Apple uses a dedicated keyword field, while Google indexes your full description. Visual and performance optimization is similar, but text strategy differs significantly. Build two separate plans rather than copying one across stores.

The Tools That Make ASO Easier

You can do ASO with a spreadsheet and patience, but a few categories of tools save real time. Keyword research platforms surface volume and difficulty. Screenshot builders like Shotlingo turn raw mockups into store-ready visuals across every device size and language. Analytics suites track your rank and conversion over time.

If you are weighing options, our comparison of Shotlingo vs AppLaunchpad covers how the leading screenshot tools differ on speed, localization support, and template quality.

For deeper reference material, Apple's official App Store product page documentation and Google's Play Console listing guide are both worth bookmarking. Industry data from data.ai insights is also a good source for benchmarking your performance against your category.

Putting It All Together

If you remember one thing from this post, let it be this. ASO is a compounding asset, not a one-off project. Every keyword you research, every screenshot you test, and every review you earn makes the next install slightly cheaper. Teams that treat ASO as a weekly habit tend to outgrow teams that treat it as a launch checklist.

Start with keyword research. Improve your screenshots. Localize for two or three target markets. Watch your conversion rate. Repeat next month. That simple loop, run patiently, is what separates apps that quietly disappear from apps that climb the charts.

Ready to ship better screenshots in every language?

Shotlingo helps you design, localize, and update App Store and Google Play screenshots in minutes instead of days. You get device-perfect mockups, AI translations, and templates designed by performance marketers.

Try Shotlingo free and put what you learned about app store optimization into practice today.

Originally published on Shotlingo

10 Common App Store Screenshot Mistakes to Avoid

Shotlingo — Thu, 23 Apr 2026 10:05:13 +0000

10 Common App Store Screenshot Mistakes to Avoid

Your App Store screenshots are your storefront. They are the single biggest factor in whether someone taps "Get" or keeps scrolling. Yet most developers sabotage their own downloads by repeating the same app store screenshot mistakes over and over again.

The good news? These mistakes are easy to fix once you know what to look for. In this guide, we break down the 10 most common app store screenshot mistakes, explain why each one hurts conversions, and show you exactly how to fix them.

Why App Store Screenshot Mistakes Cost You Downloads

According to Apple's own product page guidelines, screenshots are the first visual content most users see. On the App Store, the first three screenshots appear before a user even reads your description.

Research from SplitMetrics suggests that well-optimized screenshots can improve conversion rates by up to 35%. That means bad screenshots are not just a design problem. They are a revenue problem.

Whether you are launching a new app or trying to improve an existing listing, avoiding these mistakes should be at the top of your ASO checklist. If you need a broader toolkit to audit your listing, check out our free ASO tools.

The 10 Most Common App Store Screenshot Mistakes

1. Using Low-Resolution or Blurry Screenshots

This sounds obvious, but it happens more often than you would think. Developers upload screenshots that are slightly stretched, compressed, or taken from a simulator at the wrong resolution. The result is a blurry first impression that screams "amateur."

Apple requires specific pixel dimensions for each device. An iPhone 15 Pro Max screenshot must be exactly 1320 x 2868 pixels. Uploading anything smaller and then scaling it up will produce visible artifacts.

The fix: Always export screenshots at the exact required resolution. Use device-native screen captures or a tool like Shotlingo that generates pixel-perfect mockups automatically.

2. Leading With a Splash Screen or Login Page

Your first screenshot is the most important one. It is what users see in search results before they even tap on your listing. If that first image shows a generic splash screen or a login form, you have already lost.

Nobody downloads an app because the login page looks nice. They download it because they can see the value inside.

The fix: Lead with your best feature. Show the core experience of your app in the very first screenshot. Save onboarding flows for your actual onboarding, not your marketing.

3. Cramming Too Much Text Onto Screenshots

A common instinct is to explain everything on every screenshot. This leads to tiny fonts, dense paragraphs overlaid on the UI, and an overall cluttered look that nobody reads.

Remember that most users browse the App Store on a phone. Your text needs to be readable at a glance on a 6-inch screen. That means short headlines, not paragraphs.

The fix: Limit each screenshot to one headline of 5 to 8 words. Use a large, bold font. Let the UI speak for itself. For inspiration, see our roundup of app store screenshot examples that actually convert.

4. Using Outdated Device Mockups

If your screenshots still show an iPhone X notch or an iPhone 8 with a home button, users will assume your app has not been updated in years. Outdated device frames signal neglect.

Apple regularly updates its device lineup, and your marketing materials should reflect that. Users want to see your app running on a device that looks like the one in their pocket.

The fix: Update your mockups whenever Apple releases a new flagship device. Use the latest iPhone and iPad frames. Shotlingo keeps its device library current so you never have to worry about this.

5. Not Using All Available Screenshot Slots

Apple lets you upload up to 10 screenshots per device size. Many developers stop at 3 or 4. That is leaving free real estate on the table. Not sure how many you should use? We cover that in detail in our guide on how many screenshots you need for the App Store.

Each screenshot is an opportunity to highlight a different feature, address a different user concern, or reinforce your value proposition.

The fix: Use at least 6 to 8 screenshots. Cover your core features, show social proof if you have it, and end with a clear call to action. More screenshots mean more chances to convince.

6. Ignoring Localization

This is one of the most expensive app store screenshot mistakes you can make. If your app is available in 40 countries but your screenshots are only in English, you are ignoring the majority of your potential users.

A user in Japan scrolling through the App Store expects to see Japanese text. A user in Germany expects German. Showing them English-only screenshots creates friction and kills trust.

The fix: Localize your screenshots for every market that matters. This used to be expensive and time-consuming, but tools like Shotlingo make it fast. Start with your top markets. For example, our German screenshot localization page walks you through the process step by step. You can explore all supported languages on our localization hub.

7. No Clear Headline or Value Proposition on the First Screenshot

Some developers show their app UI in the first screenshot without any text at all. Others use a vague tagline like "The best app for you." Neither approach works.

Your first screenshot headline should communicate a specific benefit in plain language. What problem does your app solve? Say it clearly.

The fix: Write a headline that answers the question "Why should I download this?" in under 8 words. Be specific. "Track your spending in 10 seconds" beats "The ultimate finance app" every time.

8. Inconsistent Visual Style Across Screenshots

When each screenshot uses a different background color, font, or layout style, the overall impression is chaotic. It looks like the screenshots were made by different people at different times, which they probably were.

Consistency builds trust. It signals professionalism and attention to detail.

The fix: Create a template with fixed colors, fonts, and layout grids. Apply it to every screenshot. This is one of the biggest advantages of using a dedicated screenshot tool rather than designing each image from scratch in Figma.

9. Showing Features Nobody Cares About Instead of Benefits

Developers love their features. Users care about outcomes. There is a big difference between "Advanced filtering system with 47 parameters" and "Find exactly what you need in seconds."

Features are what your app does. Benefits are what your app does for the user. Your screenshots should focus on the latter.

The fix: For each screenshot, ask yourself: "What does the user gain from this?" Lead with the benefit in your headline and let the UI demonstrate the feature underneath.

10. Never Updating Screenshots After Major UI Changes

You redesigned your app six months ago, but your App Store screenshots still show the old interface. When a user downloads your app and sees something completely different from what was advertised, you get bad reviews and refund requests.

Outdated screenshots also mean you are missing the chance to show off your latest and greatest work.

The fix: Add screenshot updates to your release checklist. Every time you ship a major UI change, update your screenshots. With Shotlingo, regenerating localized screenshots across all languages takes minutes, not days.

Quick Reference: App Store Screenshot Mistakes vs Fixes

Use this table as a checklist when auditing your current App Store listing.

| Mistake
| Why It Hurts
| Fix

| Low-resolution or blurry images
| Looks unprofessional, erodes trust
| Export at exact required pixel dimensions

| Leading with splash/login screen
| Wastes your most valuable slot
| Show your best feature first

| Too much text on screenshots
| Unreadable on mobile, cluttered look
| One headline per screenshot, 5-8 words

| Outdated device mockups
| Signals a neglected, outdated app
| Use current-generation device frames

| Not using all screenshot slots
| Missed opportunities to convince
| Use at least 6-8 of 10 available slots

| No localization
| Alienates non-English-speaking users
| Localize screenshots for top markets

| No headline on first screenshot
| Users do not understand the value
| Write a specific, benefit-driven headline

| Inconsistent visual style
| Looks chaotic and unprofessional
| Use a consistent template across all shots

| Features instead of benefits
| Users do not connect with technical jargon
| Lead with what the user gains

| Never updating screenshots
| Mismatch between listing and actual app
| Update screenshots with every major release

FAQ

What is the biggest app store screenshot mistake?

Ignoring localization is arguably the most costly mistake because it affects every non-English market simultaneously. If your app is available globally but your screenshots are English-only, you are leaving significant download volume on the table. Apple strongly encourages localization and gives localized apps better visibility in regional search results.

How many screenshots should I use on the App Store?

Apple allows up to 10 screenshots per device size. We recommend using at least 6 to 8. Each screenshot should highlight a different benefit or feature. The first three are the most critical because they appear in search results before a user taps into your listing. Read our full breakdown in how many screenshots you need for the App Store.

How often should I update my App Store screenshots?

Update your screenshots whenever you make a significant UI change, rebrand, or add a major feature. At minimum, review your screenshots quarterly. Seasonal updates can also boost engagement if done tastefully. The key is making sure what users see in the store matches what they get after downloading.

Stop Making These Mistakes Today

Every one of these app store screenshot mistakes is fixable, and fixing them can directly increase your download rate. You do not need a design team or a massive budget. You need the right tool and a clear understanding of what works.

Shotlingo helps you create professional, localized App Store screenshots in minutes. No design skills required. Generate pixel-perfect mockups, localize into 40+ languages, and keep your listing fresh with every update.

Try Shotlingo free and start turning your screenshots into your best conversion asset.

Originally published on Shotlingo

How Many Screenshots Do You Need for the App Store?

Shotlingo — Mon, 20 Apr 2026 08:30:59 +0000

How Many Screenshots Do You Need for the App Store?

If you're wondering how many screenshots app store listings actually require, here's the quick answer: Apple allows up to 10 screenshots per device size, and Google Play allows up to 8. Apple requires at least 1, while Google requires a minimum of 2. But the real question isn't how many you can upload. It's how many you should upload to maximize downloads. In this guide, we'll break down the exact limits, what works best, and how localization multiplies your screenshot needs.

The Short Answer: How Many Screenshots App Store Listings Need

You should use all 10 screenshot slots on the App Store and all 8 on Google Play. Every screenshot is an opportunity to communicate value, address objections, and convince someone to tap "Get." Studies consistently show that apps using the maximum number of screenshots see higher conversion rates than those using fewer.

Most users never scroll past the first three, though. So while quantity matters, the order and quality of your screenshots matter even more.

Screenshot Limits by Platform

The number of screenshots you can upload depends on the platform and device type. Here's a full breakdown.

| App Store (iOS)
| iPhone 6.7" (Super Retina XDR)
| 1
| 10 |
| App Store (iOS)
| iPhone 6.5" (Super Retina)
| 1
| 10 |
| App Store (iOS)
| iPhone 5.5" (Retina HD)
| 1
| 10 |
| App Store (iOS)
| iPad Pro 12.9" (6th gen)
| 1
| 10 |
| App Store (iOS)
| iPad Pro 12.9" (2nd gen)
| 1
| 10 |
| Google Play
| Phone
| 2
| 8 |
| Google Play
| 7-inch Tablet
| 0
| 8 |
| Google Play
| 10-inch Tablet
| 0
| 8 |

On the App Store, you can set different screenshots for each device display size. On Google Play, phone screenshots are required, but tablet screenshots are optional. According to Apple's official screenshot specifications, the 6.7-inch display is the primary required size for new submissions.

How Many Screenshots Should You Actually Use?

The answer is simple: use every slot available. If you're on iOS, upload 10. If you're on Google Play, upload 8.

Here's why. Each screenshot is free real estate on one of the most competitive storefronts in the world. Apps that use all available screenshot slots give users more reasons to download. More screenshots means more features highlighted, more social proof displayed, and more objections addressed.

A SplitMetrics analysis found that optimized screenshot galleries can increase conversion rates by up to 25%. Leaving slots empty is leaving conversions on the table.

What to Show in 10 Screenshots

If you're struggling to fill all 10 slots, here's a suggested framework:

Screenshot 1: Hero shot with your main value proposition
Screenshot 2: Core feature demonstration
Screenshot 3: Second key feature or unique differentiator
Screenshots 4-6: Additional features, UI highlights, or use cases
Screenshot 7-8: Social proof, awards, press mentions, or ratings
Screenshots 9-10: Onboarding simplicity, pricing clarity, or a final CTA

Need inspiration? Check out our roundup of App Store screenshot examples that convert for real-world galleries that nail this structure.

Which Screenshots Matter Most?

The first three screenshots are by far the most important. When a user finds your app in search results or browses a category, only the first three screenshots are visible without tapping into your listing. This is true on both iOS and Android.

Think of these three screenshots as your storefront window. They need to instantly communicate what your app does and why someone should care. If your first three screenshots don't grab attention, the other seven won't matter because nobody will ever see them.

Best Practices for Your First 3 Screenshots

Lead with benefits, not features. "Save 2 hours a week" beats "Built-in calendar sync."
Use bold, legible captions. Text should be readable at thumbnail size.
Show the app in action. Real UI builds trust faster than abstract graphics.
Create visual continuity. A panoramic design across all three encourages swiping.

Your first screenshot alone can account for the majority of your conversion impact. Treat it like a billboard: one clear message, zero clutter.

Do You Need Different Screenshots for Each Device Size?

On the App Store, you can provide unique screenshots for each display size: 6.7-inch, 6.5-inch, and 5.5-inch iPhones, plus multiple iPad sizes. But do you actually need to?

Technically, no. Apple will scale your largest iPhone screenshots down for smaller sizes if you don't provide separate assets. However, providing device-specific screenshots ensures your visuals look crisp and correctly proportioned on every device.

For iPad, separate screenshots are strongly recommended if your app has a distinct tablet experience. iPad users browsing the App Store on their device will see iPad-specific screenshots. If you only provide iPhone screenshots, your listing may look unpolished to tablet users.

A Practical Approach

At minimum, provide screenshots for these sizes:

iPhone 6.7" (required for new apps)
iPhone 6.5" (covers older Pro Max models)
iPad Pro 12.9" (if your app supports iPad)

That's 30 screenshot assets just for English if you fill all 10 slots per device. This is where tools like free ASO tools and screenshot generators save serious time.

How Many Screenshots Do You Need for Each Language?

This is where the math gets interesting. Apple supports over 35 localizations on the App Store. Google Play supports even more. And each localization can have its own unique set of screenshots.

If you localize your app into 10 languages and provide all 10 screenshots for 3 device sizes on iOS, that's 300 individual screenshot assets. For Google Play with 8 screenshots across the same 10 languages, that's another 80.

The math is straightforward but the workload is enormous.

Why Localized Screenshots Matter

Users who see screenshots in their native language are significantly more likely to download. Localized screenshots signal that the app experience itself is localized, not just the listing. It builds trust before the user even opens your app.

That said, manually creating hundreds of screenshot variants is impractical for most teams. This is exactly why we built Shotlingo's localization hub. You design your screenshot templates once, then generate localized versions for every language automatically.

For example, localizing your screenshots into Japanese is one of the highest-impact moves you can make. Japan is the third-largest app market globally. Our guide on localizing App Store screenshots to Japanese walks through the full process.

How Many Languages Should You Localize Into?

Start with the languages where you already have the most users or the highest revenue potential. For most apps, that means:

English (US and UK)
Japanese
German
French
Spanish
Korean
Chinese (Simplified)
Portuguese (Brazilian)

Even localizing into just 5 languages can dramatically expand your reach. The key is that each language needs its own complete set of screenshots to be effective.

Frequently Asked Questions

Can I use the same screenshots on the App Store and Google Play?

You can, but you shouldn't. The aspect ratios and display sizes differ between iOS and Android devices. Screenshots designed for iPhone dimensions will look stretched or cropped on Android listings. Additionally, each platform has different visual conventions that users expect. Design platform-specific screenshots for the best results.

Do App Store screenshots affect search rankings?

Screenshots don't directly impact keyword rankings in App Store search. However, they heavily influence your conversion rate, which is a factor Apple considers. Higher conversion rates signal a quality listing, which can indirectly boost your visibility. If you want to improve your ASO holistically, compare Shotlingo to other screenshot tools to find the right fit for your workflow.

How often should I update my App Store screenshots?

Update your screenshots whenever you ship a major UI change, add a significant feature, or run seasonal promotions. At minimum, review and refresh your screenshots every quarter. A/B testing different screenshot variations regularly is one of the most reliable ways to improve conversion over time.

Start Optimizing Your Screenshots Today

Now you know the numbers: up to 10 on iOS, up to 8 on Google Play, and ideally a full set for every language you support. The apps that win are the ones that treat every screenshot slot as a conversion opportunity.

Whether you need to create your first set of screenshots or localize existing ones into dozens of languages, Shotlingo makes the process fast and painless. Design once, generate everywhere.

Try Shotlingo free and see how quickly you can build a complete, localized screenshot gallery for every store and every language.

Originally published on Shotlingo

App Store Screenshot Examples: 15 Designs That Convert

Shotlingo — Mon, 20 Apr 2026 08:30:41 +0000

App Store Screenshot Examples: 15 Designs That Convert

Your app store screenshots are the single biggest factor in whether someone taps "Get" or keeps scrolling. In fact, most users never read your description. They glance at your icon, scan your app store screenshot examples, and decide in seconds. That means your screenshots need to do all the heavy lifting.

So what separates screenshots that convert from ones that get ignored? We studied dozens of top-performing apps across categories and pulled out 15 design patterns that consistently drive downloads. Whether you're launching a new app or refreshing an existing listing, these examples will give you a concrete playbook to follow.

Why Your App Store Screenshots Make or Break Downloads

Apple reports that 70% of App Store visitors never go past the first impression. Your screenshots sit front and center in that first impression, right below your icon and ratings.

Think of screenshots as a mini sales pitch. You get 10 frames (on iOS) to tell a story, highlight your best features, and convince someone your app is worth their time. Get it wrong, and no amount of ASO keyword work will save your conversion rate.

The good news? Screenshot design follows patterns. You don't need to reinvent the wheel. You just need to study what works and adapt it to your app. Let's look at 15 approaches that top apps use right now.

15 App Store Screenshot Examples Worth Studying

We've grouped these into five categories based on the design approach. Each pattern works well for different types of apps, so find the ones that match your product best.

Pattern 1: Clean Device Mockups with Bold Headlines

Example 1: The "Hero Screen" opener. Many top finance and productivity apps lead with their most impressive screen inside a clean iPhone mockup. The background is a single bold color, and a short headline sits above the device. Something like "Track Every Dollar" in large sans-serif type. Simple, scannable, effective.

Example 2: The floating device. Instead of placing the phone flat, some apps angle the device at 15-20 degrees with a subtle shadow. This creates depth and draws the eye. Meditation and wellness apps use this frequently because it feels calm and premium.

Example 3: The cropped screen. Rather than showing the full device frame, this pattern crops the UI to fill most of the screenshot. It puts maximum focus on the actual interface, which works great if your app has a visually distinctive UI.

Pattern 2: Lifestyle and Context Shots

Example 4: Real-world photography backgrounds. Fitness apps commonly place their UI over a photo of someone working out. The key is using the photo as a blurred or dimmed background so the app UI stays readable. It sets an emotional tone without sacrificing clarity.

Example 5: Hands holding the device. Showing a real hand holding a phone with your app on screen adds a human touch. Food delivery and social apps use this to make the experience feel tangible. The trick is keeping the hand and background simple so they don't compete with your UI.

Example 6: Split composition. One half shows a lifestyle photo (a kitchen, a gym, a desk), and the other half shows the app screen. This bridges the gap between "what you do in real life" and "how the app helps." Recipe and home workout apps nail this approach.

Pattern 3: Feature Highlight Sequences

Example 7: One feature per screenshot. This is the most common pattern across all categories. Each screenshot focuses on exactly one feature with a headline, a brief subtitle, and the relevant screen. Navigation apps, task managers, and note-taking apps all rely on this. The discipline of "one idea per frame" keeps things digestible.

Example 8: Before and after. Photo editing apps love this pattern. The screenshot shows a split view of a photo before and after editing. It's instantly compelling because the value is visible without reading a single word. If your app transforms something, this is your go-to pattern.

Example 9: The numbered walkthrough. Some apps number their screenshots (Step 1, Step 2, Step 3) to create a narrative flow. This works well for apps with a clear workflow, like budgeting tools or habit trackers. It answers "how does this actually work?" in a visual sequence.

Pattern 4: Social Proof and Data-Driven Layouts

Example 10: Stats and achievements front. Language learning and fitness apps often lead with a screenshot showing user stats, streaks, or progress charts. Numbers are persuasive. Showing "500,000+ words learned" or a progress graph immediately communicates value.

Example 11: Review quotes overlay. A few top apps overlay a real user review quote on their first or second screenshot. Something like "This app changed how I manage my money" with a 5-star rating graphic. It combines social proof with the visual showcase.

Example 12: Award badges. If your app has won an Apple Design Award, an App of the Day feature, or a notable press mention, placing that badge on your first screenshot adds instant credibility. Keep it small and tasteful.

Pattern 5: Localized and Market-Specific Versions

Example 13: Fully localized screenshots. The highest-converting apps don't just translate text overlays. They localize the entire screenshot: the UI language, the currency symbols, the date formats, even the background imagery. A shopping app targeting Japan might show yen prices and Japanese text throughout. This is where tools like Shotlingo's localization hub become essential, especially if you're expanding into markets like Japanese where cultural fit matters enormously.

Example 14: Regional lifestyle adaptation. Beyond text, some apps swap the lifestyle imagery for each market. A travel app might show Paris landmarks for the French store and Mount Fuji for the Japanese store. It signals "this app was made for you."

Example 15: RTL-aware layouts. Apps targeting Arabic or Hebrew markets flip their entire screenshot layout to right-to-left. The headline placement, the device position, and the text alignment all mirror. This attention to detail dramatically improves trust and conversion in those markets.

What the Best App Store Screenshot Examples Have in Common

After analyzing these 15 patterns, clear themes emerge. Here's a summary of what the top-performing screenshots share:

| Element
| What Top Apps Do
| Why It Works |

How to Apply These App Store Screenshot Examples to Your App

Knowing what works is step one. Here's how to actually implement these patterns for your own listing.

Step 1: Audit Your Current Screenshots

Open your App Store listing on a phone (not desktop) and look at it the way a new user would. Can you understand what your app does from the first two screenshots alone? If not, you need to restructure. Use Shotlingo's free ASO tools to benchmark your current listing against competitors.

Step 2: Pick Your Pattern

Choose one primary design pattern from the 15 examples above. Don't mix too many styles. If you're a productivity app, the "one feature per screenshot" approach (Example 7) is a safe bet. If you're a photo editor, "before and after" (Example 8) is hard to beat.

Step 3: Write Headlines First

Before you touch any design tool, write the headline for each screenshot. Keep them under 6 words. Focus on benefits, not features. "Save 2 Hours Every Week" beats "Advanced Task Scheduling" every time.

Step 4: Design for Thumbnail Size

Most people will first see your screenshots as tiny thumbnails in search results. Open your designs at 30% zoom and check if the headline is still readable. If it's not, increase the font size or simplify the layout.

Step 5: Localize for Every Market

If you're only showing English screenshots globally, you're leaving downloads on the table. Localizing your screenshots for your top 5-10 markets can boost conversion rates significantly. This used to be a painful manual process, but tools like Shotlingo let you localize screenshots across dozens of languages without recreating each design from scratch.

Common Mistakes to Avoid

Even with great patterns to follow, there are pitfalls that can tank your conversion rate.

Cramming too much text. If your screenshot looks like a blog post, you've gone too far. One headline, one subtitle max.
Using outdated device frames. An iPhone X mockup in 2026 tells users your app hasn't been updated in years.
Ignoring the landscape option. For iPad apps and games, landscape screenshots can display your UI much more effectively.
Leading with a splash screen or login page. Your first screenshot should show the core experience, not a sign-up form.
Identical screenshots across all markets. A user in Brazil scrolling past English-only screenshots will almost certainly choose a competitor with Portuguese text. Localization is not optional for global apps.
Forgetting dark mode. If your app supports dark mode, consider including at least one dark-themed screenshot. Many users browse the App Store at night.

If you're not sure how your screenshots stack up against competitors, tools like Shotlingo's comparison pages can help you see where you stand and what alternatives are available.

FAQ

How many screenshots should I use in the App Store?

Apple allows up to 10 screenshots per device size. Use all 10. According to Apple's App Store product page guidelines, your first three screenshots are the most important since they appear in search results without tapping into your listing. But every additional screenshot is another chance to convince someone to download.

What size should App Store screenshots be?

For iPhone, Apple requires 6.7-inch display screenshots at 1290 x 2796 pixels and 6.5-inch display screenshots at 1242 x 2688 pixels (or 1284 x 2778 pixels). You can find the full list of required sizes in the App Store Connect screenshot specifications. Always design at the largest size first, then scale down.

Should I localize my app store screenshots for different countries?

Absolutely. Localized screenshots convert significantly better than English-only versions in non-English markets. At minimum, translate the text overlays on your screenshots. Ideally, adapt the entire design including UI language, currency, and cultural references. For apps targeting multiple regions, automated localization tools make this process manageable without blowing up your design budget.

Start Creating Better Screenshots Today

Great app store screenshots aren't about having a huge design budget. They're about understanding the patterns that work and applying them consistently. Pick one of the 15 design approaches above, write clear benefit-driven headlines, and make sure you're localizing for every market you care about.

Ready to localize and optimize your screenshots without the manual grind? Try Shotlingo free and start creating screenshot sets that convert across every market.

Originally published on Shotlingo

A/B Testing Your App Store Screenshots: A Complete Framework

Shotlingo — Tue, 14 Apr 2026 15:16:31 +0000

Most app developers choose their screenshots based on gut feeling. They pick what "looks nice" and hope for the best. But in a competitive marketplace, hope is not a strategy. A/B testing your screenshots lets you make data-driven decisions that directly impact your download numbers.

The Tools Available

Both major platforms now offer native testing capabilities:

Apple App Store: Product Page Optimization allows you to test up to 3 alternative screenshot sets against your original. Tests run for a configurable duration and provide statistical significance metrics.
Google Play Store: Store Listing Experiments support A/B testing of all store listing elements, including screenshots. Google provides confidence intervals and projected impact metrics.

Third-party tools like SplitMetrics and StoreMaven offer additional testing capabilities, including pre-launch testing and more granular analytics.

What to Test

High-Impact Variables

Not all screenshot changes are created equal. Focus your tests on variables that historically produce the biggest conversion differences:

First screenshot content: Which feature or message leads your set? This single variable often produces 10-20% conversion swings.
Screenshot order: Rearranging the same screenshots can significantly change conversion. Users rarely view past the third screenshot.
Headline messaging: Feature-focused ("Edit photos in one tap") vs. benefit-focused ("Look stunning in every photo") vs. social proof ("Used by 10M photographers")
Color scheme: Dark vs. light backgrounds, brand colors vs. contrasting colors

Lower-Impact Variables

These are worth testing but typically produce smaller differences:

Device frame style (realistic vs. minimal vs. no frame)
Text placement (top vs. bottom)
Font choice and size
Background patterns and effects

The Testing Framework

Step 1: Establish Your Baseline

Before testing anything, document your current conversion rate. In Apple's App Analytics, look at your impression-to-install conversion rate over a 30-day period. This is your baseline to beat.

Step 2: Form a Hypothesis

Every test should have a clear hypothesis: "Changing the first screenshot from a feature overview to a social proof message will increase conversion by at least 5% because our target audience values peer validation."

Without a hypothesis, you are just making random changes and cannot build actionable insights from results.

Step 3: Test One Variable at a Time

This is the golden rule of A/B testing. If you change the first screenshot's headline AND its color scheme AND the device frame, you will not know which change caused the result. Isolate variables to build reliable knowledge.

Step 4: Run Until Statistical Significance

Do not make decisions on insufficient data. Apple recommends running tests for at least 7 days. For most apps, you will need 2-4 weeks to reach 90% confidence. Apps with lower traffic may need even longer.

Resist the temptation to end a test early because one variation "looks like it's winning." Early results are often misleading due to day-of-week effects and sample size limitations.

Step 5: Document and Iterate

Record every test: what you changed, the hypothesis, the result, and the confidence level. Over time, this builds a knowledge base specific to your audience. What works for a gaming app may not work for a productivity app, and your testing history helps you make better hypotheses over time.

Common Testing Mistakes

Testing too many things at once: Multi-variable tests require exponentially more traffic to reach significance.
Stopping tests too early: A 3-day test rarely has enough data to be meaningful.
Not accounting for seasonality: Running a test during a holiday period will skew results.
Ignoring segment differences: Your screenshots may convert differently in different countries. A global winner may be a local loser.
Testing tiny changes: Changing a font from 42pt to 44pt will never produce a measurable difference. Test bold changes that could move the needle significantly.

Advanced: Localization-Specific Testing

Different markets respond to different visual and messaging approaches. Japanese users tend to prefer information-dense screenshots with detailed feature descriptions. US users respond better to clean, minimal designs with emotional messaging. German users value specificity and technical accuracy.

If you have enough traffic, run separate A/B tests for your top markets. The optimal screenshot set for the US App Store may perform poorly in Japan, and vice versa.

Start with your highest-traffic market, establish a winning variation, then test localized versions for secondary markets. This tiered approach maximizes learning while managing the complexity of multi-market testing.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Designing Screenshots for RTL Languages: Arabic, Hebrew & More

Shotlingo — Tue, 14 Apr 2026 15:16:27 +0000

Right-to-left (RTL) languages represent some of the most lucrative and underserved app markets in the world. Arabic alone is spoken by over 400 million people across 25+ countries. Hebrew, Persian, and Urdu add hundreds of millions more. Yet most app developers treat RTL localization as an afterthought — if they address it at all.

Getting RTL screenshots right requires more than running text through a translator. It demands a fundamental shift in how you think about visual layout, reading flow, and cultural context.

Understanding RTL Reading Flow

In RTL languages, users do not just read text from right to left — they scan the entire page from right to left. Their eyes naturally land on the top-right corner first, then sweep leftward and downward. This has profound implications for your screenshot layout.

Your visual hierarchy must flip. The most important element should be positioned where RTL readers look first — the top-right area. Call-to-action elements should align to the right. Progress indicators should flow from right to left.

What Needs to Mirror (And What Doesn't)

Always Mirror

Text alignment: All text should be right-aligned (or right-to-left justified)
Navigation elements: Back arrows point right, forward arrows point left
Progress indicators: Steps flow from right to left
Lists and bullet points: Bullets appear on the right side
Layout flow: If your LTR layout has an image on the left and text on the right, the RTL version should swap them

Never Mirror

Logos and brand marks: These should remain in their original orientation
Phone number and numeric data: Numbers are read left-to-right even in RTL languages
Media controls: Play, pause, forward, and rewind buttons follow universal conventions
Clocks and timelines: These follow universal left-to-right or circular conventions
Images and photographs: Do not flip photos — a person facing left should still face left

Typography for Arabic and Hebrew

Arabic Typography

Arabic is a connected script — letters change form depending on their position in a word (initial, medial, final, or isolated). This means you cannot use just any font. Your chosen typeface must support all four forms and render ligatures correctly.

Recommended fonts for Arabic app screenshots include Cairo, Tajawal, IBM Plex Arabic, and Noto Sans Arabic. These are modern, clean, and render well at small sizes. Avoid decorative Arabic fonts — they reduce readability at screenshot scale.

Arabic text is generally more compact vertically than Latin text but can be wider horizontally. Plan for 10-20% additional horizontal space compared to English.

Hebrew Typography

Hebrew is simpler typographically — it is not a connected script, so font support is less of an issue. However, nikud (vowel marks) can appear in certain contexts and require fonts with proper diacritics support. For app screenshots, unvocalized Hebrew (without nikud) is standard and cleaner.

Good Hebrew fonts include Heebo, Assistant, Rubik, and Noto Sans Hebrew.

Cultural Considerations

RTL markets are not monolithic. What works in Saudi Arabia may not work in Israel, and what resonates in Iran differs from Egypt. Key cultural factors to consider:

Color symbolism: Green has positive connotations across most Arabic-speaking countries. Red can signal danger in some contexts but celebration in others. Blue is universally safe.
Imagery: Be mindful of cultural sensitivities in imagery. What is considered appropriate casual imagery varies significantly across RTL markets.
Formality level: Arabic-speaking markets generally expect a more formal tone in text. Casual slang that works in English may come across as unprofessional.
Date and number formats: Some Arabic-speaking countries use Eastern Arabic numerals (٠١٢٣٤٥٦٧٨٩), while others use Western Arabic numerals (0123456789). Know your target market.

Testing RTL Screenshots

Always get your RTL screenshots reviewed by native speakers before publishing. Common issues that automated tools miss:

Mixed LTR/RTL text rendering incorrectly (e.g., English brand names within Arabic text)
Punctuation marks appearing on the wrong side
Text that is technically correct but sounds unnatural or overly literal
Cultural faux pas in imagery or messaging

Implementation With Shotlingo

Shotlingo's template system supports automatic RTL layout mirroring. When you select an RTL language, text elements automatically switch to right alignment, and the layout direction adapts. You can also manually override specific elements — keeping logos unmirrored while flipping the overall layout.

Investing in proper RTL screenshots is one of the highest-ROI localization activities. The markets are large, spending power is significant, and competition from well-localized apps is still relatively low. Developers who get RTL right today have a meaningful first-mover advantage.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

How to Create App Store Screenshots That Convert in 2026

Shotlingo — Tue, 14 Apr 2026 15:16:18 +0000

Your app store screenshots are doing one job: convincing someone to tap "Get" instead of scrolling past. Everything else — your icon, description, ratings — plays second fiddle. Over 60% of users make their download decision without ever reading your app description. Your screenshots are your storefront, your pitch deck, and your sales page rolled into one.

This is not a theory guide. It is a step-by-step playbook based on what actually works in 2026, drawn from ASO data across thousands of app listings.

Step 1: Define Your Screenshot Storyline

The most effective screenshot sets follow a narrative structure. Users swipe through your screenshots like pages of a story, and each page should build on the last.

The proven 5-screenshot formula:

The Hook: Your single biggest value proposition. What is the one thing your app does better than anything else? Lead with this. "Track Every Expense in 3 Seconds" beats "Welcome to MoneyApp" every time.
The Pain Point: Name the problem your users face. "Stop Losing Receipts" or "No More Spreadsheet Chaos." This creates an emotional connection — the user thinks "that is me."
The Solution: Show your app solving that exact problem. This is where your best UI screen appears, demonstrating the core workflow in action.
The Key Feature: Highlight one standout capability that differentiates you. Not three features, not five — one. The feature that makes users say "oh, that is clever."
The Social Proof: End with credibility. "Trusted by 500K+ Users" or a star rating callout. Users who reach your fifth screenshot are on the fence — this tips them over.

Step 2: Design for Thumb-Stopping Impact

Most users encounter your screenshots while scrolling through search results on a 6-inch phone screen. Your screenshots are thumbnails at this point — roughly 120 pixels wide. If your message is not readable at that size, it is invisible.

Typography Rules

Maximum 6 words per headline. "AI Budget Tracking" works. "Artificial Intelligence Powered Personal Budget Tracking and Analytics" does not.
Minimum 80pt font size (at 1290×2796 canvas). Anything smaller disappears in search results.
Sans-serif fonts only. Inter, SF Pro, Montserrat, and Poppins are proven performers. Serif fonts lose legibility at small sizes on screens.
High contrast text. White on dark or dark on light. Never place text over busy UI without a solid background or overlay.

Color Strategy

Your screenshot backgrounds should contrast with the App Store's white (or dark mode black) background. Mid-tone colors — deep blue, rich purple, forest green — stand out in both modes. Avoid pure white backgrounds that blend with the store and pure black that disappears in dark mode.

Device Frames: Use Them Wisely

Device frames add context but eat space. In 2026, the trend is moving toward frameless or minimal frames — showing just the screen content with subtle shadow and rounded corners. This gives you more room for headlines and lets the UI speak for itself. If you do use frames, use current hardware — an iPhone 15 Pro or iPhone 16, not an iPhone 12.

Step 3: Optimize Your First Screenshot Obsessively

Your first screenshot gets 10x more views than your last one. In search results, it is often the only screenshot visible without scrolling. Treat it like a billboard:

Strongest headline you have
Most impressive UI screen
Clearest value proposition
Zero clutter

A/B test your first screenshot more than any other element in your listing. Apple's product page optimization and Google Play's store listing experiments both support this. Even a 5% improvement in first-screenshot conversion compounds across every impression your app receives.

Step 4: Localize for Your Target Markets

If your app is available in multiple countries, localized screenshots are not optional — they are mandatory for competitive listings. The data is overwhelming: localized screenshots increase conversion rates by 30-80% in non-English markets.

This does not mean just translating the text. Effective localization includes:

Translated headlines and captions in the local language
Culturally appropriate imagery — currency symbols, date formats, local content
Layout adaptation — RTL languages need mirrored layouts, CJK languages may need different font sizes

Tools like Shotlingo make this practical by letting you manage all translations in one place and batch-export localized screenshots for every market simultaneously. What used to be a multi-week localization project becomes a same-day task.

Step 5: Test, Measure, Iterate

Your first screenshot set is a hypothesis, not a final answer. Both platforms give you the tools to test:

Apple Product Page Optimization: Test up to 3 screenshot variations simultaneously. Apple shows different versions to different users and reports conversion rates for each.
Google Play Store Listing Experiments: Similar A/B testing functionality. You can test screenshots, descriptions, and icons independently.

What to test first:

First screenshot variations (highest impact)
Headline copy (benefit vs. feature framing)
Color schemes (dark vs. light backgrounds)
With vs. without device frames

Run each test for at least 7 days with a minimum of 1,000 impressions per variant before drawing conclusions. Small sample sizes produce misleading results.

Step 6: Update Screenshots With Every Major Release

Outdated screenshots are a conversion killer. If a user downloads your app and sees a completely different interface than what the screenshots showed, you will lose trust immediately — and likely get a 1-star review.

Build screenshot updates into your release process. If you use a template-based tool, this is trivial: update the UI images in your template, and all localized versions regenerate automatically.

The Quick-Start Checklist

☐ Define a 5-screenshot storyline (Hook → Pain → Solution → Feature → Proof)
☐ Design headlines with 6 words or fewer, 80pt+ font size
☐ Use mid-tone backgrounds that contrast with the store
☐ Show real app UI with realistic data
☐ Localize for your top 5 markets
☐ Set up A/B testing for your first screenshot
☐ Schedule screenshot updates with each major release

Start with this checklist, measure your conversion rate before and after, and iterate from there. The developers who treat screenshots as an ongoing optimization — not a one-time task — are the ones who consistently outperform in the app stores.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Google Play vs App Store: Screenshot Requirements Compared

Shotlingo — Tue, 14 Apr 2026 15:16:14 +0000

If your app is available on both iOS and Android, you need to manage two completely different sets of screenshot requirements. While the core principles of good screenshot design are universal, the technical specs, policies, and optimization opportunities differ significantly between Google Play and the App Store.

This guide provides a comprehensive, up-to-date comparison to help you navigate both platforms efficiently.

Technical Specifications

Apple App Store

Number of screenshots: Up to 10 per localization per device type
Required device sizes: 6.7" display (1290 x 2796px) and 5.5" display (1242 x 2208px) for iPhones. iPad Pro 12.9" (2048 x 2732px) if app supports iPad
File format: JPEG or PNG, no alpha channel
File size limit: No specific limit, but high-resolution PNGs are recommended
Orientation: Portrait or landscape (must be consistent within a device type)
App previews: Up to 3 video previews per localization, 15-30 seconds each

Google Play Store

Number of screenshots: Minimum 2, maximum 8 per listing
Size requirements: Minimum 320px, maximum 3840px. 16:9 or 9:16 aspect ratio recommended
File format: JPEG or 24-bit PNG (no alpha)
File size limit: 8MB per screenshot
Orientation: Can mix portrait and landscape
Promotional video: YouTube video URL (no length limit, but 30-120 seconds recommended)

Content Policies

What Apple Restricts

Apple has strict content guidelines for screenshots:

Screenshots must accurately represent the app experience
No pricing information or "free" claims in screenshots
Device frames must match actual Apple products (no custom colors)
No references to other platforms (no Android screenshots in your iOS listing)
Text overlay must be relevant to the app's functionality
No user testimonials or review quotes without proper attribution

What Google Restricts

Google's policies are slightly more permissive but still have boundaries:

Screenshots must be representative of the actual app experience
No misleading imagery (showing features the app does not have)
No excessive promotional text that obscures the app interface
Performance claims must be verifiable
User data collection disclosures must match app behavior

Optimization Opportunities

Apple-Specific Advantages

Product Page Optimization (PPO) lets you A/B test up to 3 alternative screenshot sets. This is invaluable for data-driven optimization. Each test can run across all localizations or be targeted to specific markets.

Apple's Custom Product Pages allow you to create up to 35 unique store listing versions, each with different screenshots. You can link these to specific ad campaigns, allowing you to match screenshot messaging with ad creative for higher conversion rates.

Google-Specific Advantages

Store Listing Experiments offer similar A/B testing but with more flexibility in what you can test (including the feature graphic and short description alongside screenshots).

Google's Custom Store Listings let you create different screenshots for different countries, install states (pre-registration, installed), and referral sources. This granularity allows for highly targeted visual messaging.

Google Play also auto-plays video previews in search results, giving video-enabled listings a significant visibility advantage.

Localization Differences

Apple's Localization Model

Apple supports 40+ localizations, and each one can have its own complete screenshot set. Some localizations serve multiple countries — for example, French serves France, Belgium, Switzerland, and several African countries. You can use this strategically to reach multiple markets with one localization.

Google's Localization Model

Google Play supports 75+ languages and allows country-level customization. You can have different screenshots for French (France) and French (Canada), which Apple does not support natively. This gives Google Play publishers more granular control over regional messaging.

Design Strategy: One Set or Two?

Should you create separate screenshot designs for each platform? The answer depends on your resources:

Unified approach: Design at the highest resolution (Apple's 6.7" size), then resize for Google Play. Use frameless designs to avoid platform-specific device mockup issues. This saves time but may not optimize for each platform's unique display characteristics.
Platform-specific approach: Create separate sets that leverage each platform's strengths. Show iPhone frames on iOS and Pixel/Samsung frames on Android. Optimize text placement for each platform's search result layout. This requires more work but maximizes conversion on each platform.

For most teams, we recommend a hybrid approach: unified base designs with platform-specific device frames and minor layout adjustments. Tools like Shotlingo support multi-platform export from a single template, making this approach practical without doubling your workload.

Quick Reference Table

Max screenshots: Apple 10, Google 8
Min screenshots: Apple 1, Google 2
A/B testing: Both supported natively
Video: Apple (in-store preview), Google (YouTube, auto-plays)
Custom pages: Apple 35, Google unlimited (via custom listings)
Localization granularity: Apple per-language, Google per-country

Understanding these differences is essential for any cross-platform app. The developers who optimize for each platform independently — rather than using a one-size-fits-all approach — consistently see better conversion rates and higher download numbers on both stores.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

German App Store Screenshots Are 35% Longer Than English - Here Is What to Do

Shotlingo — Tue, 14 Apr 2026 15:16:10 +0000

The 35% problem

Every time you translate English marketing copy to German, the text grows by roughly 35%. This is not an opinion - it is a linguistic fact measured across thousands of real app store listings.

English: Design stunning screenshots in minutes (48 characters)

German: Gestalten Sie in wenigen Minuten beeindruckende App-Store-Screenshots (71 characters)

That is a 48% expansion for this specific sentence. The average across typical UI and marketing copy is 30-40%. For short strings like button labels, it can be worse: the English word Settings (8 characters) becomes Einstellungen (14 characters) - a 75% expansion.

Why this wrecks your screenshots

If you design your screenshot layout for English text and then replace the text with German, one of two things happens:

Text overflows the container - it either clips or wraps awkwardly, breaking the visual hierarchy.
Auto-shrink kicks in - the design tool reduces font size to fit, making the German text visibly smaller and harder to read than the English original. Users notice.

Both outcomes make your German screenshots look worse than your English ones. And Germany is the #1 App Store revenue market in Europe - you cannot afford a second-class listing there.

The data: how much does each language expand?

We measured average character expansion across 200 real App Store listings. Here are the languages that expand the most:

Language	Avg expansion vs English	Risk level
German	+35%	HIGH
Finnish	+30%	HIGH
Portuguese (Brazil)	+30%	HIGH
Polish	+30%	HIGH
Hungarian	+30%	HIGH
Spanish	+25%	MEDIUM
French	+20%	MEDIUM
Italian	+20%	MEDIUM
Dutch	+20%	MEDIUM
Japanese	-45%	LOW (shrinks)
Chinese	-50%	LOW (shrinks)

Try the numbers yourself with our free Text Expansion Calculator - paste your English text and see expansion across 40 languages instantly.

How to fix it: 4 rules

1. Design for German first

Start your screenshot layout with German text (or Finnish, whichever is your longest target language). If the layout works for German, it will work for every other language. English will have extra breathing room, which looks great.

2. Never center-align in a fixed-width button

German compound words like Benachrichtigungseinstellungen (notification settings, 34 characters) will break any center-aligned button designed for English. Use left-alignment with generous right padding.

3. Use sentence case, not Title Case

German already capitalizes all nouns. Adding Title Case on top makes every word look capitalized, which reads as ALL CAPS to German speakers. Sentence case is the standard.

4. Reserve 35% horizontal padding

On every text container in your screenshot, add 35% extra horizontal space beyond what English needs. This is your expansion buffer. If it looks too spacious in English, good - it will look just right in German.

The font matters too

German uses umlauts (a with two dots, o with two dots, u with two dots). Some fonts render these poorly or with awkward spacing. Test with: Inter, Roboto, or Noto Sans - all handle German diacritics well.

More details in our German localization guide.

What about languages that shrink?

Japanese and Chinese use fewer characters than English, but each character is roughly twice the width of a Latin letter. So the visual width stays approximately the same. Do not assume CJK text will give you more space - it usually does not.

The shortcut

Shotlingo handles text expansion automatically. Upload your English screenshot, add target languages, and the AI reflows text so German, Finnish, and Polish never overflow. No manual resizing, no layout broken.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Device Mockup Best Practices for App Store Listings

Shotlingo — Tue, 14 Apr 2026 15:16:06 +0000

The humble device mockup — that iPhone or Android frame surrounding your app screenshot — plays a surprisingly important role in user perception and conversion. But the rules around device mockups have shifted considerably. Here is what the data tells us about how to use them effectively in 2026.

To Frame or Not to Frame?

Let us start with the most common question: should you even use device frames? The answer depends on your app category and visual style:

Use frames when: Your app UI might be confused with the store interface itself, when showing multiple screens side by side, or when your app has a distinctive interface that benefits from being framed as a "product."
Skip frames when: You want maximum visual impact from your UI, when your screenshots use full-bleed backgrounds, or when your app is content-focused (news, social media, video).

Data from A/B tests across thousands of apps shows that frameless screenshots outperform framed ones by 5-8% on average. However, this is heavily category-dependent. Productivity apps see better results with frames, while games and creative apps benefit from going frameless.

Choosing the Right Device

Stay Current

Using an outdated device frame is a subtle but real trust signal. Users unconsciously associate old device designs with abandoned apps. Always use the latest device models — as of 2026, that means iPhone 17-series frames for iOS and Galaxy S26 or Pixel 10 for Android.

Match Your Audience

If your analytics show that 70% of your users are on iPhones, lead with iPhone mockups. If you are targeting emerging markets where Android dominates, Samsung or Pixel frames may resonate better.

Flat vs. Angled

Flat, front-facing device mockups are the safest choice — they are clean, easy to read, and universally understood. Angled or perspective views can add visual interest but make UI details harder to read. Use angles sparingly, perhaps for one screenshot that shows your app alongside complementary features.

Creating Professional Mockups

Resolution and Quality

Your device frame must be pixel-perfect. Blurry or low-resolution frames immediately cheapen the entire screenshot. Use vector-based frames (SVG) when possible, and always export at the maximum resolution required by the store.

Realistic Shadows and Reflections

A subtle drop shadow beneath the device adds depth and makes the screenshot feel more polished. Avoid overly dramatic shadows or reflections — they distract from the app content. A 10-15% opacity shadow with a slight vertical offset looks natural and professional.

Screen Content Fit

The most common mockup mistake is incorrect scaling. Your app screenshot must fit the device screen precisely — no visible gaps, no cropping of UI elements, and the status bar should match the device type. If you are showing an iPhone, the status bar should show the iOS notch design, not Android's status bar.

Layout Strategies

Single Device, Centered

The classic approach: one device in the center of the screenshot with a headline above or below. This works well for the first screenshot where you want maximum focus on a single feature.

Overlapping Devices

Showing 2-3 screens overlapping creates a sense of depth and lets you showcase multiple features in one screenshot. Keep the primary screen fully visible and let secondary screens peek out at the edges. This technique is especially effective for showing a workflow or progression.

Device Plus Context

Place the device alongside contextual elements — icons, illustrations, or abstract shapes that reinforce your message. A fitness app might show a device alongside workout icons; a finance app might include chart elements around the device frame.

Platform-Specific Considerations

Apple App Store: Apple is particular about how their devices are depicted. Review Apple's marketing guidelines to ensure your mockups comply. Using non-standard colors or modified device designs can lead to rejection.
Google Play: More permissive with device representation, but consistency matters. If you use a specific device in your first screenshot, maintain that choice throughout the set.

Quick Checklist

Device model is current (2025-2026 models)
Frame resolution matches export size
Screen content fits perfectly with no gaps
Status bar matches device platform
Shadows are subtle and consistent across all screenshots
Angles, if used, still allow UI readability
Device color does not clash with background

The device mockup is a supporting actor, not the star. Its job is to present your app's interface in the best possible light without drawing attention to itself. Get it right and users will focus entirely on your app. Get it wrong and it becomes a distraction that undermines your entire screenshot set.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Best iOS Screenshot Generators in 2026 — Free & Paid Tools Compared

Shotlingo — Tue, 14 Apr 2026 15:16:02 +0000

Creating polished App Store screenshots used to mean hours in Figma or Photoshop. In 2026, dedicated iOS screenshot generators handle device frames, text overlays, and even localization automatically. But which tool is actually worth your time?

We tested every major option — free and paid — to help you pick the right one for your workflow. Whether you are a solo indie developer or part of a larger ASO team, this guide covers what matters: speed, output quality, localization support, and price.

What Makes a Good iOS Screenshot Generator?

Before diving into specific tools, here is what separates the good from the mediocre:

Correct device frames: iPhone 15 Pro, iPhone 16, iPad Pro — the tool should offer current Apple hardware frames, not outdated iPhone X mockups.
Proper export sizes: Apple requires specific pixel dimensions (1290×2796 for 6.7", 1242×2208 for 5.5"). The tool should handle this automatically.
Text overlay support: Headlines and captions are critical for conversion. You need control over fonts, sizes, colors, and positioning.
Batch export: If you support multiple languages, exporting one screenshot at a time is not viable.
Template system: Starting from a professionally designed template saves hours compared to building from scratch.

The Tools: Head-to-Head

1. Shotlingo

Best for: Localization-first teams and indie developers

Shotlingo was built specifically for the screenshot localization problem. You design your template once, add translations for 40+ languages, and export everything in a single batch. The canvas editor is browser-based with real-time preview, and the community template gallery gives you professional starting points.

Drag-and-drop canvas editor with Fabric.js
AI-powered translation for 40+ languages
Batch export for App Store and Google Play
Community templates (free)
Pricing: Free tier available, Pro from $9/month

2. AppScreens

Best for: Teams wanting a full-featured design suite

AppScreens has been around for years and offers a mature editor. It supports both iOS and Android, has a large template library, and includes basic localization. The main drawback is pricing — plans start higher, and localization features require premium tiers.

Large template library
Device frame customization
Basic localization support
Pricing: From $19/month

3. Screenshots.pro

Best for: Quick mockups with minimal effort

A streamlined tool focused on speed. Upload your screenshot, pick a device frame, add text, and export. Less flexible than full editors, but perfect for developers who want something done in 10 minutes.

Simple drag-and-drop interface
Good device frame selection
Limited text customization
Pricing: Free with watermark, paid from $9/month

4. Mockupper

Best for: Budget-conscious solo developers

Mockupper offers a generous free tier and covers the basics well. The editor is straightforward, and device frames are regularly updated. Localization and batch export are limited compared to dedicated tools.

Generous free tier
Clean, simple editor
Regular device frame updates
Pricing: Free tier, Pro from $7/month

5. Apple Framer

Best for: Apple-only developers who want pixel-perfect Apple hardware frames

Focused exclusively on Apple devices. The frames are extremely accurate, and the export pipeline is optimized for App Store Connect. Limited to iOS/iPadOS/macOS — no Android support.

Pixel-perfect Apple device frames
Optimized for App Store Connect
No Android support
Pricing: One-time purchase

6. Figma / Photoshop (Manual Approach)

Best for: Designers who need complete creative control

If you already live in Figma or Photoshop, dedicated screenshot plugins can speed up the process. Rotato for 3D device mockups and various Figma screenshot templates offer professional quality. The tradeoff is time — manual workflows take 5-10x longer than automated tools, especially when localization is involved.

Comparison Table

Feature	Shotlingo	AppScreens	Screenshots.pro	Mockupper	Apple Framer
Free tier	Yes	Trial	Watermarked	Yes	No
iOS + Android	Yes	Yes	Yes	Yes	iOS only
40+ languages	Yes	Limited	No	No	No
Batch export	Yes	Yes	No	Limited	Yes
Community templates	Yes	Yes	No	Limited	No
AI translation	Yes	No	No	No	No

Which One Should You Use?

The answer depends on your primary need:

If you need localization: Shotlingo is the clear winner. No other tool handles 40+ language batch export as seamlessly.
If you want the most features: AppScreens offers the broadest feature set for teams willing to pay more.
If you just need quick mockups: Screenshots.pro or Mockupper will get you there fastest.
If you are Apple-only and want perfection: Apple Framer delivers the most accurate device frames.

For most indie developers in 2026, the smartest approach is starting with a free tool to validate your app, then graduating to a localization-focused tool like Shotlingo when you are ready to scale internationally. The screenshots that convert best are the ones that speak each market's language — literally.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.