Apple doubled your screenshot slots. You're using one.

Last October, Apple quietly doubled the limit on Custom Product Pages from 35 to 70. Google Play has allowed up to 50 Custom Store Listings for years. Between the two stores that's over a hundred screenshot sets you're allowed to ship — and the overwhelming majority of listings still use exactly one, the default.

What a Custom Product Page actually is

A Custom Product Page (CPP) is a second — or seventy-second — version of your App Store listing that lives at its own URL, with its own screenshots, preview videos, and promotional text. The app name, icon, and price stay locked to whatever the default listing says; only the visual pitch changes. You route specific traffic to it — an Apple Search Ads keyword, a link in a blog post, a QR code on packaging — and that traffic sees the tailored set instead of the generic one.

Since mid-2025 you can also assign existing keywords from your keyword field directly to a CPP, which lets it surface in organic search results, not just paid campaigns. That closes a gap that used to limit CPPs to ad traffic only.

Each CPP gets the same screenshot allowance as your default listing — up to ten images per device size class, plus up to three preview videos — and App Store Connect breaks out impressions, product page views, and conversion rate per CPP separately from the default listing's numbers. That per-variant data is the part worth paying attention to: it's not just a way to show a different set, it's a way to find out whether the different set actually converts better for that specific audience, and quietly kill the ones that don't.

Google's version does more, in one way

Google's Custom Store Listings work on the same principle — up to 50 per app — but they can swap more than screenshots: icon, short description, long description, and feature graphic are all fair game. Google also gives you more ways to target one: by country, by acquisition campaign (UTM source/medium), by referrer URL, by search keyword, or by whether the visitor already has the app installed. That last one is easy to miss and genuinely useful — a listing shown only to people who've already installed reads completely differently than one aimed at a cold visitor.

All five targeting types share the same 50-listing cap per app, and like Apple's CPPs, each one reports its own install and uninstall metrics in Play Console rather than folding into the default listing's totals. The practical difference from Apple worth remembering: because Google lets a custom listing change the app name and icon too, not just the screenshots, it's possible to run a genuinely different first impression per audience — not just a different pitch, but a different framing of what the app even is.

Why almost nobody uses more than one

Not because the upside is small. It's because building a second full screenshot set has historically meant redoing the whole design pass — new copy, new layout, new export sizes, times however many variants you want to test. For a solo dev or a two-person team, that's a day of work per variant, and a day of work for "maybe better conversion on a subset of traffic" loses to shipping the next feature almost every time. The feature isn't underused because it's not valuable. It's underused because the tooling around it assumed you had a design team.

Where the extra slots are actually worth spending

You don't need 70 variants. Three or four well-chosen ones already put you ahead of nearly every other listing in your category:

A paid-traffic variant. If you run Apple Search Ads or Google UAC on a specific keyword, build a CPP/listing that leads with the outcome that keyword implies. Someone searching "expense tracker" and someone searching "budget for freelancers" want to see a different first frame, even in the same app.

A campaign-specific variant. Whatever you're linking from a newsletter, a Product Hunt launch, or a creator's bio, point it at a listing that echoes the specific pitch that got them to click — not the generic set everyone else sees.

An installed-user variant (Google). Use the install-state targeting to show existing users a "what's new" style page instead of a first-time pitch, if they land back on the listing from a search or a share link.

A country or locale variant. Even before you localize the app itself, a screenshot set with translated headlines for your top non-English market is a small lift with an outsized first impression.

The real blocker is speed, not strategy

The hard part was never deciding you want a paid-traffic variant or a country variant — it's obvious those would help. The hard part was that building each one meant a fresh design pass. That's the actual reason a hundred available slots turn into one used slot in practice.

This is exactly the gap ShotCanvas closes: design your default set once, then spin up a variant by swapping the headline, palette, or lead frame in minutes instead of redoing the layout from scratch — and export at the exact pixel sizes both stores expect for every CPP or Custom Store Listing you ship.