← Blog

How to automate screenshot resizing for iOS and Android in 2026

Published: July 5, 2026

Version française →

Every time you update your app's screenshots, you face the same problem. One source image. Several required formats. Two stores with different specs. And Photoshop open in the background.

This article covers the exact screenshot size requirements for both the App Store and Google Play in 2026, the manual workflow most developers are still grinding through, and how to replace it with something that doesn't eat an afternoon.

Why screenshot resizing is still painful in 2026

The App Store and Google Play don't share a single required dimension. Apple accepts iPhone screenshots at the 6.5" display (iPhone 11 Pro Max era) and the 6.7" display (iPhone 14/15 Pro Max) and auto-scales them upward to fill the 6.9" (iPhone 16 Pro Max) preview — so you don't strictly need a separate 6.9" set. iPad has its own requirement on top of that. Google Play adds its own phone and tablet specs.

That's several distinct output sizes before you've touched a line of metadata.

Most developers handle this in Photoshop or Figma: open the source, resize, export, rename, repeat. If you ship on both platforms simultaneously, you run through this twice per update cycle. Three or four apps in your portfolio and the math gets ugly fast.

The tedium isn't even the worst part. The worst part is uploading the wrong size, triggering a rejection, and losing a day to a resubmission.

The required screenshot sizes in 2026

Here's what a standard dual-platform release actually demands:

Apple App Store

  • 6.5" display — 1242 × 2688 px (some devices report 1284 × 2778 px)
  • 6.7" display — 1290 × 2796 px
  • iPad Pro 12.9" — 2048 × 2732 px (required when your app declares iPad support)

Apple's rule is "at least one iPhone set." It auto-scales your 6.5"/6.7" screenshots upward to fill the 6.9" (1320 × 2868 px) preview, so a distinct 6.9" set is optional, not required. Most developers upload 6.7" (and often 6.5") and let Apple handle the rest.

Google Play

  • Phone screenshots — minimum 320 px on the short side, maximum 3840 px on the long side, aspect ratio between 16:9 and 9:16
  • 7-inch tablet — recommended
  • 10-inch tablet — recommended

Google Play is more flexible on exact pixel dimensions, but the aspect ratio constraint still means your Apple screenshots won't drop in without cropping or padding.

