App store screenshot size is the badge, not a pixel myth

App store screenshot size, plainly#

App store screenshot size is what teams ask for first. The pages read here do not give a pixel pair that survived as text. The 5 October developer note says iPhone Duo will be available to customers starting 23 October 2026. That customer date is today. The note also says you can submit optimised apps in App Store Connect now, and that submitting iPhone Duo screenshots makes the product page show a badge that the app is optimised for the phone. Starting April 2027, apps or games submitted will need to include those screenshots.

The screenshot specifications page repeats both points: from April 2027, screenshots will be required for any app using the iOS 27.1 SDK or later, and the badge appears when those screenshots are submitted. The dimension table did not come through as readable text in this fetch. Iphone screenshot size and ios screenshot size are therefore not filled in with a remembered rectangle. App store screenshot requirements, as published in the text, are a badge now and a submission rule from April 2027, not a forged width and height.

What the prepare page actually asks you to change#

The prepare page says apps built with the iOS 27 SDK and later resize when the phone folds and unfolds. Hardcoded screen sizes, fixed orientations, and device assumptions can stretch or clip the layout. Apps built with the iOS 26 SDK or earlier still run, but on the open device they sit in the centre with empty space around the window. Before you ship a build on the iOS 27.1 SDK, the page says the content must adapt when bars become vertical.

Step one on that page is a resizability skill inside Xcode: ask the coding assistant to get the app ready for iPhone Duo. The Xcode link is the door it names. That is a build task. It is not a pixel export. A team that only swaps a marketing frame and leaves hardcoded sizes in the binary will fail the open-phone test the page describes.

The iPhone Duo hub points at Human Interface Guidelines, screenshot specifications, and the prepare steps. It does not, in the extract used here, add a customer count or a list of featured apps. A social claim of 50 ready apps is not used. The scent on this trail is the badge and the SDK, not a rumour of a shelf.

The product page, once the binary is honest#

The asset best-practices page says creative assets, previews, and screenshots do different jobs. Previews and screenshots show the app in use. Creative assets can carry brand, season, and new content, on iOS 27 and iPadOS 27 and later, including the product page and search results. Assets on the store must meet a 4+ age rating even if the app itself is rated higher. The page points at guideline 2.3 on accurate metadata. A 19 October piece on this site already covers that guideline. This one does not repeat it.

App preview specifications are linked from the 5 October note and from the asset page. The preview specifications URL is the place Apple names for moving pictures. This fetch did not return a duration or a pixel pair from that URL, so none is stated. Use the page itself before you export. Do not borrow a size from an older phone and call it Duo.

The prepare page also says you can nominate the app for featuring, and points at the nomination guide. A tech talk is listed as further viewing. Submission steps are named at the submitting page. The developer news index is where the 5 October note sits among older items, including a 16 October guidelines update already covered elsewhere. The quiet quarry is the badge you earn by submitting the right screenshots, not a featuring promise.

How to brief the week without a fake rectangle#

Tell the team three dates and one behaviour. Customers from 23 October. Badge when Duo screenshots are submitted. Screenshots required on submission from April 2027 for apps on the iOS 27.1 SDK or later, as the specifications page states. App store screenshot size stays a live page, not a number in this article. Open it yourself before the export, and write the size you see there into the brief. A guessed rectangle is worse than a blank one now.

Tell engineering to drop hardcoded sizes. The prepare page is plain: an older SDK build will letterbox on the inner display. That is a store-page problem and a product problem. A moonlit den of new screenshots will not hide a window that does not fill the glass. Ask for a fold test on a real build before the first customer weekend, not after the reviews land. A hedgerow of new frames will not fix a binary that still assumes one rectangle.

If the job is the product page, the badge, and the first week of customer traffic, start at app marketing. Paid support around the listing is on paid search and paid social. The measurement habit is on SEO and GEO. Rates are on pricing. The door is contact. The rest of the desk is on the news stream.

Frequently asked questions#