DEV Community: Shotlingo

Why German App Store Listings Need 30% More Vertical Space

Shotlingo — Thu, 21 May 2026 08:59:57 +0000

Why German App Store Listings Need 30% More Vertical Space (Data-Driven Analysis)

If you are localizing an app for Germany and reusing your English screenshot template pixel for pixel, your German app store listing is almost certainly broken in subtle but conversion-killing ways. Not in a catastrophic, refuse to upload kind of way, but in the slow, quiet way that costs you conversions: clipped headlines, awkward line wraps, captions that spill past the safe area on iPhone Pro Max, and feature lists that look squeezed compared to the English version.

We pulled real measurements from a few hundred translated UI strings, captions, and headlines and the pattern is consistent. The average German app store listing needs roughly 30 percent more vertical space than its English counterpart, and certain compound nouns blow that number out to 40 to 45 percent on their own. This post breaks down the data, shows you exactly where layouts fail, and gives you a playbook for designing screenshots that work in German on the first try.

The TL;DR

German text is on average 30 to 35 percent longer than the English equivalent. For app store screenshots and metadata specifically, that translates to: 30 percent more vertical space for headlines, 35 percent larger text containers in screenshots, 25 percent more padding because compound nouns cannot be hyphenated cleanly, and roughly 10 to 15 percent smaller font sizes when the layout cannot stretch. The 4000 character app description limit is rarely the problem. Tight screenshot captions are where almost every team fails.

German App Store Listing Text Expansion: The Numbers

Text expansion is well documented by both Apple's localization guidance and Google's localization style guide, but neither quantifies what it means for screenshot design. Linguistic research from the W3C on text size in translation puts German between 10 and 35 percent longer than English depending on string length, with the kicker being that shorter strings expand more in relative terms. That is exactly the kind of string you find in screenshot captions and call-to-action buttons, which is exactly where most teams get burned.

Here is what real, measured expansion looks like for the kind of microcopy that lives on app store screenshots:

Save time becomes Zeit sparen: 10 characters vs 11. Roughly the same.
Get started becomes Loslegen: 11 vs 8. One of the rare cases German is shorter.
Download becomes Herunterladen: 8 vs 13. About 40 percent longer.
Settings becomes Einstellungen: 8 vs 13. About 60 percent longer.
Notifications becomes Benachrichtigungen: 13 vs 18. About 40 percent longer.
Privacy Settings becomes Datenschutzeinstellungen: 16 vs 24. About 43 percent longer, in a single compound noun.
Customize your experience becomes Personalisieren Sie Ihre Erfahrung: 26 vs 34. About 40 percent longer.

Notice the floor and the ceiling. Common verbs hover around parity. Anything involving a compound noun jumps 40 percent or more, and you cannot escape compound nouns in German because that is literally how the language builds vocabulary.

Where German App Store Listings Break

Text expansion is invisible in a spreadsheet. It becomes painful the moment you drop the translated string into your existing template. Across audits we have done, the failure points repeat in the same four places.

1. Screenshot headline area

Most English screenshot templates allocate two lines for the headline at the top of the canvas. A typical English headline like "Plan your week in seconds" fits on two lines at 120 to 140 px font size. The German version, "Planen Sie Ihre Woche in Sekunden," wraps to three lines at the same font size, eats into the device mockup below it, and looks visually heavier than the English original.

2. Caption strip under the headline

This is the worst offender. Captions are short, which is exactly the regime where German expands the most in percentage terms. "Notifications you control" becomes "Benachrichtigungen, die Sie steuern" and a tight two line caption becomes a wrappy three line caption that crowds the device.

3. Feature bullet lists inside the screenshot

If you have a screenshot showing three or four bullet features ("Sync everywhere", "Privacy first", "No ads"), the German equivalents add roughly 30 percent width per bullet. On 1242 px wide iPhone screenshots, that pushes bullets past the safe horizontal area unless you preemptively shrink the container.

4. App description preview on the listing page

The first two lines of your description are what users see before tapping "more." An 800 character English description becomes roughly 1100 characters in German, which sounds fine against the 4000 character limit, but the visible preview lines now show only one and a half sentences instead of the two and a half you had in English. You lose hook strength even though you are well under the limit.

The 7 Common German Words That Wreck Your Layout

If you only memorize one table from this post, make it this one. These are the seven words and phrases that appear in nearly every app store listing and that consistently break English-first layouts.

  | English 
  | German 
  | Character Delta 
  | Layout Risk 




  | Download 
  | Herunterladen 
  | +62% 
  | Breaks CTA buttons 


  | Settings 
  | Einstellungen 
  | +62% 
  | Breaks tab bar labels and section headers 


  | Notifications 
  | Benachrichtigungen 
  | +38% 
  | Wraps screenshot captions 


  | Privacy Settings 
  | Datenschutzeinstellungen 
  | +50% 
  | Single compound noun, no wrap point 


  | Customize your experience 
  | Personalisieren Sie Ihre Erfahrung 
  | +31% 
  | Three line headlines instead of two 


  | Account 
  | Benutzerkonto 
  | +86% 
  | Menu labels overflow 


  | Subscribe 
  | Abonnieren 
  | +11% 
  | CTA buttons get tight

Two patterns to take away. First, compound nouns like Datenschutzeinstellungen and Benutzerkonto cannot be soft hyphenated nicely without manual &shy; hints. Second, the percentage delta is highest exactly where you can least afford it: buttons, tab bar labels, and short captions.

How to Design German App Store Listings Right

The fix is not to translate and hope. It is to design the German version as a first class layout with its own type scale and its own safe areas. Five rules will get you 90 percent of the way there.

1. Reserve 30 to 35 percent more vertical space for the headline area

If your English template uses a 280 px tall headline zone, the German version should plan for 370 to 400 px. Either move the device mockup down or shrink it slightly. Do not compress the headline font.

2. Drop headline font size by 10 to 15 percent

When the headline still does not fit even with the extra vertical space, the next lever is font size. Going from 140 px to 120 px is usually enough and is barely noticeable against the device, which already dominates the visual hierarchy.

3. Add 25 percent more horizontal padding around captions

Compound nouns will not break cleanly. Give them room or they will look squeezed against the edges. This is more forgiving than trying to find clean wrap points inside a 24 character compound.

4. Use `&shy;` soft hyphens for the worst offenders

For words like Datenschutz&shy;einstellungen, a soft hyphen lets the rendering engine break the word at a semantically clean point. This is what native German design systems do and it should be in your screenshot template too.

5. Re-check on iPhone SE width

iPhone SE is the narrowest active iPhone screenshot size. If your German layout works at SE width, it will work everywhere. If you only test on Pro Max, you will ship clipping you cannot see until users start complaining.

What Tools to Use

You do not have to eyeball this. A few tools make a huge difference.

A text expansion calculator to predict the German length of any English string before you commit to a layout. This is the single highest leverage tool when planning a German layout.
The Shotlingo German screenshot localization guide, which has the specific font sizes, padding values, and safe areas we use for German.
The broader localization hub for everything beyond German, including French, Spanish, and Japanese, each of which has its own expansion profile.

If you want the full picture on screenshot design beyond localization, read our pillar on what ASO is in 2026 and the companion piece on app store screenshot mistakes to avoid, both of which assume English first but cover the structural principles every German layout builds on.

FAQ

How much longer is German than English, on average?

Between 30 and 35 percent longer for typical UI and marketing copy, with short strings expanding more in percentage terms (40 percent plus) and long descriptive paragraphs expanding less (around 20 percent). This is consistent with W3C and Apple localization guidance.

Do I need a separate screenshot template for German?

You need separate layout values: more vertical space for the headline, smaller font sizes, more horizontal padding. You do not necessarily need a separate visual identity. The cleanest approach is a single template with a "language profile" that adjusts type scale and spacing for German automatically.

Can I just use a smaller font for German and keep everything else the same?

