App Store and Play Store screenshot specs

Store specs change without notice. Apple's documents, A1 and A2, were rechecked on 2026-08-27, and the next scheduled recheck is 2026-11-25, on a 90 day cycle. If you are reading this after that date, open the links above and confirm the numbers yourself. That recheck was not a formality: the iPhone 6.3" size had changed.

No blog posts or summary sites were used as evidence. Where the official documents state no value, this article leaves the cell empty and says so.

So this article keeps two things apart. The first half is what the stores require. The second half is what this editor actually produces, compared against those requirements row by row.

First, the most common misconception

You will often read that store screenshots must not sit inside a device frame. That rule does not apply to phone and tablet screenshots.

In Google's documentation the sentence appears only in the Wear OS and watch face section.

Not position the screenshots within device frames, or include additional text, graphics, or backgrounds that are not part of the interface of the app.Source G1

The phone, tablet, and Chromebook sections carry no such restriction, and Apple's documents contain no frame rule at all. Watch apps are the only case that needs care.

Apple (App Store)

Rules that apply to every size

• Count: 1 to 10 screenshots
• Formats: .jpeg, .jpg, .png
• Alpha channels and transparency are not allowed
• File size cap: Not stated in the source, in either A1 or A2, so this article leaves it blank

You can upload one to 10 screenshots in .jpeg, .jpg, and .png formats. Images can't include alpha channels or transparencies.Source A1

Both sentences are in A1. The count and the formats are cross checked in A2, which states the same rule in different words: "You can upload a minimum of one and a maximum of ten screenshots in .jpeg, .jpg, and .png formats." The alpha channel sentence, however, appears in A1 only and is not in A2. This was confirmed by rereading A2 on 2026-08-27, correcting an earlier version of this article that presented both sentences as cross checked.

Why one set of sizes is enough

provide only the highest resolution screenshots required. They automatically scale down to smaller device sizes.Source A2

Upload the largest size once and the smaller device sizes are generated by scaling down. There is no need to produce eight separate iPhone sets. If you would rather not use the scaled versions, add specific screenshots for other device sizes and localizations in Media Manager (A2). Note the condition attached to the quote above: it applies when the interface is the same across device sizes and localizations. If your app looks different per device, build the sizes rather than leaning on the scaling.

That is Apple's requirement. Whether this editor can produce the one set it asks for is a separate question, and the comparison tables further down answer it.

iPhone

For landscape, transposing each pair works for most rows. The 4" and 3.5" sizes, which have a no status bar variant, are the exception. The landscape counterpart of the 4" portrait 640 × 1096 is 1136 × 600, not 1096 × 640. If you need those two, read the landscape column in A1 directly.

iPad

Mac, Apple TV, Vision Pro

Apple Watch

You must use the same screenshot size for Apple Watch consistently across all localizations for the app.Source A1

Google (Google Play)

Apple asks for fixed pixel dimensions per device. Google works differently and defines a minimum, a maximum, and a ratio. The two approaches do not merge into one table, so they are kept apart here.

App icon and feature graphic

Screenshots

File size caps are mostly undocumented

Across A1, A2, and G1 there are exactly two stated file size limits.

Apple states no screenshot file size cap, and Google states none for the remaining assets. The figures that circulate online have no traceable source. If an upload is rejected, shrink the file then.

What this editor can actually output

The tables above are what the stores require. They are not a list of what this editor can produce. So here is our side of it, written out plainly and set against those store specs.

Canvas size comes from the format preset. There is no field for typing your own pixel values, and the format panel offers four canvas sizes: 1080 × 1080, 1200 × 1200, 1600 × 1000, and 1920 × 1080. No format uses a portrait canvas.

All 18 formats apply the moment you press them, and every one of them uses one of the four canvases above.

Multiply those four by the export scales of 1x, 2x, 3x, and 4x and the resulting 16 sizes are everything this editor can produce. Output size is canvas size times scale, and the export panel prints that number as you pick it.

Against Apple's specs

Apple asks for fixed pixel dimensions per device. For iPhone and iPad the required aspect ratio itself differs from every canvas here, so no combination of scales gets there.

In short, screenshots destined for iPhone, iPad, or Mac cannot be built here. On the Apple side the exact matches are Apple TV and Vision Pro.

Against Google's specs

Google defines ranges and ratios instead of fixed pixels, which is why so much of what this editor exports passes as it stands.

Phone, tablet and Chromebook, and Wear OS screenshots for Google Play can be uploaded exactly as this editor exports them. Wear OS is the one place the device frame restriction applies, so export those without a frame (G1).

If you need exact iPhone pixels

This editor does not get you there. Build the mockup, download it, then resize the file to 1320 × 2868 or whichever size you need in another tool. The ratios differ, so resizing means cropping or padding, and the composition shifts accordingly. Better to know that step is coming before you start.

If you came here for portrait iPhone screenshots, this is where it stops. As of today the facts are these: no format uses a portrait canvas, and there is no custom pixel entry.

Practical notes when you build these from a mockup

• Do not export on a transparent background. Apple does not allow alpha channels (A1), and Google asks for alpha free formats on everything except the icon (G1). Turn the transparency option off and set a background color. This editor already satisfies that condition.
• What the store requires: for Apple, build the largest size only (A2). What we provide: if that one set is an iPhone or iPad size, this editor cannot produce it. The Apple targets it can hit exactly are Apple TV, at 1920 × 1080 and 3840 × 2160, and Vision Pro, at 3840 × 2160.
• What the store requires: for Google phone screenshots, any size within a 3840px long edge is fine (G1). What we provide: ten of the sixteen export combinations sit inside that range and can be submitted unchanged.
• The device frame restriction applies to watch apps only (G1). Drop the frame on the 1:1 exports you intend for Wear OS.
• For the targets whose specs cannot be met here, meaning iPhone, iPad, Mac, Automotive, and the feature graphic, the only route is to download an export and resize it in another tool.

In this editor the transparent background option is off by default, and choosing JPG locks the option outright. Export it as it stands and the file carries no alpha channel, sitting on the background color you picked. Downloads carry no watermark, so a file that meets the specs above can be submitted unchanged.

Verification status of this article

The statements about what this editor can build come from our own source code, not from documentation. The evidence table below names the file and the value behind each one. Where a spec cannot be met here, the article says so instead of leaving it out.