Shipshot guide
How to Show a Paid App or In-App Purchases in Store Screenshots
A screenshot should make the product understandable without making the purchase model ambiguous. Whether the app is paid, free with in-app purchases, or includes separately purchased items, show the product experience first and state the relevant access context accurately.
Start with the product experience
Use a real screen that demonstrates the app's main job. A price or plan reference can be part of the story, but it should not replace the product evidence. Keep the first frames focused on what the customer will actually use after installing or purchasing the app.
- Choose the product state that explains the core value.
- Show the action or result a customer can find in the submitted build.
- Keep pricing language separate from claims the screen cannot prove.
Make additional purchase context clear
Apple's metadata guidance says that when a screenshot features an item that requires an additional purchase, you should make that clear. Apply the same discipline to captions and visible product UI: do not make an optional paid item look like it is included for everyone.
- Mark which visible feature or item requires an additional purchase.
- Use direct wording that distinguishes included and paid access.
- Check the caption against the purchase flow in the submitted build.
Separate paid and free paths
A paid app, a free app with in-app purchases, and a free app with a subscription can have different first-use paths. Choose screenshots that match the access model the store listing describes. Avoid showing a locked state as if it were the complete product, or a premium screen as if no purchase decision exists.
- Map each screenshot to the access state it represents.
- Label a locked, trial, subscription, or separately purchased item when the distinction matters.
- Keep the store copy and screenshot copy consistent with the actual offer.
Localize the offer carefully
Pricing, plan names, and purchase terms need language review just like other caption copy. Keep product-owned names and identifiers intentional, and do not let a translated caption change whether a feature appears included or optional. Review the wording with the person responsible for each locale.
- List purchase terms and names that need a locale-specific review.
- Check translated captions against the product's actual access states.
- Inspect line breaks so purchase context is not hidden or clipped.
Review checklist
Questions to ask before handoff
Should a paid app put its price in a screenshot?
Only when it helps explain the product and remains accurate for the listing. Keep the product experience visible and do not turn the screenshot into a price-only frame.
Do I need to mention every in-app purchase?
Make additional purchase context clear when a featured item requires it. Keep the screenshot sequence focused on the product rather than listing every transaction.
Can a screenshot make a premium feature look included?
It should not. Match the caption and visible state to the actual access model and identify an additional purchase when it is relevant to the featured item.