You can, but you will lose visual punch. The better approach is to combine a slightly smaller font (10 to 15 percent) with more reserved vertical space (30 percent) and more padding (25 percent). Doing only the font change makes the German version look weaker than the English original, which is the opposite of what you want in your second largest European market.

Localize Your App Store Listing the Right Way

German is the canary in the coal mine for localization. If your layout survives German, it will survive Finnish, Hungarian, and most of the long-tail European languages that expand even more. If it does not, you are leaving conversions on the table in one of the highest spending app markets in the world.

Shotlingo handles the layout math for you. Drop in your English screenshots, pick German, and the type scale, padding, and safe areas adjust automatically using the same data this post is built on. Create a free account and ship a German app store listing that actually fits.

Originally published on Shotlingo

Apple Product Page Optimization (PPO) Guide for 2026

Shotlingo — Mon, 18 May 2026 09:38:50 +0000

Apple Product Page Optimization (PPO) Guide for 2026

Apple Product Page Optimization is the single most underused growth lever on the App Store in 2026. It is free, it is native, and it uses real organic App Store traffic to tell you which creative actually converts. Yet most indie developers and even many mid-sized studios still rely on gut feeling for their icon and screenshots. This guide walks you through what Apple Product Page Optimization is, how it differs from Custom Product Pages, how to set up your first test in App Store Connect, how to read the results without fooling yourself, and the advanced tactics that ASO teams are using this year.

If you only have ten minutes, here is the short version: pick one variable (icon, screenshots, or app preview), test it against your default page in your top market, give it at least 30 days, and let Apple call the winner. Everything else in this guide is a refinement of that loop.

What is Apple Product Page Optimization?

Apple Product Page Optimization (often shortened to PPO) is Apple's native A/B testing feature inside App Store Connect. It launched with iOS 15 in December 2021 and has matured significantly by 2026. PPO lets you run up to three alternate "treatments" against your current default product page, with Apple randomly splitting organic App Store traffic across each variant and declaring a statistically significant winner.

The mechanics are simple. You create a test, choose which asset you want to experiment with, upload up to three new versions, and Apple handles the traffic split. Each treatment must go through App Review just like a regular submission, so plan for a 24 to 48 hour delay before your test goes live. Once live, the test runs for up to 90 days, although most healthy tests reach significance in 14 to 30 days.

PPO is fundamentally a conversion rate tool. It does not change your search ranking or your keyword indexing. It tells you, with real money on the line, which creative makes more visitors tap "Get." That is why PPO sits at the top of every serious App Store Optimization roadmap in 2026.

PPO vs CPP: Which One Do You Need?

One of the most common questions we get from new ASO managers is whether to invest in Apple Product Page Optimization or in Custom Product Pages (CPP). The honest answer is that they solve different problems and the best teams use both. Here is a side-by-side comparison.

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




  | Primary purpose 
  | A/B test your default page 
  | Create targeted pages for paid campaigns or audiences 


  | Traffic source 
  | Organic App Store traffic (random split) 
  | Driven by unique CPP URL you share 


  | Number of variants 
  | Up to 3 treatments plus control 
  | Up to 35 custom pages per app 


  | What you can change 
  | Icon, screenshots, app preview 
  | Screenshots, app preview, promotional text 


  | Winner declared by Apple? 
  | Yes, with statistical confidence 
  | No, you measure conversion via analytics 


  | Per-locale? 
  | Yes, one test per locale 
  | Yes, you can localize each CPP 


  | Best for 
  | Improving baseline organic conversion 
  | Matching paid ad creative to landing page

If you are running paid user acquisition or running influencer campaigns, you absolutely need CPPs. Read our complete guide to Apple Custom Product Pages and our CPP localization playbook for those use cases. If you want to systematically improve the page that ranks for your branded and category keywords, PPO is the right tool. Most teams should be running both in parallel.

What You Can and Cannot Test with Apple Product Page Optimization

Apple is deliberately restrictive about what PPO can touch. The framework is designed for visual creative testing only, not for repositioning your app. Here is the exact scope in 2026.

  | Asset 
  | Testable with PPO? 
  | Notes 




  | App icon 
  | Yes 
  | Requires icon to be present in app binary via alternate icons 


  | Screenshots 
  | Yes 
  | All sizes for the locale must be provided 


  | App preview video 
  | Yes 
  | Up to 3 previews per treatment 


  | App name 
  | No 
  | Use a CPP or a regular metadata update 


  | Subtitle 
  | No 
  | Cannot be A/B tested natively 


  | Description 
  | No 
  | Tested manually via release versioning 


  | Keywords 
  | No 
  | Keywords are not user-facing creative 


  | Price or IAP 
  | No 
  | Use server-side pricing experiments instead

The key implication is that Apple Product Page Optimization is a creative tool, not a positioning tool. If you want to test a new value proposition, you have to encode it visually into your screenshots or icon. This is exactly why localized screenshot quality matters so much. Our screenshot localization workflow gives you a head start by producing per-market screenshot sets you can drop straight into a PPO treatment.

How to Set Up a PPO Test in App Store Connect

Setting up your first Apple Product Page Optimization test takes about 20 minutes once your creative is ready. Here is the exact flow.

Step 1: Navigate to the right section

Open App Store Connect, select your app, click the App Store tab, then choose Product Page Optimization in the left sidebar. You will see a list of past and active tests.

Step 2: Create the test

Click Create Test and give it a descriptive name. We recommend a naming convention like 2026Q2-US-Screenshots-FitnessHero so your future self can find it. The name is internal only, so be verbose.

Step 3: Choose the locale

This is the most important early choice. PPO runs per-locale, which means a test in en-US does not affect what users in de-DE see. Start with your single highest-revenue market. Do not try to test five locales at once on your first attempt because you will dilute your sample size.

Step 4: Pick exactly one variable

Choose icon, screenshots, or app preview video. Do not pick more than one. If you change the icon and the screenshots at the same time, you cannot attribute the lift. This is the single most common mistake new teams make.

Step 5: Upload your treatments

Add up to three treatments. Each one must be a complete asset set for the locale. For screenshots, that means all required device sizes. Apple's official Product Page Optimization documentation lists current size requirements.

Step 6: Configure traffic allocation

The default is an equal split between control and each treatment. If you have four-way test (control plus three treatments), each gets 25 percent of organic traffic. You can lower the treatment allocation if you are worried about exposing too many users to an unproven variant, but the lower the allocation, the longer the test runs.

Step 7: Submit for review

Each treatment goes through App Review independently. This usually takes 24 to 48 hours in 2026. Treatments are reviewed for guideline compliance, not for quality, so make sure your screenshots follow Apple's marketing guidelines around device frames and status bars.

Step 8: Let the test run

Resist the urge to peek every hour. Give the test at least 14 days. Most teams stop at 30 days, which is the sweet spot for statistical significance on apps with moderate traffic. If your app is small, you may need the full 90 days that Apple allows.

Reading PPO Results: Statistical Significance and Lift

When you open the results dashboard, Apple shows you two numbers per treatment: the conversion rate and the improvement versus the control, along with a confidence indicator. The confidence indicator is what tells you whether the difference is real or just noise.

A reliable Apple Product Page Optimization result needs three things. First, enough visitors per treatment, ideally 2000 minimum, although 1000 can work for high baseline conversion apps. Second, a confidence level of 90 percent or higher, because anything lower is just a coin flip dressed up in statistics. Third, a meaningful effect size, which we define as at least a 3 percent relative lift. Anything below 3 percent is usually not worth the operational overhead of a rollout.

One nuance that catches teams off guard is that PPO measures impression-to-install conversion on the App Store itself, not retention. A treatment that wins on PPO might attract worse-fit users who churn faster. Always cross-reference your PPO winner with Day 7 retention before you commit. We cover this validation step in detail in our screenshot A/B testing deep dive.

Common Apple Product Page Optimization Mistakes

After running hundreds of PPO tests with customers, we see the same mistakes again and again. Avoiding these will put you ahead of 80 percent of competitors.

