The task
You have 5-8 App Store / Play screenshots. Browsers see the first 1-2 before they decide to scroll, and they see the text overlay first — not the UI itself. Generic overlays (“Easy to use,” “Powerful,” “Beautifully designed”) kill installs. The job is short headlines (≤25 chars) and sub-lines (≤35 chars) that promise an outcome, not a feature, for each screenshot in the set.
When AI helps — and when it does not
AI is excellent at producing tight character-counted variants for each screenshot, varying angle (status, savings, transformation), and keeping voice consistent across the set. It is poor at knowing your real user’s pain — feed AI 2-3 actual review quotes that describe the outcome users praise; do not let it invent the benefit.
What to feed the AI
- Per-screenshot list: subject of the screenshot + intended message
- App category and primary outcome users seek
- 2-3 real review quotes describing what users love
- Brand voice (one sentence)
- Visual context — light or dark background, typography style
- Character caps: 25 for headline, 35 for sub-line (adjust per design)
Copy-ready prompt
Write App Store screenshot copy.
App and category: <line>
Primary outcome users seek: <line>
Real review quotes: <2-3 quotes>
Brand voice: <one sentence>
Visual context: <dark/light, type style>
Caps: headline ≤25 chars, sub-line ≤35 chars
Screenshots (subject + intended message):
1. <screenshot> — <message>
2. ...
For each screenshot return:
- Headline (≤25 chars, character count shown)
- Sub-line (≤35 chars, character count shown)
- One alternate headline (different angle)
- A note on which screenshot in the carousel this should be (first impression, mid-scroll, conversion)
Constraints:
- No "Easy to use," "Powerful," "Beautifully designed"
- Each headline names one outcome the user reaches
- The first 2 screenshots earn the scroll; the last 1-2 ask for the installFor localised stores: “Now adapt for <locale> — same outcome, idiomatic phrasing, recount characters in target script.”
Recommended output structure
A table: screenshot # / subject / headline / sub-line / character counts / alternate / carousel slot. The carousel slot matters — first impression copy is different from conversion copy.
How to check the output is usable
- Every headline counts to ≤25 chars and sub-line to ≤35 (verify yourself)
- The first screenshot promises an outcome strangers care about
- No generic adjectives passed through
- Voice is consistent across all screenshots
- The last screenshot is action-oriented, not feature-oriented
Common mistakes
- Generic adjective copy — “Easy. Powerful. Smart.” converts no one
- Same copy on the first and last screenshot — the carousel job is different per slot
- Headlines that need tap-to-zoom to read — browsers do not zoom
- Letting AI invent feature claims — verify against your real UI
- Forgetting localisation character counts — Chinese / Japanese / Korean break the English-sized layout
Practical depth notes
For How to Use AI to Write App Store Screenshot Copy: Headlines That Earn the Install, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.
After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How many screenshots? Apple allows 10; 6-8 is the sweet spot for conversion.
- Should the headline match the in-app UI? No — it sells the outcome, the UI shows the feature.
- A/B test screenshots? Yes. App Store Connect Product Page Optimisation supports this. Test the first screenshot’s headline.
Related
- App store listing prompts — title and description
- App onboarding copy AI — first-run copy users see after install
- App store screenshot copy prompts — additional copy variants
- App store review response prompts — replying to store reviews
- Product launch copy — broader launch copy
- Launch checklist — verify screenshots before publishing