The manual workflow most developers use

  1. Design the screenshot at the largest reference size (typically 1320 × 2868 px for the 6.9" display)
  2. Open Photoshop or Figma
  3. Resize the canvas for each subsequent size, adjust the layout, export
  4. Repeat for Google Play's aspect ratio
  5. Rename files to match each platform's expected convention
  6. Upload to App Store Connect
  7. Switch tabs, upload to Google Play Console
  8. Realize you forgot the iPad size — back to step 2

This is the workflow that eats the most time per release cycle. It's not complicated. It's just repetitive, error-prone, and entirely manual.

How to automate it

A few approaches exist, depending on how much setup you're willing to absorb.

Option 1: Fastlane's snapshot and frameit

Fastlane can automate screenshot capture with snapshot for iOS and screengrab for Android. Write a Snapfile, configure your simulators, let it run. frameit layers device frames on top.

The catch: you write and maintain the scripts. When your UI changes, your screenshot scripts often need updating too. There's no GUI. For a solo developer managing two or three apps, the setup cost is real — and the maintenance overhead compounds over time.

Option 2: Design tool plugins

Figma and Sketch both have plugins that export at multiple sizes from a single artboard. That trims the export step, but you're still managing source files, still uploading to two separate consoles, and still handling the Google Play aspect ratio difference by hand.

Faster than pure Photoshop — but not automated. You're still in the loop for every step.

Option 3: A unified publishing tool that handles resizing as part of the workflow

This is where the approach changes. Instead of treating screenshot resizing as a standalone design task, you treat it as part of publishing.

OneStorehandles this directly. Drop one HD screenshot. Every required format — iPhone 6.5" and 6.7", iPad, and Google Play phone and tablet sizes — comes out the other side, and Apple auto-scales those to cover the 6.9" preview. You don't open Photoshop. You don't manage a stack of export presets. Upload once — the platform produces what each store needs.

This matters most when you're shipping updates frequently or managing multiple apps. The time saved compounds. And because resizing happens inside the same tool where you edit metadata and upload your .ipa or .aab, the entire publishing workflow stays in one place.

What the automated workflow actually looks like

With resizing handled natively, the workflow collapses:

  1. Upload your highest-quality source screenshot
  2. OneStore outputs 6.5", 6.7", iPad, and Google Play formats automatically — and Apple fills the 6.9" preview by scaling up
  3. Review the outputs in the same editor where you're editing your title, subtitle, and description
  4. Publish to both stores from one interface

No tab-switching between App Store Connect and Google Play Console. No manual exports. No renaming files.

For teams shipping on both platforms simultaneously, that's the practical difference between a half-day task and a 20-minute one.

What to look for in a screenshot automation tool

Not every tool that claims to handle screenshots actually closes the loop. A few things worth checking:

Does it output all required sizes?Some tools cover iPhone but not iPad, or Apple but not Google Play. You need iPhone 6.5" and 6.7", iPad, and Google Play phone and tablet in one pass.

Is it connected to actual publishing? A tool that resizes screenshots but still requires you to upload manually to each console solves half the problem. The real efficiency gain comes when resizing and publishing are the same step.

Does it handle metadata too?If you're already editing your App Store title (30 characters) and Google Play title (30 characters) with live counters in the same editor, screenshots in that same interface means one fewer context switch per release.

What happens to your credentials? If the tool needs your .p8 API key or Google service account JSON, ask where those are stored. OneStore keeps credentials in an AES-256-GCM encrypted vault at the application layer. A Data Processing Agreement based on EU Standard Contractual Clauses is available on request at onestore.so/dpa.

Screenshot resizing is one piece of a larger problem

Screenshot resizing gets attention because it's visually obvious tedium. But it sits inside a bigger workflow problem: managing two stores separately.

You resize screenshots twice because you publish to two stores. You check reviews twice because they come in through two consoles. You copy-paste metadata because App Store Connect and Google Play Console don't talk to each other.

Solving screenshot resizing in isolation helps. Solving it as part of a unified publishing workflow — one that covers metadata editing, binary upload, and review management — helps more. That's the difference between a Figma plugin and a tool that handles the full cycle.

If you want to see where your current store listing stands before you start optimizing screenshots, the free Store Listing Audit scores your listing out of 100. No account required, no email needed.

FAQs

What screenshot sizes does the App Store require in 2026?

Apple's rule is "at least one iPhone set." It accepts 6.5" and 6.7" screenshots and auto-scales them up to fill the 6.9" (iPhone 16 Pro Max) preview, so a separate 6.9" set is optional — plus iPad Pro if your app supports iPad.

Can I use the same screenshots for iOS and Android?

Not directly. Apple and Google Play have different aspect ratio requirements. An Apple screenshot won't drop into Google Play without adjustment — you need platform-specific outputs from your source image.

Does Fastlane automate screenshot resizing?

Fastlane's snapshot and screengrab actions automate screenshot capture from simulators, and frameit adds device frames. Setup requires CLI scripting with no GUI. For developers who want a no-script approach, a unified publishing tool is the more practical option.

What's the minimum image quality I should start with?

Start from the largest display — the 6.9" reference at 1320 × 2868 px. Downscaling from a high-resolution source produces cleaner results than upscaling from a smaller one.

How does OneStore handle screenshot resizing?

You upload one HD screenshot. OneStore outputs iPhone 6.5" and 6.7", iPad, and Google Play formats automatically — inside the same editor where you manage metadata and upload your binary — and Apple scales your iPhone set up to cover the 6.9" preview.

Is automated screenshot resizing only useful for large app portfolios?

No. Even with a single app, the time saved per release cycle adds up. If you ship updates monthly across iOS and Android, automated resizing removes a repeatable manual task from every release.

Does OneStore's free plan include screenshot resizing?

Yes. The free plan covers 3 apps, both stores, and requires no card. Screenshot resizing is part of the core publishing workflow, not a paid add-on.