Running too many tests in parallel across locales. If you have four active tests, your operational attention is split four ways and your interpretation of each result gets fuzzier. Start with one test in one locale, ship the winner, then move on.
Stopping tests too early. A treatment that looks 15 percent better at day 3 frequently regresses to the mean by day 14. Wait for confidence, not for a feeling.
Testing icon and screenshots simultaneously. If both change, you cannot tell which moved the needle. Apple does not let you bundle them into a single test anyway, but some teams run two overlapping tests and confuse themselves.
Not localizing the test treatments. A treatment built for US users may underperform in Japan because of cultural and density differences. Always localize before launching a non-English PPO test.
Ignoring qualitative feedback. Conversion is one signal. App Store ratings, support tickets, and TestFlight comments all carry information about whether your new creative is honest about what the app does. A misleading treatment can win on conversion and lose on retention.
Forgetting App Review timelines. If your treatment gets rejected because the screenshots show fake content or a device with a status bar, you lose a week. Pre-check your assets against Apple's guidelines before you submit.

Advanced PPO Tactics for 2026

Once you have run a few baseline tests, here are the advanced moves we see top teams using this year.

Sequential testing with a creative ladder

Instead of testing three random variants, build a "ladder" of hypotheses. Test 1 establishes the best hero screenshot layout. Test 2 swaps the headline copy on the winner. Test 3 changes the background color on the new winner. Each test compounds on the previous one, and over six months you can lift baseline conversion by 30 percent or more.

Localized PPO as part of a market-entry plan

When you launch in a new country, run a PPO test in that locale within the first 60 days. Even with low traffic, the directional signal helps you adapt creative quickly. Pair this with our CPP localization guide for paid campaigns in the same market.

Seasonal treatments

Test a seasonal screenshot set (holiday, back-to-school, summer fitness) against your evergreen control. Even if seasonal does not win year-round, you may find a 4-week window where it dominates, which is worth scheduling into your release calendar.

Icon micro-tests

Icons are sticky on home screens, so big icon changes are risky. Use PPO to test subtle variations: a slightly bolder mark, a different background color, a new accent. Subtle wins still translate to thousands of incremental installs at scale.

Pairing PPO with your screenshot tooling

The faster you can produce variants, the more tests you can run. Manual screenshot production caps most teams at one or two PPO cycles per quarter. Using a dedicated screenshot generator from our ASO tools hub brings that down to a one-day turnaround for a full variant set, including device frames and localized text.

For deeper technical reading, Apple's own App Store Connect documentation covers the API endpoints and reporting fields you can use to pull PPO data into your own dashboards, and the App Store screenshot specifications page lists the current size and format requirements for treatments.

FAQ

How long should an Apple Product Page Optimization test run?

The minimum useful duration is 14 days, but 30 days is the realistic sweet spot for most apps. Apple allows tests to run up to 90 days, which is occasionally necessary for low-traffic apps that need more impressions to reach statistical significance. Stopping a test before day 14 almost always produces a result you should not trust.

Can I run PPO and Custom Product Pages at the same time?

Yes, and you should. PPO optimizes your default page for organic traffic, while CPPs serve targeted variants to paid campaigns, influencer audiences, or specific feature launches. They are complementary, not competitive. Just keep the test scope clear in your head so you do not confuse organic lift with paid lift.

Does Apple Product Page Optimization affect my keyword rankings?

No. PPO only affects conversion on the product page itself. Your search ranking is driven by keywords, downloads, retention, and ratings, none of which are part of a PPO test. A winning PPO treatment can indirectly improve rankings over time because higher conversion sends positive signals to Apple's ranking algorithm, but there is no direct keyword effect.

Start Testing Today

Apple Product Page Optimization is the closest thing to a free conversion optimization team that the App Store gives you. The only real cost is the creative production. If you have been holding back because building three new screenshot sets feels like too much work, that is the problem to solve first. Sign up for a free Shotlingo account to generate localized screenshot variants in minutes, ship them as PPO treatments this week, and let Apple tell you which one wins.

Originally published on Shotlingo

Best Free Tools for App Store Screenshot Localization in 2026

Shotlingo — Thu, 14 May 2026 12:06:14 +0000

Best Free App Store Screenshot Localization Tools in 2026

If your budget is stretched across translation, design, and ad spend, the ecosystem of free app store screenshot localization tools has never been stronger. In 2026 you can capture a screenshot from Xcode, run the copy through a free translator, check it for text expansion, validate the locale code, preview the right to left version, and drop the whole thing into a free template, all without paying a cent. The catch is that no single free tool does the whole job.

This roundup walks through ten tools we use or recommend in our own workflow. Some are ours, most are not. We ranked them by where they fit in a real pipeline, and called out what is free and what is gated. For the broader ASO toolbelt, our best ASO tools of 2026 roundup covers the paid landscape.

Why Use Free App Store Screenshot Localization Tools?

The obvious answer is cost. The less obvious answer is iteration speed. When localization is free at the margin, you stop treating it as a quarterly project and start shipping it alongside every feature release. A team that localizes once a year almost always loses to a team that localizes every sprint, because the second team learns faster.

Free tools also let small teams compete with funded studios. You do not need a six figure tooling budget to ship a properly localized listing. The free app store screenshot localization tools in this list are the ones we would reach for if we were starting from zero today.

One caveat. Free tools optimize for the common case. The moment your needs get specialized, for example bulk regenerating 40 locales every release, you will outgrow them. Start free, prove the workflow, then upgrade only where the pain is real. We cover that at the end of this post and in our ASO 2026 pillar.

Quick Comparison: Free App Store Screenshot Localization Tools

  | Tool 

  | Free features 

  | Limitations 

  | Best for 

| Shotlingo Free Tools 

  | Text expansion calculator, locale code lookup, RTL preview 

  | No bulk rendering on the free tier 

  | Pre flight checks before you commit to a design 

| AppLaunchPad Free Tier 

  | Template based screenshot builder, multiple device frames 

  | Watermark on free exports, limited locale tooling 

  | One off screenshot mockups with no localization layer 

| Mockupper 

  | Free device mockup generator, common iPhone and iPad frames 

  | No translation or text layer support 

  | Wrapping a finished screenshot in a device frame 

| Apple Localization Glossary 

  | Official Apple terminology in 40 plus languages 

  | Terminology only, not full translation 

  | Getting platform terms like Settings or Wallet exactly right 

| Google Translate 

  | Free machine translation for 130 plus languages 

  | Tone is often flat, idioms break 

  | First pass translation before human review 

| DeepL Free 

  | Higher quality translation for European and East Asian languages 

  | Character cap on free tier, fewer languages than Google 

  | Polishing marketing copy in supported languages 

| Figma Community Templates 

  | Free downloadable App Store screenshot templates 

  | Manual swap for each locale, no automation 

  | Designers who already live in Figma 

| AppScreens Free Tier 

  | Template based screenshot maker with starter export 

  | Locked premium templates and exports on free plan 

  | Trying a competing tool before you commit 

| Xcode Simulator 

  | Capture pixel perfect screenshots in any locale Apple supports 

  | Mac only, no marketing layer 

  | Generating the raw source screenshots you will localize 

| Shotlingo Locale Code Lookup 

  | Search and copy the exact App Store Connect locale code 

  | No translation features, lookup only 

  | Avoiding the classic en-US vs en-GB mistake

10 Best Free Tools for App Store Screenshot Localization

Here is the full breakdown, ordered roughly by where each tool fits in the workflow rather than by raw quality.

1. Shotlingo Free Tools

Our own free toolset lives at /tools and is built for the pre flight stage of localization. The three tools we ship for free are the Text Expansion Calculator, the App Store Locale Code Lookup, and the RTL Screenshot Preview.

What is free: All three tools, no signup gate. What is limited: Bulk rendering, AI translation, and the full template library are paid. Best for: Validating that your English copy will not overflow once translated, confirming the locale code Apple expects, and seeing how Arabic or Hebrew breaks your composition before you ship to a translator.

2. AppLaunchPad Free Tier

