App Store and Google Play Screenshots, Videos and Metadata Done Right

The asset checklist for both stores

Screenshot sizes without the guesswork

Apple asks for one set per display class but only requires the largest current iPhone class – at the moment the 6.9-inch display, 1320 × 2868 pixels in portrait – and, if the app supports iPad, the 13-inch iPad class at 2064 × 2752 pixels. Smaller devices are scaled from these. New iPhone generations occasionally change the required class, so check the screenshot specifications in App Store Connect before you export.

Google Play accepts PNG or JPEG screenshots with sides between 320 and 3,840 pixels, where the long side may be at most twice the short side. Provide tablet screenshots if you want the app presented well on large screens.

Practical tips:

• Design the first two or three screenshots for the search results view – most people never swipe further.
• Use one clear benefit per screenshot with a short caption, and show the real interface.
• Never upload stretched iPhone screenshots as iPad screenshots. Reviewers notice.
• Keep source files in a design tool or generate them with Fastlane snapshot so updates for new languages and UI changes stay cheap.

Preview videos

Apple's app previews must consist of footage captured from the app itself, 15 to 30 seconds long; they autoplay muted in search results, so the first seconds and on-screen captions matter. Google Play uses a YouTube link shown above the screenshots. A video is optional on both stores – a weak one is worse than none.

Keywords, subtitle and localization DE/EN

On the App Store, the name, subtitle and keyword field are the main search signals. Separate keywords with commas, skip spaces and avoid repeating words already in the name. On Google Play, the title, short description and full description are indexed, so write natural sentences that contain the terms people search for, without stuffing.

Localization is more than translation. Each language has its own keyword field and character limits, and German compound words consume them quickly. German users often search with English terms for tech categories as well, so research both. Localize screenshot captions too; English captions on a German listing look unfinished. Decide early whether your German copy uses “du” or “Sie” and keep it consistent with the app.

What triggers metadata rejections

• Screenshots that do not show the app in use – only splash screens, login pages or marketing art (Apple Guideline 2.3.3).
• Trademarks, competitor names or prices in the name, subtitle or keywords (2.3.7).
• References to other platforms, such as Android device frames or “also on Google Play” (2.3.10).
• Assets not suitable for a 4+ audience, even if the app has a higher age rating (2.3.8).
• On Google Play: ranking or price claims such as “#1”, “best” or “free” in the title, icon or developer name, misleading calls to action, and unrelated keyword lists in the description.

The full rules are in the App Store Review Guidelines; Google's equivalent is the metadata section of its developer program policies.

How jocapps can help

appsubmitter.io checks your listing against store rules with AI-assisted checks and App Specialists, prepares screenshots and metadata in your own accounts and handles rejections. UXreviewer.io complements this with a UX report on your app or onboarding – commented screenshots and concrete improvement ideas within 10 business days – so the screens you advertise are the ones users enjoy. For search visibility after launch, read our guide on app store optimization, or book a free 30-minute call via the meeting planner.