Build one screenshot system for a Brazil launch, review Brazilian Portuguese and English versions, and export the phone or tablet presets that match the stores and devices your app supports.
Loved by 3,000+ creators
Pick a template, add accurate app screens, and localize the editable captions. Choose the relevant store presets when the design is ready.
5 slides · minimal
6 slides · bold
5 slides · bold
5 slides · minimal
Google Play accepts a range; Apple validates a defined list. Reuse the design, then choose and verify the outputs your release needs.
Google requires at least 2 screenshots across device types and allows up to 8 per type. JPEG or 24-bit PNG files must be 320–3840 px per side, with the longer side no more than twice the shorter side.
Make Play Store screenshotsApple publishes exact dimensions by display class. Current 6.9-inch portrait options include 1260 × 2736, 1290 × 2796, and 1320 × 2868. Match the output to the capture and listing.
Make App Store screenshotsPrepare iPad or Play tablet sets when the app supports those form factors. Use actual large-screen captures and check the current store guidance rather than stretching a phone composition.
Cover tablet sizesLaunch Pass and Pro can package multiple selected sizes and enabled locales into organized PNG folders. Review one sample from every device and language before uploading the full set.
Start your setVerify the current requirements in Google's preview-asset guidance and Apple's screenshot specification. For the design workflow, see the Play Store screenshot generator and App Store screenshot generator pages.
A Brazil-specific Portuguese version needs Brazilian vocabulary, product terminology, dates, pricing, and examples rather than a direct assumption that one Portuguese draft fits every market. Add the locale only when the app and support experience can serve it, and make sure the caption and underlying product capture tell the same story.
Screenhance includes Portuguese as a locale preset and can auto-translate editable English captions into a first draft. Have someone familiar with Brazilian Portuguese review the wording, tone, line breaks, and calls to action before publishing. The App Store screenshot translator explains the workflow, while our screenshot localization guide covers the editorial review.
Localization includes the interface and example data, not only the marketing caption. Show local details only where they exist in the product.
If the released app presents Brazilian pricing, use the matching R$ screen in that localized set. Do not alter a screenshot to imply pricing the product does not offer.
If the released app supports Pix, showing that real interface can explain the payment workflow. Never add a Pix option or claim to a mockup when the product does not support it.
Capture the local version of your app, with R$ amounts and Brazilian demo data, and drop those screens into the same template set. The layout stays on brand while the content reads local.
Move from source material to a polished launch asset without rebuilding the design in another tool.
Choose a visual template, a store-listing set, a Launch Kit, or an empty canvas for full control.
Add screenshots, photo scenes, device frames, text, icons, annotations, backgrounds, layers, and motion in the browser editor.
Download PNG, WebP, JPEG, GIF, WebM, or MP4, or export organized iOS, Google Play, and Chrome screenshot ZIPs.
Screenhance covers the full path from a raw screenshot or screen recording to coordinated, editable launch assets.
Use current device frames, stylized treatments, or photorealistic placements across phones, tablets, laptops, watches, TVs, print, apparel, and outdoor media.
Start with a complete composition for mockups, Product Hunt, OG images, website heroes, Play feature graphics, or Chrome Web Store promo assets, then edit every layer.
Create coordinated iOS, Google Play, and Chrome Web Store screenshot sets, edit localized copy across supported languages, and export organized PNG ZIPs, including fastlane-ready iOS folders.
Animate layers with editable motion styles and export GIF or WebM, or record and polish a product demo in Studio with frames, cursor motion, captions, audio, and MP4/WebM export.
Start with the store your release actually supports and use your own acquisition or customer data to prioritize work. For Google Play, prepare at least two valid screenshots across device types and consider Google's higher-resolution 9:16 or 16:9 recommendation for app discovery surfaces. The Play Store screenshot generator provides phone and tablet starting points.
If you also ship on iOS, reuse the visual system but choose an accepted Apple output and recheck the composition at that aspect ratio. The App Store screenshot generator flow lets you preview the iPhone or iPad canvas before export.
Add the Portuguese version where it matches your localization and support plan. Auto-translate the editable captions, review the Brazilian wording, and capture the localized product UI where available. Keep English and Portuguese in one project so the visual system stays consistent without treating the two versions as interchangeable.
Prioritize the stores your app supports and where your own acquisition or customer data shows demand. If you ship on both platforms, reuse the visual system but prepare separate outputs because Apple and Google validate different dimensions and device categories.
Google Play requires at least two screenshots across device types and allows up to eight per type; JPEG or 24-bit PNG files must be 320–3840 px per side with the longer side no more than twice the shorter. Apple publishes exact dimensions by display class; current 6.9-inch portrait options include 1260 × 2736, 1290 × 2796, and 1320 × 2868. Choose relevant Screenhance presets and verify both stores before upload.
Use the languages your support, onboarding, and in-app experience can serve. For a Brazil-specific Portuguese version, review vocabulary, tone, pricing, dates, and product terminology for Brazilian readers rather than assuming one Portuguese draft fits every market.
Yes. Portuguese is one of Screenhance's built-in locale presets, and Screenhance can auto-translate editable English captions. Treat the result as a draft: have someone familiar with Brazilian Portuguese review terminology, tone, line breaks, and the matching in-app capture before publishing.
Use those details when they are present in the released product. If the app offers Brazilian pricing, capture the matching R$ screen; if it supports Pix, show the real payment option where it helps explain the workflow. Never alter a screenshot to imply a price or payment method the app does not offer.
Yes. The free plan includes three watermarked PNG exports at 1× each month. The $6 Launch Pass includes ten clean static exports over seven days plus multi-locale and multi-size export; Pro adds unlimited clean exports for ongoing production.
You'll also need Play Store screenshots, a Product Hunt gallery, an OG image, and a website hero. Upload your screenshots once and Launch Kit generates them all, on-brand and matching.
Continue preparing the same App Store, Google Play, or Chrome listing.
Resolve the App Store Connect wrong-dimensions error
Start creatingLocalize App Store screenshots in 16 locales
Start creating1024×500 Google Play feature graphics
Start creatingPromo tiles, marquee, and screenshots
Start creatingCreate iOS and Android store visuals
Start creatingAndroid-ready Google Play visuals
Start creatingBuild one screenshot system, review Brazilian Portuguese and English variants, and export the selected store presets. Free to start.
%2FOlivia%20Rhye.webp&w=64&q=75){kind=small}
%2FPhoenix%20Baker.webp&w=64&q=75){kind=small}
%2FLana%20Steiner.webp&w=64&q=75){kind=small}
%2FDemi%20Wilkinson.webp&w=64&q=75){kind=small}
%2FDrew%20Cano.webp&w=64&q=75){kind=small}