Home Articles Tools & Indie Devs Batch-Producing Store Screenshots for China's Multi-Channel Android Stores (2026)

Table of contents

  • Quick nav

Was this helpful?

Share it with someone who needs it.

Batch-Producing Store Screenshots for China's Multi-Channel Android Stores (2026)

A
AppShot Maker
10/19/2026
Batch-Producing Store Screenshots for China's Multi-Channel Android Stores (2026)

The problem: six stores, six redesigns?

For overseas developers: in mainland China, Android apps are distributed through many phone makers' and platform stores rather than Google Play. Listing on Android in China usually means dealing with Tencent MyApp (应用宝), Xiaomi, OPPO, vivo, Honor, Huawei and other channels at once. Each has slightly different rules for the number, aspect ratio and file size of description images and whether device frames are allowed. If every release means "open Photoshop and Save As six times", an indie team is quickly worn down.

The goal should instead be: one logical master → automated export → channel-level compression and spot checks.

Step 0: Build a channel differences table (maintained in one place)

Record these in a spreadsheet or stores.yaml (sample fields; values per each console's current prompts):

ChannelDescription imagesMain ratioPer-image sizeIcon sizeOrientation ruleNotes
Tencent MyApp4–5Portrait 1080×1920 commonOften strictOften strictSizes should matchSearch carries big weight
Xiaomi≥3Portrait/landscapePer console512 commonTablet images can be uploaded separately—
OPPO3–5Portrait 1080×1920 commonPer consoleSquare corners——
vivo3–5Portrait or landscapePer consoleSize-sensitiveMust be all landscape or all portrait—
Honor3–5Docs commonly 9:16 / 16:9≤5MB rangeDocs commonly ≤200KBSingle orientationDevice frames must match
Huawei3–8Multiple specsPer consoleSpecial specsPortrait or landscape (per docs)Don't mix up with Honor's console

Write "per console" in the table header: third-party articles go out of date, so the table must be editable.

Step 1: The master contains only "logical frames"

Define for each frame:

  • frame_id (e.g. 01_hero)
  • Headline and subheadline
  • UI screenshot pixels (no device frame)
  • Whether a manufacturer device frame is allowed

Design rules:

  • Fix the headline safe area at the top 18%–22% so different channel crops don't damage the text.
  • Keep UI content away from the bottom gesture bar area.
  • Never hard-code channel names or competitors' store badges into the master.

Step 2: One artboard, then adapt

Recommended master artboard: 1080×1920 (9:16). Export matrix:

  1. master/01_hero.png … (no frame, uncompressed)
  2. framed/honor/... (only when the channel allows it and the device matches)
  3. export/<channel>/... (scaled to the target dimensions and compressed)

For landscape channels, create separate 1920×1080 logical frames alongside 1080×1920; don't stretch portrait images.

Step 3: Automate compression and naming

Suggested naming:

<app>_<version>_<channel>_<frame>_<WxH>.png

For example: moodjournal_1-2-0_vivo_01_hero_1080x1920.png

Compression strategy:

  • Export lossless PNGs first, then convert to JPEG (quality 82–90) or run pngquant to meet each channel's size limit.
  • Keep icons and screenshots in separate pipelines: icons often have much tighter KB limits.
  • Make CI or your local script fail on any oversized file, so large images never slip through.

Step 4: QA checklist (3 minutes per channel)

  • Image count is within the channel's range
  • All portrait or all landscape, no mixing
  • Image 1's headline is fully visible in the on-device details page preview
  • No competitor device designs, debug watermarks or unmasked data
  • Icon has square corners and meets the size limit
  • Copy matches the current version's features

Step 5: Release cadence

  • Major features: update frames 01–02 + the one-line summary.
  • Hotfixes: no need to change screenshots; just update the release notes.
  • Seasonal campaigns: use a separate campaign/ directory and switch back to evergreen/ after the campaign, so holiday assets don't linger.

Minimum setup when you're short-handed

Teams of two or fewer can standardize on:

  1. 4 permanent frames (hero, main path, differentiator, trust)
  2. Per channel, only run the compression script; no re-layout
  3. Once a quarter, compare competitors' details-page screenshots and adjust only the copy hierarchy

For batch headline application and multi-size export, you can generate the master with AppShot Maker and then feed it into your own compression script. The key: the master never goes to a store; only export does.

Separate the copy layer from the pixel layer

Batch production is usually slow because headlines are baked into pixels. A sturdier structure is:

  1. Pixel layer: UI screenshots, backgrounds, decorations (rarely changed)
  2. Copy layer: headlines, subheadlines, badges (changed often)
  3. Channel layer: file size, dimensions, whether to add frames (automated)

Render the copy layer at export time with a template tool or script. Then "changing just four headlines" doesn't mean recutting six sets of images. Put volatile information like version numbers and campaign dates in the store's "what's new" field whenever possible, rather than burning it into screenshots.

Rollback and archiving

Before replacing a store's images wholesale, keep the previous export/ archive for at least 30 days. If the new images hurt conversion, you can roll back within hours instead of redoing everything overnight. Name archive directories YYYYMMDD_version and record the "reason for change" (new feature / campaign / experiment).

We recommend noting each channel's "last approved icon MD5 / screenshot set ID" in your table, so you don't accidentally upload unapproved drafts when resubmitting.

Keeping it separate from iOS assets

If your product is also on the App Store, don't mix your China Android batch directories with your iOS ones. iOS has its own size set and review sensibilities; China's Android channels care more about file size and consistent orientation. Only the "logical frame copy" and UI source files are shared. Export device frames, corner radii and status bar styles separately to avoid "one set of images for everywhere" looking bad on both platforms.

Teams that only serve China's Android market can still reserve an empty en_export/ directory, so when they go global they can reuse the same logical-frame story and swap only the language layer.

Summary

The cost of multi-channel store images comes from "rule differences", not "design talent". A differences table + logical frames + automatic compression + quick QA turns six redesigns into one design. Treat the console prompts as the final truth and documented numbers only as starting values, and this workflow will keep working in 2026.

Ready to design your store screenshots?

Try AppShotMaker and turn raw captures into store-ready screenshots in minutes.

On this page

About 17 min read0%

AppShot Maker

App screenshot design tools

  • Ready-made layout templates
  • App Store, Google Play & Android sizes
  • Fast, simple PNG zip export