App Store Screenshot Captions: How to Write Copy That Converts (With 40 Examples)

Most of the design work in a screenshot set is done by the template. Most of the conversion work is done by six or seven words at the top of each image. Those words are the App Store screenshot captions, and they are the part of the listing developers spend the least time on and the part that moves install rate the most.

This guide is about the copy only: what a caption has to do, a formula that produces good ones fast, the limits that keep them readable, the rules Apple enforces, and forty examples you can adapt. For layout, sizes and the rest of the set, see the guide to screenshots that convert.

What a Caption Has to Do #

On the product page, a visitor scrolls the screenshot carousel in a second or two. In search results, only the first one to three screenshots show at all, at a size where the app's actual interface is barely legible. The caption is the only text large enough to read at that scale, so it carries the whole message.

That gives a caption three jobs, in order:

1. State one benefit the user gets, in their words, not yours.
2. Be readable at thumbnail size, which means short and high-contrast.
3. Match the screen below it, so the image proves the claim.

A caption that does all three is a promise with evidence attached. A caption that does none of them is a feature name floating over a screenshot, which is what most listings have.

The Formula: Benefit, Then Proof #

The fastest way to a good caption is to write the feature first, then translate it.

The pattern is the same every time: drop the noun that names the feature, and say what changes for the person using it. If you cannot find the benefit, the feature may not deserve a screenshot.

Verbs beat nouns. "Track subscriptions" is a feature. "Never miss a renewal" is a result. Captions that start with a verb or a "never" or "always" read as outcomes.

Specifics beat adjectives. "Powerful search" says nothing. "Find any note in under a second" says something a reader can picture. Numbers work the same way, as long as they are true and will stay true.

The Limits That Keep Captions Readable #

A caption competes with a phone frame for a canvas that is shown at a fraction of its size. These are the limits that hold up in practice.

• Six to eight words. Two short lines at most. Past eight words the type has to shrink, and at search-result size it becomes noise.
• Under 40 characters per caption, which is roughly the same limit in a different unit. Long words in German and Finnish push against this hardest; see the localization note below.
• One idea per screenshot. If the caption contains "and", it is two screenshots.
• Consistent length across the set. A four-word caption next to a nine-word caption looks like an accident. Vary within a word or two.
• Sentence case, not Title Case. "Never miss a renewal" reads like a person talking. "Never Miss A Renewal" reads like a slide deck. Either is allowed; sentence case converts better in most tests because it is faster to read.

A quick test: shrink the screenshot to the height of your thumb and squint. If you can still read the caption, it is short enough and large enough.

The First Screenshot Is a Different Job #

Apple shows the first one to three screenshots in search results, and the first one is what a visitor sees before deciding to tap through. Its caption has to do more than describe a feature: it has to say what the app is and why this one.

Good first captions are the app's promise in a handful of words.

• "Budget together, without the spreadsheet"
• "Every subscription, one screen"
• "Screenshots for the App Store in minutes"
• "Your reading list, finally under control"

Bad first captions are feature names, welcome messages or the app name repeated. "Welcome to Budgetly" tells a searcher nothing they did not already know from the icon.

A useful structure for the set: screenshot one is the promise, screenshots two to four are the three strongest benefits in order, and anything after that is for people who are already convinced and want detail.

What Apple's Guidelines Say About Caption Text #

Captions are explicitly allowed. Guideline 2.3.3 permits text and image overlays on screenshots as long as the app itself is shown in use. The constraints come from elsewhere in the rules, and they are all about honesty. The full set is in Apple's screenshot guidelines explained; the parts that touch copy:

• No prices or terms in the image. "Only $2.99" or "7-day free trial" falls under Guideline 2.3.7 and goes stale the day the price changes.
• No claims the build cannot back up. A caption for a feature that ships next month is a 2.3.1 rejection.
• No rankings or awards you cannot substantiate. "#1 budgeting app" needs to be true somewhere specific, and even then it ages badly.
• Nothing that fails a 4+ rating regardless of the app's own rating.