AppLaunchPad is one of the older template based screenshot makers and still has a usable free tier. You pick a template, drop in a device frame and some copy, and export. The free export carries a small watermark.

What is free: Template library, device frames, basic export. What is limited: Watermark removal and bulk locale automation sit behind the paid tier. Best for: Solo developers who want a quick mockup to share with stakeholders.

3. Mockupper

Mockupper focuses narrowly on wrapping a flat screenshot in a realistic device frame. It is not a localization tool by itself, but it solves a real subproblem. Once you have a localized screenshot rendered, you still need to present it in a frame that matches Apple's current device generation.

What is free: Most device mockups and exports. What is limited: No text layer, no translation, no template logic. Best for: The last step of a workflow where you already have the localized image and just need a frame.

4. Apple Localization Glossary

Apple publishes an official localization glossary that contains the canonical translation of every platform term, from Settings to Wallet to Sign in with Apple, in more than 40 languages. If your screenshot copy uses an Apple specific term, you should pull it from this glossary, not a generic translator. Browse it at developer.apple.com/localization.

What is free: The entire glossary, including downloadable AppleGlot files. What is limited: Terminology only, so you cannot translate full sentences. Best for: Making sure your German screenshot uses the canonical Apple term.

5. Google Translate

The default baseline for free machine translation. Google Translate covers 130 plus languages, runs in the browser, and is free. The tone is often flat and it struggles with idiomatic marketing copy, but for a first pass it is fine.

What is free: Everything, plus the API up to a generous quota. What is limited: Quality varies by language pair. Japanese, Korean, and Arabic output usually needs heavier human editing. Best for: Getting a rough translation in front of a native reviewer fast.

6. DeepL Free

DeepL has earned a reputation for nuanced translation, particularly between European languages and into Japanese. The free tier is generous enough that most solo developers will never pay.

What is free: Web translation with a monthly character cap, browser extensions, basic desktop app. What is limited: Fewer languages than Google, no glossary on the free tier. Best for: Polishing short marketing copy where tone matters. Try it side by side with Google at deepl.com and pick the more natural output.

7. Figma Community Templates

The Figma Community is full of free App Store screenshot templates, many of them surprisingly well built. You download the template, duplicate the page per locale, and swap copy by hand.

What is free: Most community templates and the Figma free tier. What is limited: No automation. Every locale is a manual duplicate, which gets painful past three or four languages. Best for: Designers who want full control over composition.

8. AppScreens Free Tier

AppScreens is a competing template based screenshot tool with a real free tier. You can build a screenshot, preview it, and export a starter version without paying.

What is free: Basic templates, starter exports, locale switcher in preview. What is limited: Premium templates and bulk export sit on the paid plan. Best for: Comparing the template based approach before you settle on one tool.

9. Xcode Simulator (Apple Sandbox)

Xcode ships with the iOS Simulator, which lets you change device language and region and capture pixel perfect screenshots of your real app in any Apple supported locale. The screenshots come out at the exact resolution Apple expects for App Store Connect, which saves a step downstream.

What is free: Everything. Xcode is a free download from the Mac App Store. What is limited: Mac only, and the Simulator captures the app, not the surrounding marketing layer. Best for: Generating the raw source screenshots that every other tool in this list will frame, caption, and localize.

10. Shotlingo Locale Code Lookup

We list our App Store Locale Code Lookup twice for a reason. App Store Connect expects very specific locale codes, for example en-GB for British English and pt-BR for Brazilian Portuguese, and getting the code wrong means your upload silently fails or attaches to the wrong locale.

What is free: The full lookup, no signup. What is limited: Reference tool, not a translator. Best for: Anyone who has ever wondered why their Spanish screenshots were not showing up in Mexico because they used es-ES instead of es-MX.

How to Combine Free Tools for a Full Localization Workflow

A toolbox is only useful if you know the order to reach for things. Here is the workflow we recommend to teams who want to go fully free, end to end.

Capture the source screenshots. Use Xcode Simulator to grab raw frames in your primary locale, usually en-US.
Validate locale codes. Run every target market through the Locale Code Lookup so you are not guessing.
Check text expansion. Drop your headline into the Text Expansion Calculator to confirm German and Russian will not overflow.
Translate the copy. First pass through Google Translate or DeepL Free, then validate Apple specific terms against the Apple Localization Glossary.
Preview right to left layouts. Use the RTL Screenshot Preview before you commit to an Arabic or Hebrew design.
Compose the screenshot. Use a Figma Community template, AppLaunchPad free, or AppScreens free to lay out the marketing layer.
Frame the final image. Run it through Mockupper for the device frame if your template did not handle it.
Upload. Submit through App Store Connect with the locale codes you validated in step 2.

This gets you a fully localized App Store listing without spending a cent. It is slower than a paid pipeline past three or four locales, but it ships. For the strategic side, our localization hub walks through it locale by locale.

When to Upgrade to Paid Tools

Free is not free forever. Three signals tell you it is time to spend money.

You are localizing into more than five markets. The manual duplicate step in Figma or AppLaunchPad starts costing more in designer time than a paid tool would cost outright.

You ship screenshot updates every release. If your screenshots are a living asset, automation pays for itself in the second month. Bulk rendering and template inheritance are the features you will miss first.

You are running paid CPP experiments. Custom Product Pages multiply screenshots by locales. The math gets ugly fast, and free tools are not built for that volume.

If any of these describe you, create a Shotlingo account and try the paid tier alongside the free tools you already use.

FAQ

Are free app store screenshot localization tools good enough for production?

For one to three locales, yes. The combination of Xcode Simulator, DeepL Free, the Apple Localization Glossary, and a Figma template will get you to a shippable result. Past three locales, the manual labor cost starts to outweigh the price of a paid tool.

Which free translation tool is best for App Store copy?

For European languages and Japanese, DeepL Free usually reads more naturally than Google Translate. For everything else, Google Translate has wider language coverage. Run both and pick the output that needs less editing. Always have a native speaker review the final copy.

Can I localize App Store screenshots without a Mac?

Mostly yes. You can do translation, layout, and framing on any operating system using browser based tools. The one step you cannot do without a Mac is the Xcode Simulator capture. Some teams rent cloud Macs for that single step and run the rest of the pipeline on Windows or Linux.

Start With the Free Stack

You do not need a paid tool to ship a properly localized App Store listing in 2026. You need a clear workflow and a handful of focused free app store screenshot localization tools used in the right order. Start with our free tools hub, validate your locale codes, check text expansion, preview right to left layouts, and then layer in translation and design.

If you want to try the full Shotlingo workflow, create a free account in under a minute. The worst version of localization is the one you never ship.

Originally published on Shotlingo

How Apple Custom Product Pages Work With Localization (2026 Guide)

Shotlingo — Mon, 11 May 2026 09:23:42 +0000

How Apple Custom Product Pages Work With Localization (2026 Guide)

If you are running App Store ads or growth experiments in 2026, custom product pages localization is the single most underused lever in ASO. Apple Custom Product Pages (CPP) launched with iOS 15 and gave every developer up to 35 alternate versions of their product page, each with unique screenshots, app preview videos, and promotional text. What most teams forget is that every CPP is itself a per locale object. A CPP built for the US market is not the same asset as a CPP built for Japan, and the moment you treat them as the same, you start leaving installs on the table.

This guide explains how CPP and localization interact, the realistic math behind a 35 by 40 grid of variants, the field-by-field strategy that actually moves conversion, and the App Store Connect workflow for shipping a properly localized CPP. If you have not read our broader Apple Custom Product Pages guide yet, start there for the fundamentals. This post picks up where that one ends.

Why Custom Product Pages Localization Is the Most Overlooked ASO Lever

Walk into any growth team and ask how many CPPs they run. You will usually hear a confident answer between five and fifteen. Ask how many of those CPPs are localized into the markets that drive 60 percent of their non-US traffic and the room goes quiet. This is the gap. Teams treat CPP as an English-first creative testing tool when it is in fact a per locale conversion tool.

