Table of contents
- Quick nav
App Store Screenshots: Portrait or Landscape?
The short answer
For most phone listings, prepare portrait screenshots. Store product pages on a phone are built around a tall first card. A landscape image is usually letterboxed or cropped, so your headline and UI shrink and the first impression looks empty.
"Must it be portrait?" is not a single global law. What stores care about is: exact pixel sizes for the slot, orientation that matches how the app is actually used, and not faking a cinematic landscape for a portrait-first utility.
Platform cheat sheet
| Store | Default for phones | When landscape is fine | Common failure |
|---|---|---|---|
| Apple App Store | Portrait for phone display sizes | Only if the app runs primarily in landscape (some games, timeline editors) | Portrait apps uploaded as landscape "posters" — risk under Guideline 2.3 |
| Google Play | Either orientation if the aspect fits the slot | Landscape games may submit landscape sets | Mixing portrait and landscape in one phone set feels broken while scrolling |
| China Android markets (Huawei, Xiaomi, OPPO, vivo, Yingyongbao, …) | Almost always portrait phone shots | A few game pipelines accept landscape creatives — follow each console validator | Putting a promo banner into the screenshot slot and failing size checks |
| Tablet / iPad | Follow the tablet slot (often wider) | Landscape layouts are natural on iPad | Stretching phone portrait frames into iPad slots |
For pixels and required classes, use App Store screenshot sizes 2026 and Google Play screenshot requirements. This article is only about orientation.
Decision tree
- Everyday use is portrait (social, tools, shopping, productivity) → portrait only.
- App locks to landscape → submit real landscape UI; do not rotate a portrait recording.
- Both orientations supported → lead with the orientation users see most often after launch; keep the rest of the set consistent.
- Portrait splash, landscape core loop → first screenshot should show the core loop, not a logo splash that disagrees with frame two.
Why portrait usually converts better
- The phone product page card is tall; portrait fills height so caption + UI share one glance.
- Thumb reach and how people hold the phone match portrait mock CTAs.
- For multi-channel China uploads, one portrait master set ports to more consoles with fewer "wrong orientation" rejects.
Landscape is not "bad" — it is wrong for many categories. Use it when you need width: timelines, split HUDs, maps. On a notes app it only makes type smaller.
Games vs utilities
| Category | Recommendation | Note |
|---|---|---|
| Portrait casual | All portrait | Matches short-video holding habits |
| Landscape action / "console feel" | All landscape (or lead landscape) | Match real play; promo banners are not the screenshot slot |
| Tools / productivity / B2B | All portrait | Rare exceptions |
| Video / editors | Portrait first-open + optional one landscape timeline | Avoid five timeline close-ups |
More narrative contrast: game vs utility screenshots.
Pre-upload checklist
- Width/height match the target slot (do not rely on auto-rotate)
- UI orientation matches a real device session; status bar / home indicator agree
- No portrait/landscape flip-flop inside one device set
- Landscape type stays readable when the card is shown in a tall phone layout
- China Android consoles that say "portrait only" are obeyed literally
Frames and safe area
After orientation is fixed, handle bezels and notch / Dynamic Island safe areas — see device frame rules. If you batch-export sizes in the browser, lock a portrait artboard first in AppShot Maker so you never rotate a finished PNG (that softens edges).
Multi-channel orientation strategy
China Android uploads often hit Huawei, Xiaomi, OPPO, vivo, and Yingyongbao in one week. Practical rules:
- Keep a portrait phone set as the single source of truth.
- If a game console allows landscape slots, isolate
landscape-game/— never mix with utility portrait packs. - Export tablet/iPad slots separately; do not stretch phone frames.
- Keep paid social landscape creatives in
ads/, not in the store uploader.
Many “wrong size” rejects are really width/height swapped. Check file properties before you blame the console.
Official docs to keep open while you decide
- Apple App Store Connect help on screenshot specifications (required device classes and accepted pixel sizes).
- Google Play Console help on store listing graphic assets (phone/tablet counts and formats).
- Each China Android console’s “素材规范” PDF — orientation is often stated as 竖图 only even when pixel ranges look flexible.
When orientation and pixel size conflict in a validator message, fix orientation first, then re-export to the exact pixel box. Guessing a crop on an already-rotated PNG usually softens type and fails the next checksum.
Takeaway
For most phone apps the answer to "portrait or landscape?" is portrait. Use landscape only when the product truly runs that way, and keep the set consistent. Wrong orientation hurts conversion first and can look like "not actual use" in review. Decide orientation with the tree above, then optimize copy and the five-frame story.