"Best", "fastest" and "the only" are not banned, but they invite scrutiny. "Never miss a renewal" is a promise your app keeps. "The best subscription tracker" is an opinion a reviewer can question.

Forty Caption Examples by Category #

These are written to be adapted, not copied. Swap the noun for yours and check the claim is true for your app.

Productivity and tasks

1. Today, actually planned
2. Capture it before it's gone
3. Finish what you start
4. One inbox for everything you owe
5. Plan the week in two minutes

Finance and budgeting

6. Know where every dollar went
7. Never miss a renewal
8. Budget together, not separately
9. See the month before it happens
10. Every subscription, one screen

Health and fitness

11. Streaks that survive bad days
12. Log a workout in three taps
13. Sleep, explained
14. Small habits, tracked honestly
15. Your progress, week over week

Notes and writing

16. One line a day
17. Write, don't configure
18. Find any note in under a second
19. Your notes, nowhere but your device
20. 128 days and counting

Travel and lifestyle

21. Stay somewhere worth the trip
22. Book great homes around the world
23. Do what only locals know to do
24. Pack once, forget nothing
25. Every trip, one itinerary

Social and community

26. Be first to know
27. Find your community
28. Join the conversation
29. Ask anything, get real answers
30. Every question has a thread

Photo and creative

31. Edit like you mean it
32. From camera roll to store-ready
33. Frames, captions and sizes, done
34. One design, every device
35. Ship it in forty languages

Developer tools and utilities

36. Works on the plane
37. Only you can read it
38. Pick up where you left off
39. Upload straight to App Store Connect
40. Set it once, forget it exists

Several of these are the sample captions shipped with the built-in templates in Screenshot Studio, which is a reasonable place to start if you want to see them on a real canvas.

Captions in Other Languages #

A translated screenshot set outperforms an English one in every non-English storefront, and the caption is the only thing that needs translating. Two things change when you localize:

• Length changes. German and Finnish run 30 to 40 percent longer than English; Japanese and Chinese run shorter. A caption written at eight English words will overflow in German. Write at six and you have room.
• Idioms do not travel. "Pick up where you left off" translates literally into nonsense in several languages. Prefer plain statements of benefit; they translate cleanly.

Screenshot Studio translates captions with built-in AI and keeps the layout consistent when the text changes length, so the German set does not need a separate design. The workflow is in the localization guide. For your top two or three markets, have a native speaker read the captions once before you ship.

Writing Captions With an AI Assistant #

Caption copy is pure text, which is what language models are best at. A good prompt gives the assistant the feature list and asks for benefit-led captions under eight words, then you keep the ones that are true. If Screenshot Studio is connected to Claude Code or Cursor over MCP, the assistant can write the winners straight into the document and render a preview. What it cannot do is know which claims your app can back up, so read every caption before it ships. More on the limits in what AI actually does for screenshots.

Emphasis Without Clutter #

One word in a caption often carries the meaning: "Never miss a renewal", "Only you can read it". Highlighting that word in the brand colour draws the eye without adding a second line. In Screenshot Studio, wrap a word in asterisks in the caption field and it renders highlighted. Use it on one word per caption at most; two highlights cancel each other out.

Test the Caption, Not the Layout #

If you change one thing in a product page optimization test, change the first caption. It is the highest-leverage variable on the page and the cheapest to swap. The A/B testing guide covers how to set the test up in App Store Connect and how long to run it.

A Caption Checklist #

Before export, run each caption through this list.

1. States a benefit, not a feature name.
2. Eight words or fewer, under 40 characters.
3. One idea, no "and".
4. True for the build being submitted.
5. No price, trial length, ranking or award.
6. Matches the screen below it.
7. Same length and tone as the rest of the set.
8. Translates without an idiom.
9. Readable when the image is the height of your thumb.
10. The first one says what the app is.

Conclusion #

Screenshot captions are the cheapest copy you will ever write and the most-read. Give each one a single benefit in six to eight honest words, make the first one the app's promise, keep prices and superlatives out, and translate them for every market you sell in. Download Screenshot Studio to put them on a template that reads at thumbnail size and ships in every language.