App Store Screenshots for PPO and Custom Product PagesPPO and Custom Product Pages
Give more visitors a reason to install. Test which screenshot message converts with Product Page Optimization, and match each campaign to its audience with Custom Product Pages. Design, localize and upload your variants in AppScreens without rebuilding every size.
Get more from the visitors you already attract. A clearer first screenshot helps people understand why your app is worth installing; testing tells you which message works for your audience.
OLBG reported 61% higher conversion after testing its iOS screenshot designs and order with SplitMetrics. Read the case study →
Make your value obvious in the first 3 screenshots
Test messaging and styles, measure conversions
Localize the pitch, not just the words
AppScreens makes screenshot iteration painless: restyle your project to a new template, responsive sizing, localization, and upload-ready exports. Using Product Page Optimizations & Experiments, you can try new screenshots, improve conversions and get more downloads in just a few minutes.
Create App Store Screenshot A/B Tests with PPOA/B Tests with PPO
Your test should be about the message, not hours spent rebuilding assets. Start with the set you already like, duplicate it and change the idea you want to test.
Keep your original intact and turn a copy into the next treatment. Your existing layout, app captures and styling give the test a head start.
Test one idea: a sharper opening headline, a larger app view or a different first screenshot. Keep the other screens steady so the result answers that question.
Review the iPhone and iPad outputs you need. Fit translated captions and use the right app images for each locale before you deliver the set.
Create or select the PPO destination and upload the finished set directly from AppScreens. Complete Apple’s review and launch the test in App Store Connect.
Illustrative duplicate: CookBook’s App Store set is copied into Variant A with the same layout, captures and styling.
Duplicate projectCookBook
CookBook: App StoreOriginal set, kept as the control
Kept
A
CookBook: Variant ASame layout, app captures and styling
Copied
1
First screenshotReady for the one change you test
Edit
Agent Skills + AppScreens MCP
Let your AI AgentAI Agent create your next screenshot variant
Ask your agent to duplicate a saved project and try a different headline, visual style or screenshot order. Keep your original set and prepare an editable alternative for a test or audience.
Compare the previews, then approve delivery to a supported listing or export the images for your test. Run experiments and review their results in the store console.
From an Audible App Store reference to an editable demo draft, created by an AI agent in AppScreens.
Before You Start a PPO TestPPO Test
Test screenshots without a new app version
New PPO screenshots go through Apple review independently of a new app version. Try your next creative idea on its own schedule, without waiting for another app release.
Start with a test your traffic can answer
A focused test makes the result easier to act on. Compare one clear change with your original, and use the low-traffic screenshot testing guide to decide whether your test is practical.
Build Custom Product Page Screenshots for Each AudienceEach Audience
Choose an audience. Each Custom Product Page leads with the feature that audience came for, then builds the next two screenshots around that story.
Custom Product Page: Meal planners
1. Start with the week ahead
Lead with the meal planner, the reason this audience clicked.
2. Bring the next recipe into the plan
Show the recipe-saving step that feeds the planning workflow.
3. Bring the wider recipe story together
Finish with the recipe-keeping introduction behind the planning workflow.
CookBook’s published App Store screenshots, reordered for each example Custom Product Page audience.
Match the campaign’s promise
Make the first screenshot deliver what the ad or search result promised. Keep the next two screens on the same useful story.
Localize for the campaign’s market
Translate and fit the captions in the saved variant, check longer and right-to-left headlines, and add local app images where the interface differs.
Create the CPP and upload its set
Create the Custom Product Page and upload its screenshots from AppScreens. After Apple approval, use its unique URL in the matching campaign, email or partner link.
Reach relevant App Store searches too. In App Store Connect, assign keywords from your latest approved app version to an approved, visible Custom Product Page for each language, and match its screenshots to that search intent.
PPOPPO or Custom Product Pages: Choose the Right Workflow
Scroll across to compare PPO and Custom Product Pages.
Product Page Optimization compared with Custom Product Pages
Decision
Product Page Optimization
Custom Product Pages
Customer goal
Improve the default product page with a controlled test.
Match a particular audience, campaign or search intent.
Creative assets
Alternative screenshots, app icons and app previews.
A distinct screenshot story, promotional text and app previews.
Destination and traffic
Original plus up to three treatments, shown to randomly selected eligible App Store visitors.
Separate pages with unique URLs, campaign routing and selected search keywords.
Limits
Up to three treatments per test. A test runs for up to 90 days.
Up to 70 Custom Product Pages per app, each with its own URL.
Results
Apple App Analytics reports the treatment results.
Apple App Analytics reports each page’s acquisition and conversion.
Your AppScreens workflow
Duplicate a set, create the PPO test and upload the treatment.
Build the audience’s first three screens, create the CPP and upload its set.
A targeted page is not the same as a controlled test
A campaign’s audience brings its own intent and traffic quality; use PPO when you want Apple’s randomized comparison against the default page. Apple does not run PPO tests on Custom Product Pages. Build CPP alternatives for your campaigns, and use the campaign’s testing setup to compare them.
One variant, the Apple outputs and markets it needs
Keep iPhone, iPad and Localized OutputsLocalized Outputs Together
Change the headline in the variant’s responsive project, then review its device and language sets. Keep the actual iPhone and iPad interfaces appropriate for each screen.
Fit the translated first impression
A longer German caption still needs a clear composition. Preview text, line breaks and app images together before delivering the treatment.
Keep the original and variants ready for the next release
Save each variant as its own project. When your app changes, reopen the sets you want to keep, update their captures and generate the next outputs.
Example: eight screens, two sizes and ten languages. Skip filling 20 screenshot galleries by hand for each variant. Keep each treatment in its own project.
Give each treatment a useful question
See the Exact Screenshot Changes Worth TestingWorth Testing
A clearer first headline
“Your recipes. Your week.” becomes “Plan your week in minutes.” The new caption gives the same app view a specific customer outcome.
Treatment, Headline test: First screenshot caption changes from “Your recipes. Your week.” to “Plan your week in minutes.”; App capture unchanged; Layout, colours and font unchanged.
TreatmentHeadline test
First screenshot caption
Your recipes. Your week.Plan your week in minutes.
App capture
Meal-planning calendarMeal-planning calendar
Layout, colours and font
UnchangedUnchanged
Screenshot order treatment: CookBook’s meal-planning screenshot moves from third to first, ahead of the recipe-keeping introduction.
Screenshot orderOriginalTreatment
12
23
31
44
A different first screenshot
Move the meal planner ahead of the broad recipe introduction. The app’s useful activity now leads the sequence, while the rest of the set explains how to get there.
A more relevant audience story
Recipe savers and meal planners want different first answers. Build the opening three screens around the campaign’s promise and give that audience its own Custom Product Page.
Create the Page or Test, Then DeliverDeliver the Screenshots
Create supported Apple CPP destinations and PPO tests from the AppScreens uploader. Prepare the page, select its destination and send the finished assets without rebuilding the set outside AppScreens.
Choose the Apple destination
Create a Custom Product Page or PPO test beside the designs you have prepared, then upload the selected device and language sets. Your creative is ready for Apple’s review and launch without a separate round of manual file uploads.
Add matching Apple Creative Assets
Carry the campaign’s message into product page headers and search results artwork. Create these assets in AppScreens alongside your screenshot set, then upload them to supported Apple destinations.
Turn Test Results into Better ScreenshotsBetter Screenshots
AppScreens gets the variants ready. Apple runs the randomized PPO test, reviews the creative and reports the results. Bring what you learn back into the next editable screenshot set.
Compare each CPP in its campaign and market context. Different audiences do not make a randomized test.
The same editable designs. Google’s own experiment workflow.
Create Screenshots for Google Play Store Listing ExperimentsStore Listing Experiments
Test the message on Google Play too. Create Android screenshot variants or a separate feature graphic in AppScreens, then export them for Store Listing Experiments in Play Console.
01
Prepare the original and variant assets
Duplicate the relevant screenshot project or your separate feature graphic project in AppScreens. Change one headline, app capture, sequence or graphic, then preview the Android outputs. Export the finished files for the languages and device classes you intend to test.
02
Set up the experiment in Play Console
Choose the listing and audience you want to learn about. Google runs the experiment; your AppScreens project keeps each design ready for further changes.
03
Add the exported variants and submit for review
Export your variants from AppScreens and add them to the experiment in Play Console. Experiment assets use Google’s Console workflow, separate from direct uploads to the main listing.
04
Choose the next set from the results
Read the experiment’s result before replacing the original listing. More data needed or Draw is a useful signal to keep the current set. When you choose an alternative, keep its editable AppScreens project for later app updates and localization.
See how captions, app captures and templates come together in AppScreens. Keep the original project, then use the same editing controls for your test or campaign variant.
“With 150+ templates, you instantly capture that pro store vibe. My favorite feature is definitely the 80+ language support. A lifesaver for those who want to play globally.”
“With 150+ templates, you instantly capture that pro store vibe. My favorite feature is definitely the 80+ language support. A lifesaver for those who want to play globally.”
“I don't think I could release my app without this tool. It single handedly creates all the output sizes I need to release my app to the Apple App Store and Google Play Store, from one design.”
“I don't think I could release my app without this tool. It single handedly creates all the output sizes I need to release my app to the Apple App Store and Google Play Store, from one design.”
Everything you need to ship your store listingyour store listing
AppScreens is an App Store and Google Play screenshot designer with a visual editor, guided AI, MCP for AI agents and a REST API. Adapt one editable project across device sizes and 80+ languages, then preview your results and export files or upload to App Store Connect and Google Play Console.
Can’t find the answer you’re looking for? Reach out to our customer support team.
PPO tests alternative assets against your default App Store page using Apple’s experiment system. A CPP gives a particular audience or campaign a separate page with its own screenshots and URL. Create both sets in AppScreens, then use the appropriate App Store Connect destination.
Apple supports up to three treatments alongside the original page. Start with the variations you have a clear reason to test, then use Apple’s results to decide what to keep.
Apple supports up to 70 additional Custom Product Pages per app. Build the pages your audiences and campaigns need, with distinct screenshot stories and suitable traffic routes.
Yes. Create supported Apple CPP destinations and configure PPO tests in AppScreens, then upload their screenshot sets. Choose the connected app, create or select the destination, preview the assets and send the set from AppScreens. Finish review and launch in App Store Connect, where Apple also reports the experiment results.
Yes. Edit translated captions and locale-specific app images in AppScreens, preview the localized design, then export or upload the selected outputs. AppScreens supports 88 languages.
Create and export Android screenshot variants in AppScreens, then use Google’s Store Listing Experiments for the Google Play test. Apple’s PPO and CPP features remain separate from Google’s experiment and custom-listing tools.
Choose AppScreens to keep your original design, test variants, device sizes and translations together. Duplicate the finished project, change the first headline, app capture or sequence, and create the PPO destination from the uploader. Upload the selected treatments directly to Apple, so your next test starts from editable work you already have.
Duplicate your screenshot project in AppScreens and make one focused creative change. Preview the required iPhone, iPad and language outputs. In Upload to App Stores, select your connected Apple app, use the plus beside Upload Target to create the PPO test, configure its name, traffic ratio and treatments, then select the treatment and upload. Complete Apple review and choose Start Test in App Store Connect.
No. New PPO screenshots go through Apple review without a new app version, and reordering already-approved screenshots needs no resubmission. Create and deliver the screenshot treatment from AppScreens. Alternate app icons have a separate requirement: they must already be included in the current app binary.
Apple supports a maximum of 90 days, with an earlier manual stop available. Use the duration estimate and choose the traffic share and localizations before starting. More treatments share the same allocated traffic, so start with one clear variation when traffic is limited. Use Apple’s conversion and confidence result to decide what to keep.
No. Apple’s native PPO tests run on the default product page, not Custom Product Pages. Create audience-specific CPP screenshot alternatives in AppScreens, then use your campaign or testing platform to control the traffic and evaluate them. A comparison between different audiences is not the same as Apple’s randomized PPO test.
Build a screenshot story that continues the campaign’s promise, localize it for the intended market and upload it to the matching CPP from AppScreens. Complete Apple review, then choose that approved page for the relevant ad variation in Apple Ads. Its unique URL also gives emails, partner links and other campaigns a focused destination.
A CPP deep link takes someone from the page’s promise to the matching feature inside your installed app on iOS or iPadOS 18 and later. Your app handles the link, and you configure and submit it for review in App Store Connect. Build the matching screenshot story in AppScreens so the campaign, store page and in-app destination communicate the same benefit.
Create your next screenshot variant screenshot variant
A new message should not mean a new production process. Keep your outputs and translations together, create the right Apple destination and get the next set ready in AppScreens.