The reason custom product pages localization gets skipped is partly cost and partly process. Localizing one default product page already feels like a project. Localizing fifteen CPPs into five languages can sound like sixty separate creative deliverables. In reality it is closer to fifteen real briefs plus a translation pipeline, and the conversion lift is usually large enough to pay for itself inside one ad campaign. According to Apple's official documentation, every CPP supports the same locales as your default product page, which means the infrastructure is already there. You just have to use it.

If you are still framing localization as a translation problem, read our pillar on what ASO looks like in 2026. Modern ASO is locale-native, not English-translated.

How Custom Product Pages and Localization Interact

To use this lever well, you need a precise mental model of how the two systems combine.

One CPP, many locales

When you create a CPP in App Store Connect, Apple gives you a Default version. That default acts as the fallback for any locale you have not explicitly filled in. Then for every locale your default product page supports, you can choose to override the screenshots, app preview videos, and promotional text. The override is per locale, per CPP, and per field. You can localize screenshots only and let the promotional text fall back to the default, or vice versa, although mixing fallback behavior is usually a sign you have not finished the job.

Each localized CPP variant gets the same ppid URL parameter as its parent CPP. The locale is resolved by the user's App Store storefront, not by the URL. That means a single CPP link sent to a Japanese user surfaces the Japanese variant automatically, as long as that variant exists. If it does not, the user sees the Default in English, and you have just wasted ad spend.

The 35 by 40 math

Apple allows up to 35 CPPs per app, and your product page can support up to roughly 40 locales depending on regional availability. On paper this is 1,400 possible variants. In practice almost nobody should attempt to fill that grid. The interesting question is not the maximum, it is the smallest set that captures most of the upside.

The realistic answer almost always lands between 10 and 20 fully localized CPPs. Beyond that you start fighting diminishing returns, and the operational cost of keeping each variant fresh begins to exceed the conversion benefit.

Realistic Custom Product Pages Localization Strategy

The strategy that works in 2026 is to compound personas and locales rather than testing them in isolation.

Pick 3 personas, top 5 locales, 15 high-impact CPPs

Identify your three highest-value user personas. For a fitness app this might be beginners, runners, and strength trainers. For a finance app it might be students, freelancers, and small business owners. Then identify your top five revenue or install locales. The cross product gives you fifteen CPPs, each tightly targeted in both audience and language. This is the sweet spot we see most teams converge on.

  | Market 
  | Locale code 
  | Why it matters 
  | Translation priority 
  | Notes 




  | United States 
  | en-US 
  | Highest paid ad CPM, default revenue market 
  | Source 
  | Build the master CPP here, then branch. 


  | Japan 
  | ja 
  | High ARPU, strong CPP lift when localized natively 
  | Critical 
  | See our [Japanese screenshot localization workflow](/localize/app-store-screenshots-to-japanese). 


  | Germany 
  | de-DE 
  | Largest European market, text expansion is real 
  | Critical 
  | Check our [German localization guide](/localize/app-store-screenshots-to-german) for length issues. 


  | South Korea 
  | ko 
  | Mobile-first, paid ads convert well with native creative 
  | High 
  | Hangul changes both layout and reading rhythm. 


  | France 
  | fr-FR 
  | Strong organic traffic, sensitive to English-only ads 
  | High 
  | Translate promotional text first if budget is tight.

Run each persona across all five locales and you have fifteen CPPs that map directly to fifteen ad sets. This is where custom product pages localization stops being theory and starts being a campaign-level multiplier. Localized CPP for paid ads, when the ad creative language matches the destination CPP language, regularly drives a 30 to 50 percent conversion lift versus pointing the same ad at the Default English page.

Which fields actually change per locale

Not every field needs the same level of attention. In order of impact:

Screenshots. The biggest lever. Native fonts, native copy, native cultural cues. Use our text expansion calculator before you finalize layouts in German or Russian.
App preview video. Subtitles are the minimum, dubbed voiceover is the ceiling. For high-value locales like Japan and Korea, subtitles alone tend to underperform.
Promotional text. The most commonly forgotten field. Many teams ship beautifully localized screenshots while the promotional text sits in English. Apple updates this field independently of the binary, so there is no excuse.
App name and subtitle. These come from your default product page, not the CPP itself. Make sure your localization base is solid before stacking CPP variants on top of it. The localization hub covers this.

Common Custom Product Pages Localization Mistakes

After auditing hundreds of accounts, the same five mistakes show up over and over.

Mistake one. Localizing screenshots but leaving promotional text in English. The user reads the screenshots in their language, then hits a wall of English at the bottom. Trust drops, conversion drops.
Mistake two. Treating CPP locales as a translation job rather than a transcreation job. Direct translation of an English headline rarely lands. Briefs should give translators room to rewrite.
Mistake three. Building too many CPPs and localizing none of them. Fifteen English-only CPPs is almost always worse than five fully localized CPPs.
Mistake four. Ignoring text expansion. German runs 20 to 35 percent longer than English. Russian and Finnish are similar. If your English layout is tight, your German layout will break. Validate every screenshot.
Mistake five. Forgetting to refresh the Default. If a user lands on your CPP from an ad targeted at a locale you have not localized, they see the Default. A stale Default is a quiet conversion killer.

Setting Up a Localized CPP in App Store Connect (step by step)

The current App Store Connect flow is straightforward once you have your assets ready.

In App Store Connect, open your app and go to the App Store tab. Select Custom Product Pages in the left sidebar.
Click Create, name the CPP something descriptive, and choose the version it should attach to.
Apple opens the CPP editor on the Default view. Build your master English version here first. This is your fallback for any locale you do not explicitly fill in.
Use the Default versus Localized toggle near the top of the editor. Switching to Localized exposes the same locale list you have on your main product page.
Pick a locale, for example Japanese. Upload the localized screenshots, swap the app preview video if you have one, and rewrite the promotional text in native Japanese. Do not paste machine-translated output here. The promotional text is short enough that a careful human pass pays back quickly.
Repeat per locale. Save each one. Apple lets you submit the CPP for review independently of your binary, which keeps the iteration loop fast.
After approval, copy the CPP URL with its ppid parameter and use it as the destination for your Apple Search Ads or paid social campaigns targeted at that locale.

Apple's CPP setup documentation covers the exact UI in more detail if you want to bookmark it next to App Store Connect.

Measuring Localized CPP Performance

The right metrics depend on where the traffic comes from, but the core dashboard looks similar for everyone.

Conversion rate per CPP per locale. App Store Connect breaks this out natively. Compare each localized CPP against your Default product page in the same locale, not against the English Default.
Paid traffic conversion lift. Run an A/B between ads pointed at the localized CPP versus ads pointed at the Default product page in that locale. A 30 to 50 percent lift is the usual range when the localization is done well. Anything under 10 percent means the screenshots are probably translated rather than transcreated.
Retention quality by CPP. Sometimes a localized CPP drives lower install volume but materially better day 7 retention because it qualifies users more honestly. Track this.
Time to first review per locale. Localized CPPs tend to surface friction faster because users feel comfortable enough to write reviews in their own language.

If a localized CPP underperforms the Default in its own locale, the problem is almost always one of three things. The translation is too literal, the promotional text was forgotten, or the screenshots use cultural references that do not transfer. Fix in that order.

FAQ

Do I need to localize every CPP into every locale my app supports?

No. Localize only the locales where you actually plan to send traffic. Sending an ad campaign to a locale where the CPP has not been localized is fine because Apple falls back to the Default. What is not fine is localizing into a market you have no campaign or organic strategy for. Focus on the five locales where you actually spend money or have meaningful organic visibility.

Can I update a localized CPP without resubmitting the binary?

Yes. CPPs and their localized variants are reviewed independently from app binaries. You can iterate on screenshots, promotional text, and preview videos without shipping a new version of the app, which is exactly why CPP is such a fast feedback loop.

What is the difference between a localized CPP and a localized default product page?

