Create App Store and Google Play screenshots in Screenhance

Use the Screenhance store editor to create coordinated App Store, Google Play and Chrome Web Store screenshot sets.

3 min readProduct-verified 20 August 2026By the Screenhance team

Need another answer?

Understand the store editor workspace from platform selection and slide design through localization and export.

01

How the store workspace differs

The store editor treats every slide as part of one listing. Platform, device size, enabled locales and export packaging apply across the set, while each slide keeps its own elements and copy.

ControlWhat it changes
iOS / Android / ChromeThe listing platform and valid canvas sizes
Device or surface sizeThe preview canvas and export requirements
Locale menuThe language currently shown and the enabled translation set
AI captionsDraft benefit-led copy across the screenshot story
Import listingBring existing iOS listing information into the workflow
Replace allMap a fresh batch of screenshots across the set
Export allCreate the selected sizes and locale folders as PNGs in a ZIP
02

Build each slide

  • Add creates text, callouts, numbered counters, screenshots and uploaded assets.
  • Templates applies a coordinated store-set design rather than a single loose artboard.
  • Text controls the selected headline, caption or callout styling.
  • Background controls each slide's color, gradient or background media.
  • Screenshots manages the product image, crop and device or browser treatment.
  • Assets adds supporting graphics; Layers controls visibility, locking and stacking.
03

Design the set as a story

  1. 1Lead with the most important outcome, not a welcome screen or logo-only slide.
  2. 2Give each slide one claim that the visible UI can prove.
  3. 3Keep type, margins, colors and frame treatment consistent across the set.
  4. 4Vary composition enough to create rhythm, but not so much that slides look unrelated.
  5. 5Preview the whole row at thumbnail size before polishing one slide in focus view.

Put this guide into practice

Sources and checks

We reviewed this workflow against the live Screenhance product. Platform-specific requirements are linked to their maintained primary sources.

Was this guide missing something?

Tell us what you were trying to do and which step stopped you. That helps us improve both the product and this guide.

Send guide feedback