The default product page is the page Apple shows for organic traffic. A CPP is an alternate version that only appears when a user follows a CPP-specific link with a ppid parameter. Both can be localized. The default product page is your organic foundation. CPPs are your paid and campaign-specific overlays on top of that foundation.

Ship localized CPPs without the manual grind

The math of custom product pages localization is brutal if you do it by hand. Fifteen CPPs across five locales is seventy-five screenshot sets, plus promotional text, plus video subtitles. Shotlingo automates the screenshot layer end to end, including text expansion checks, native font handling, and per locale templating. You design once in your source language and ship a fully localized set ready for upload to App Store Connect.

Create your free Shotlingo account and turn one set of source screenshots into fifteen high-converting localized CPP variants this week.

Originally published on Shotlingo

App Store Screenshot Sizes for All iPhone 17 Models in 2026

Shotlingo — Thu, 07 May 2026 11:26:17 +0000

App Store Screenshot Sizes for All iPhone 17 Models in 2026

If you ship an iOS app in 2026, you need to know the new iPhone 17 screenshot sizes Apple now requires in App Store Connect. The iPhone 17 lineup, released in September 2025, introduced a fresh 6.3" display class along with the familiar 6.9" Pro Max format. Getting these dimensions wrong is the fastest way to fail App Store review or end up with stretched, blurry visuals on the storefront.

This guide breaks down every iPhone 17 screenshot size you need, which ones are required, which are optional, and how to capture them cleanly. We will also cover localization gotchas and the most common mistakes teams make when uploading assets for the iPhone 17, 17 Plus, 17 Pro, 17 Pro Max, and the brand new iPhone Air.

What's New for iPhone 17 Screenshot Sizes

The biggest change in 2026 is that Apple split the standard iPhone display class. The iPhone 17 and iPhone 17 Pro both ship with a 6.3" panel running at 2622 x 1206 pixels. That is a brand new resolution that did not exist before, and it is now its own dedicated screenshot slot inside App Store Connect.

Meanwhile, the 6.9" display class continues to cover the iPhone 17 Plus and iPhone 17 Pro Max at 2868 x 1320. Apple added a third member to this class this year: the ultra thin iPhone Air, which uses a 6.6" panel at 2778 x 1284 but is uploaded under the 6.5" or 6.9" slot depending on your asset strategy.

For a deeper look at how screenshot specs evolved across the entire Apple lineup, read our complete guide to App Store screenshot sizes in 2026. It includes the full historical context for 5.5", 6.5", 6.7", and 6.9" devices.

Complete iPhone 17 Screenshot Size Reference

Here is the master table you can bookmark. Every iPhone 17 screenshot size uses portrait orientation by default, and Apple expects PNG or JPG files at the exact pixel dimensions listed below.

  | Device 

  | Display 

  | App Store Resolution (portrait) 

  | Required? 

| iPhone 17 

  | 6.3" 

  | 1206 x 2622 

  | Yes (new) 

| iPhone 17 Pro 

  | 6.3" 

  | 1206 x 2622 

  | Yes (new) 

| iPhone 17 Plus 

  | 6.9" 

  | 1320 x 2868 

  | Yes (baseline) 

| iPhone 17 Pro Max 

  | 6.9" 

  | 1320 x 2868 

  | Yes (baseline) 

| iPhone Air 

  | 6.6" 

  | 1284 x 2778 (6.5" slot) 

  | Optional

Why two slots cover five devices

Apple does not require a unique screenshot per phone model. Instead, they group devices by display size class. So the iPhone 17 and 17 Pro share assets, while the 17 Plus and 17 Pro Max share their own. The iPhone Air sits between the two, and most teams reuse the 6.9" assets for it.

That means you only need to design two master screenshot sets to cover the entire iPhone 17 family. If your app also supports older devices, see our breakdown of how many screenshots the App Store actually shows.

Required vs Optional iPhone 17 Screenshot Sizes

App Store Connect now treats the 6.9" display as the minimum baseline. If you do not upload 6.9" assets, your submission will be rejected. The new 6.3" iPhone 17 screenshot size joined the required list this year as well, since it covers the standard iPhone 17 and 17 Pro.

Here is what you must upload, and what you can skip:

Required: 6.9" at 1320 x 2868 pixels
Required: 6.3" at 1206 x 2622 pixels (new for iPhone 17)
Optional: 6.7" at 1290 x 2796 pixels (legacy fallback)
Optional: 6.5" at 1242 x 2688 or 1284 x 2778 pixels
Optional: 5.5" at 1242 x 2208 pixels (deprecated)

Apple will automatically scale your 6.9" assets down for older devices if you skip the smaller slots, but the result is rarely pixel perfect. You can confirm the latest requirements in Apple's official screenshot specifications.

How to Capture iPhone 17 Screenshots

You have three practical options for producing assets at the correct iPhone 17 screenshot sizes. The right choice depends on whether you have access to the hardware, how polished you want the final output to look, and how many languages you plan to localize into.

From a real device

Press the side button and the volume up button at the same time on any iPhone 17 model. The screenshot saves to Photos at the device's native resolution, which already matches the App Store Connect requirement. AirDrop the file to your Mac to keep the original pixel dimensions intact.

This is the cleanest path for product screenshots that need to match the real UI. The downside is you cannot easily swap text or backgrounds, which makes localization slow.

From Xcode Simulator

Open Xcode, launch the iPhone 17 or iPhone 17 Pro Max simulator, and press Cmd + S to save a screenshot to your desktop. The simulator outputs at the exact resolution of the modeled device, so a 17 Pro Max simulator will produce a 1320 x 2868 file ready to upload.

Apple documents the full simulator workflow in the Xcode capturing screenshots guide. This approach is great for engineering teams but lacks marketing polish.

From a screenshot generator tool

Most marketers use a dedicated tool to design the final App Store visuals. A generator lets you start from a blank canvas at the right iPhone 17 screenshot size, drop in your UI capture, add headlines, frames, and backgrounds, and export every locale at once.

Shotlingo handles all five iPhone 17 resolutions automatically. You upload one design, and it renders perfect 1206 x 2622 and 1320 x 2868 output for every language. Browse our tools hub to see what else is available, or jump straight to the localization workflow if you ship in more than one market.

How iPhone 17 Sizes Affect Localization

Bigger canvases mean more room for translated copy, but they also expose layout problems faster. A German headline that fit on a 6.5" screenshot can wrap awkwardly on a 6.9" canvas if you did not plan padding correctly. The new 6.3" slot is even tighter than the 6.7" you may be used to.

Before you commit to a headline, run it through our free text expansion calculator. It estimates how much longer your text will become in 30+ languages so you can size your title font correctly before exporting all five iPhone 17 resolutions.

If you are new to localized App Store assets, our pillar guide on what App Store Optimization looks like in 2026 covers how screenshots interact with keywords, conversion rate, and store listings across regions.

Common Mistakes with iPhone 17 Screenshots

The same handful of issues come up over and over when teams upload iPhone 17 assets. Avoid these and your submission usually clears review on the first try.

Uploading 6.7" instead of 6.9": The 6.7" slot is legacy. Apple wants 1320 x 2868 as the new baseline.
Skipping the 6.3" slot: The new iPhone 17 screenshot size at 1206 x 2622 is required, not optional.
Wrong aspect ratio: Even one pixel off and App Store Connect rejects the file. Always export at the exact dimensions.
Compressed JPGs: Heavy compression introduces banding on the iPhone 17 OLED. Use PNG when possible.
Forgetting safe areas: The Dynamic Island and rounded corners can clip headlines if you push text to the edges.
Reusing iPhone 16 assets: The 6.3" panel is genuinely new. Older 6.1" assets will look soft when scaled up.

If you want a sanity check before submitting, Apple's App Store product page documentation shows exactly how each screenshot slot renders on the live storefront.

FAQ

Do I need separate screenshots for the iPhone 17 and the iPhone 17 Pro?

No. Both phones share the same 6.3" display at 1206 x 2622 pixels, so a single set of assets covers both. Apple groups screenshot slots by display size class, not by individual SKU.

Can I just upload 6.9" screenshots and let Apple downscale for the rest?

Technically yes, but the result usually looks soft on the new 6.3" iPhone 17. For best conversion rate, design native assets for both required slots. The extra effort pays off in sharper text and crisper UI captures.

Where does the iPhone Air fit in?

The iPhone Air uses a 6.6" panel at 2778 x 1284 pixels. App Store Connect does not give it a dedicated slot yet, so most teams upload the 6.9" assets and let the system handle scaling. You can also upload to the legacy 6.5" slot if you want tighter control.

Ship Your iPhone 17 Screenshots Faster

The new iPhone 17 screenshot sizes are not hard to produce once you know the dimensions. The hard part is rendering every required size, in every language, every time you ship a feature update. Manual exports break down quickly past two locales.

Shotlingo automates the entire pipeline. Design once, get pixel perfect 1206 x 2622 and 1320 x 2868 output for every language, ready to drop into App Store Connect. Create your free Shotlingo account and ship your iPhone 17 screenshots in minutes, not days.

Originally published on Shotlingo

Best ASO Tools 2026 — Free & Paid Roundup for Indie Developers

Shotlingo — Mon, 04 May 2026 12:30:41 +0000

Best ASO Tools 2026: Free and Paid Roundup for Indie Developers

Choosing the right stack of best ASO tools in 2026 is harder than it sounds. The market is crowded with platforms promising keyword magic, AI metadata, and competitor x-ray vision. Some of them deliver. Others charge enterprise rates for features you can replicate with a free Apple Search Ads account.

This roundup is written for indie developers and small studios who care about ROI per dollar spent. We tested every tool listed below on real apps, and we will be honest about where each one shines and where it falls short. If you only have budget for one or two app store optimization tools, this guide will help you pick wisely.

How We Picked the Best ASO Tools

We evaluated each platform on five criteria that actually matter when you ship apps:

Data accuracy compared to first-party sources like App Store Connect and Google Play Console.
Workflow speed for indie developers who do not have a dedicated ASO team.
Price-to-value ratio at the entry tier, not the enterprise tier.
Localization support, since 60 percent of app revenue comes from non-English markets.
Free tier or trial that is actually usable, not a five-minute demo.

We are biased toward tools that respect indie budgets. If a platform requires a sales call to see pricing, we said so. For the foundational concepts behind these tools, our ASO pillar guide covers how the App Store and Play Store rank apps in 2026.

Quick Comparison Table of the Best ASO Tools

  | Tool 

  | Best for 

  | Pricing 

  | Free tier? 

| Shotlingo 

  | Screenshot localization at scale 

  | From around 19 USD/mo 

  | Yes (free tools) 

| AppTweak 

  | Deep keyword research and ASO intelligence 

  | From around 79 USD/mo 

  | 7-day trial 

| Sensor Tower 

  | Market intelligence and competitive data 

  | Enterprise (custom) 

  | Limited free 

| AppLaunchPad 

  | Screenshot templates and quick mockups 

  | Free or around 9 USD/mo 

  | Yes 

| AppFigures 

  | Keyword tracking and review monitoring 

  | From around 25 USD/mo 

  | 14-day trial 

| MobileAction 

  | Keyword tracking plus ad intelligence 

  | From around 69 USD/mo 

  | Free starter plan 

| Asodesk 

  | Keyword research on a budget 

  | From around 25 USD/mo 

  | 7-day trial 

| AppRadar 

  | AI metadata generation and keyword tools 

  | From around 80 USD/mo 

  | Limited free 

| Apple Search Ads 

  | Free keyword popularity data for iOS 

  | Free 

  | Yes (fully free) 

| Google Play Console 

  | First-party Android keyword and experiment data 

  | Free with developer account 

  | Yes

Best ASO Tools Reviewed in Detail

Below is the full breakdown for each of the ten ASO tools. We grouped paid platforms first, then closed with the two free first-party tools every developer should already be using.

1. Shotlingo

Shotlingo is a screenshot localization specialist built for teams who ship to many App Store and Play Store markets. Instead of rebuilding screenshots in Figma every time you launch in a new country, you upload one master design and Shotlingo translates the text, swaps fonts, and exports App Store and Play Store ready assets in 30 plus languages.

Best for: Indie devs and studios localizing screenshots into multiple markets.
Pricing: Free tools available. Paid plans start around 19 USD per month.
Key feature: AI-driven screenshot translation with font auto-pairing and store-specific export sizes.
Pros: Removes the bottleneck of localized creative production. Free utility tools like the screenshot resizer are genuinely useful even on the free plan.
Cons: Focused on screenshots, not a full keyword research suite. Pair it with a keyword tool for complete ASO coverage.

If localization is your bottleneck, our localization hub walks through the workflow from master design to 30 language exports.

2. AppTweak

AppTweak is one of the most respected names in ASO intelligence. Their keyword data is sourced from multiple signals and updated frequently, which makes it a popular pick for agencies and mid-size studios.

Best for: Teams that need defensible keyword research data to share with clients or stakeholders.
Pricing: Plans start around 79 USD per month and scale up significantly for full features.
Key feature: ASO score with actionable recommendations for title, subtitle, and keyword field optimization.
Pros: Excellent keyword difficulty and chance scores. Strong global coverage including emerging markets.
Cons: The entry price is steep for a solo indie. Some advanced reports are gated to higher tiers.

3. Sensor Tower

Sensor Tower is the platform large publishers and investors use for market sizing and competitor revenue estimates. It is overkill for most indie devs, but if you are pitching a publisher or raising funding, the data carries weight.

Best for: Market intelligence, download estimates, and competitive benchmarking at scale.
Pricing: Enterprise. Expect to talk to sales for a custom quote.
Key feature: Cross-platform download and revenue estimates plus ad creative library.
Pros: Industry-standard data trusted by publishers and analysts. Deep historical archives.
Cons: Pricing is opaque and almost always out of indie budget. Limited free tier.

4. AppLaunchPad

AppLaunchPad is a browser-based screenshot generator with more than 1000 templates. It is a fast way to draft store screenshots without opening Figma or Photoshop, which is why many first-time developers start here.

Best for: Developers who want a quick, template-driven screenshot draft.
Pricing: Free tier with watermarks. Paid removes watermarks at around 9 USD per month.
Key feature: Large template library with device frames and multi-screen export.
Pros: Low learning curve. Good for MVP launches with limited time.
Cons: Templates can feel generic, and localization across 20 plus languages is a manual job. See our Shotlingo vs AppLaunchPad comparison for a feature-by-feature breakdown.

5. AppFigures

AppFigures has been around since 2008 and remains a favorite for developers who want clean keyword tracking and review monitoring without enterprise pricing.

Best for: Indie devs who want reliable rank tracking and review alerts at a fair price.
Pricing: Plans start around 25 USD per month.
Key feature: Daily keyword rank tracking across countries plus consolidated review feeds.
Pros: Clean interface. Honest pricing with no sales call required.
Cons: Keyword research database is smaller than AppTweak or Sensor Tower. Better for tracking than discovery.

6. MobileAction

MobileAction blends ASO data with paid ad intelligence, which is unusual at this price point. If you run Apple Search Ads or Google App Campaigns, the combined view saves time.

Best for: Teams running both ASO and paid user acquisition.
Pricing: Plans start around 69 USD per month. A free starter plan exists with limited features.
Key feature: Ad creative library plus keyword intelligence in one dashboard.
Pros: Strong Apple Search Ads integration. Useful for scaling paid campaigns.
Cons: Interface can feel busy. Some keyword counts disagree with first-party sources.

7. Asodesk

Asodesk is one of the more indie-friendly platforms in this list. Pricing is transparent, and the keyword research tools are surprisingly deep for the cost.

Best for: Solo developers who want serious keyword research without the AppTweak price tag.
Pricing: Entry plans start around 25 USD per month.
Key feature: Keyword auto-suggestions and competitor keyword overlap reports.
Pros: Affordable. Decent App Store and Play Store coverage.
Cons: Smaller team and less brand recognition compared to AppTweak. Some dashboards feel dated.

8. AppRadar

AppRadar leans into AI-assisted metadata generation, which is genuinely helpful when you stare at the keyword field and your brain freezes. It also offers solid keyword research and tracking.

Best for: Developers who want AI to draft titles, subtitles, and keyword sets they can refine.
Pricing: Plans start around 80 USD per month.
Key feature: AI metadata suggestions tied to keyword volume data.
Pros: Speeds up first-draft metadata. Combines tracking and creation in one tool.
Cons: AI suggestions still need human review. Pricing competes directly with AppTweak.

9. Apple Search Ads (free)

Apple Search Ads is the single most underused free ASO tool in 2026. You do not need to actually run ads to use it. Once you create an account, the keyword popularity tool gives you Apple's own first-party search volume data on a 5 to 100 scale.

Best for: First-party iOS keyword popularity data, completely free.
Pricing: Free. You only pay if you choose to run actual ad campaigns.
Key feature: Keyword popularity scores straight from Apple.
Pros: Most accurate iOS volume data available. No third-party guessing.
Cons: No keyword difficulty metric. UI is built for ad buying, not ASO research. Read more in the official Apple Search Ads documentation.

10. Google Play Console (free)

For Android, your most important ASO tool is the one Google already gave you. Play Console offers store listing experiments, install conversion data, and acquisition reports that no third party can replicate.

Best for: Android creative testing and first-party install data.
Pricing: Free with a one-time 25 USD developer account fee.
Key feature: Store listing experiments for A/B testing icons, screenshots, and short descriptions.
Pros: Direct experiment results with statistical significance. No tool can match this for Android.
Cons: No keyword research equivalent to Apple Search Ads. The official Play Console documentation covers experiment setup in detail.

Which of the Best ASO Tools Should You Pick?

There is no single answer because the right stack depends on your stage and budget. Here are three realistic scenarios for indie developers in 2026.

Scenario 1: Solo indie, pre-launch, budget under 30 USD/mo

Use Apple Search Ads keyword popularity for iOS, Google Play Console for Android, and Shotlingo or AppLaunchPad for screenshots. Add Asodesk or AppFigures only when you have a live app with rank data worth tracking. This is the leanest viable ASO stack.

Scenario 2: Small studio, 2-3 live apps, budget around 100 USD/mo

Pair AppFigures or Asodesk for keyword tracking with Shotlingo for localized screenshots. Keep Apple Search Ads and Play Console open for first-party validation. This combination covers research, tracking, and creative without enterprise costs.

Scenario 3: Scaling studio with paid UA, budget 200 USD/mo and up

AppTweak or AppRadar plus MobileAction for the paid ads layer. Add Shotlingo for localization across 20 plus markets so creative production never blocks expansion. Sensor Tower only if you need investor-grade market data.

ASO Tools You Don't Need (Yet)

Tool stacks creep. New developers often subscribe to three keyword platforms because each promises a slightly different metric. Resist this. Here is what to skip until you actually have the problem.

Enterprise dashboards like Sensor Tower full access. Until you ship multiple apps with meaningful revenue, you are paying for data you cannot act on.
Multiple keyword tools with overlapping features. Pick one paid keyword tool and one first-party source. Stop there.
Standalone review reply tools if your current platform already includes review monitoring. AppFigures and AppRadar both ship this.

Spend the saved budget on localization and creative testing instead. That is where most indie apps leave money on the table. Our keyword optimization guide shows how to extract more value from a single keyword tool rather than stacking three.

FAQ

What are the best ASO tools for a solo indie developer in 2026?

Start free with Apple Search Ads keyword popularity and Google Play Console. Add one paid tool, either AppFigures or Asodesk for tracking, plus Shotlingo for screenshot localization. That stack costs under 50 USD per month and covers the essentials.

Are paid ASO tools worth it if I am just launching?

Not for keyword research. The first-party tools from Apple and Google are accurate and free. Paid tools become worth it when you need rank tracking across markets, competitor benchmarking, or AI metadata drafting at scale.

How accurate are third-party download estimates?

They vary. Sensor Tower and data.ai are generally considered the most reliable, but even they can be off by 20 percent or more for smaller apps. For a credibility check, cross-reference with public industry reports from data.ai when possible.

Ready to Localize Your Screenshots?

Picking the right keyword tool gets you found. Localized screenshots get you installed. If your app store creative still ships in English only, you are leaving non-English markets on the table. Create a free Shotlingo account and translate your first set of screenshots into 30 plus languages this week.

Originally published on 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.

DEV Community: Shotlingo

Why German App Store Listings Need 30% More Vertical Space

Why German App Store Listings Need 30% More Vertical Space (Data-Driven Analysis)

The TL;DR

German App Store Listing Text Expansion: The Numbers

Where German App Store Listings Break

1. Screenshot headline area

2. Caption strip under the headline

3. Feature bullet lists inside the screenshot

4. App description preview on the listing page

The 7 Common German Words That Wreck Your Layout

How to Design German App Store Listings Right

1. Reserve 30 to 35 percent more vertical space for the headline area

2. Drop headline font size by 10 to 15 percent

3. Add 25 percent more horizontal padding around captions

4. Use &amp;shy; soft hyphens for the worst offenders

5. Re-check on iPhone SE width

What Tools to Use

FAQ

How much longer is German than English, on average?

Do I need a separate screenshot template for German?

Can I just use a smaller font for German and keep everything else the same?

Localize Your App Store Listing the Right Way

Apple Product Page Optimization (PPO) Guide for 2026

Apple Product Page Optimization (PPO) Guide for 2026

What is Apple Product Page Optimization?

PPO vs CPP: Which One Do You Need?

What You Can and Cannot Test with Apple Product Page Optimization

How to Set Up a PPO Test in App Store Connect

Step 1: Navigate to the right section

Step 2: Create the test

Step 3: Choose the locale

Step 4: Pick exactly one variable

Step 5: Upload your treatments

Step 6: Configure traffic allocation

Step 7: Submit for review

Step 8: Let the test run

Reading PPO Results: Statistical Significance and Lift

Common Apple Product Page Optimization Mistakes

Advanced PPO Tactics for 2026

Sequential testing with a creative ladder

Localized PPO as part of a market-entry plan

Seasonal treatments

Icon micro-tests

Pairing PPO with your screenshot tooling

FAQ

How long should an Apple Product Page Optimization test run?

Can I run PPO and Custom Product Pages at the same time?

Does Apple Product Page Optimization affect my keyword rankings?

Start Testing Today

Best Free Tools for App Store Screenshot Localization in 2026

Best Free App Store Screenshot Localization Tools in 2026

Why Use Free App Store Screenshot Localization Tools?

Quick Comparison: Free App Store Screenshot Localization Tools

10 Best Free Tools for App Store Screenshot Localization

1. Shotlingo Free Tools

2. AppLaunchPad Free Tier

3. Mockupper

4. Apple Localization Glossary

5. Google Translate

6. DeepL Free

7. Figma Community Templates

8. AppScreens Free Tier

9. Xcode Simulator (Apple Sandbox)

10. Shotlingo Locale Code Lookup

How to Combine Free Tools for a Full Localization Workflow

When to Upgrade to Paid Tools

FAQ

Are free app store screenshot localization tools good enough for production?

Which free translation tool is best for App Store copy?

Can I localize App Store screenshots without a Mac?

Start With the Free Stack

How Apple Custom Product Pages Work With Localization (2026 Guide)

How Apple Custom Product Pages Work With Localization (2026 Guide)

Why Custom Product Pages Localization Is the Most Overlooked ASO Lever

How Custom Product Pages and Localization Interact

One CPP, many locales

The 35 by 40 math

Realistic Custom Product Pages Localization Strategy

Pick 3 personas, top 5 locales, 15 high-impact CPPs

4. Use `` soft hyphens for the worst offenders