How to Use the App Store Screenshot Size Checker Above
The checker at the top of this page works on the files you are about to upload. It takes a few seconds and needs no sign in.
- Step 1
Choose or Drop Your Files
Click to choose files or drag them onto the tool, up to 10 at a time, as PNG or JPG. Ten is also the most screenshots the App Store takes for one device size, according to Apple's screenshot specifications, so one full set fits in one pass. If you drop more, the tool checks the first 10. It reads each file in your browser. Nothing is uploaded to a server.
- Step 2
Read the Size in Pixels
Each file gets a row with its file name and its width and height in pixels. This is the size of the file itself, which is what App Store Connect reads. It can differ from the canvas size your design tool shows, because the export scale multiplies it.
- Step 3
Read the App Store Result
When both numbers match a size Apple accepts, the row names the display group and the orientation, for example "iPhone with Dynamic Island, large display, portrait". That is the device tab to upload under. When nothing matches, the row says "Not an accepted App Store size", names the closest accepted size and tells you how many pixels off the file is. The tool compares against the accepted sizes for iPhone, iPad, Mac, Apple TV, Apple Vision Pro and Apple Watch. A size that two platforms share, such as 3840 x 2160 for Apple TV and Apple Vision Pro, names both.
- Step 4
Look for the File Type and Transparency Flags
A file whose extension is not .png, .jpg or .jpeg gets a flag, because those are the only three Apple lists. A PNG that contains transparency gets a second flag. Apple does not accept transparent screenshots, even when the pixel size is right.
- Step 5
Read the Google Play Result
The second result on each row is for Google Play, so the tool works as a Google Play screenshot size checker too. A file passes when each side is between 320 and 3,840 pixels and the long side is no more than twice the short side, the limits on Google's Play Console Help page for preview assets. When a file fails, the row says which of the two rules it broke.
- Step 6
Fix the File Where It Was Made, Then Check Again
The checker reports. It does not resize, crop or edit anything. Go back to the simulator, Figma or Sketch file, change the setting described further down this page, export again and drop the new file in. Repeat until every row names a display group. If you would rather rebuild the set at an exact size, the free App Store screenshot generator exports every slide at 1320 x 2868, 1284 x 2778 or 1206 x 2622.
What Each Result From the App Store Screenshot Validator Means
Every row in the tool ends in one of these outcomes. The last column is what to do about it.
| Result on the row | What it means | What to do next |
|---|---|---|
| A display group and an orientation | The width and height match one of the accepted sizes in Apple's specifications exactly. | Upload the file under that device tab in App Store Connect. If the group is not the one you planned, for example a medium display when you wanted the large one, you captured or exported from the wrong device. |
| Not an accepted App Store size, with the closest size | No size on Apple's list has both of these numbers. The tool shows the nearest one and the gap in pixels. | Read the gap. A few pixels means a crop or a canvas typed wrong. Exactly half or a third of an accepted size means the export scale. A different shape means the wrong device or the wrong platform. |
| File type flag | The extension is something other than .png, .jpg or .jpeg, such as .webp or .gif. A file your browser cannot open as an image is skipped, with a note above the results. | Export again as PNG or JPG. On a Mac, Apple's Preview guide describes File, Export and the Format menu. |
| Transparency flag on a PNG | The PNG has see through pixels. Rounded corners, the empty space around a device frame or a frame with no fill are the usual sources. | Flatten the image onto a solid background or export it as JPG. The section on transparency below has the steps. |
| Google Play: passes | Both sides sit between 320 and 3,840 pixels, and the long side is at most twice the short side. | The size is fine for a phone screenshot. For the large recommendation formats, Google asks for at least 1080 x 1920 in portrait or 1920 x 1080 in landscape. |
| Google Play: a side is too small or too large | One side is under 320 or over 3,840 pixels. | Export at a different scale. This mostly hits Apple Watch files and very large tablet or desktop captures. |
| Google Play: the long side is more than twice the short side | The image is too tall or too wide for Google's 2 to 1 limit. Every current full screen iPhone screenshot lands here. | Make a separate set for Google Play at 1080 x 1920. The table on the 2 to 1 rule below shows the numbers. |
The two results are independent. A file can match an App Store size and fail Google Play, and most iPhone screenshots do exactly that.
The App Store Screenshot Sizes Most Apps Need
Apple accepts dozens of sizes, and most apps need four rows of them. These are the App Store screenshot requirements that matter for a phone and tablet app: the iPhone and iPad sizes that Apple's screenshot specifications tie to a requirement, checked on October 12, 2026. Sizes are portrait, width first. Swap the two numbers for landscape. Every other size, including Mac, Apple Watch, Apple TV and Apple Vision Pro, is in the full reference of App Store screenshot sizes.
| Display group | Accepted sizes in pixels | When you need it |
|---|---|---|
| iPhone with Dynamic Island, large display | 1320 x 2868, 1290 x 2796 or 1260 x 2736 | The set to make first. If you leave it empty, Apple fills it with scaled screenshots from the Face ID large display. |
| iPhone with Face ID, large display | 1284 x 2778 or 1242 x 2688 | Required if the app runs on iPhone and you upload nothing for the Dynamic Island large display. |
| iPhone with Dynamic Island, medium display | 1206 x 2622 or 1179 x 2556 | Named in Apple's list of required device sizes at the top of its page. |
| iPad, 13 inch display | 2064 x 2752 or 2048 x 2732 | Required if the app runs on iPad. |
| Google Play phone, for comparison | Any size with each side from 320 to 3,840 and the long side at most twice the short side. 1080 x 1920 is the size Google names. | At least 2 screenshots across device types to publish, up to 8 per device type. |
Apple's page states the iPhone requirement in two ways: the summary names the Dynamic Island medium display, and the size table marks the Face ID large display as required when the Dynamic Island large set is missing. Exporting one design at 1320 x 2868 and at 1206 x 2622 covers both readings.
Why App Store Connect Rejects a Screenshot That Is a Few Pixels Off
The App Store screenshot dimensions are a list, and a list has no tolerance. Apple's screenshot specifications give each display group two or three exact pixel sizes and nothing in between. A file of 1290 x 2800 is four pixels taller than 1290 x 2796, and App Store Connect treats it the same as a file that is wildly wrong.
The near misses are the ones that cost an afternoon, because the image looks right. In one thread on Apple's Developer Forums, a developer who had cropped screenshots by hand reported that uploads kept failing for the wrong size. The file turned out to be 1240 x 2688. The accepted size is 1242 x 2688, two pixels wider. The tool above reports the closest accepted size and the gap in pixels for exactly this case, so a miss of two pixels shows up as two pixels.
A file can also be a perfectly good size for a different tab. A 1290 x 2796 screenshot belongs to the Dynamic Island large display. Dropped into the tab for the Face ID large display, which takes 1284 x 2778 or 1242 x 2688, it is refused. The display group in the checker's result tells you which tab the file is for.
Scaling is the other half of the story. Apple says that when your interface looks the same across devices you only need the highest required resolution, and App Store Connect scales it down for smaller devices. The scaling is done by Apple, from a set you uploaded at an exact size. It does not mean an upload can be roughly the right size. Apple's guide to managing App Store assets describes the Media Manager, where you can see every device size and which ones are using scaled copies.
App Store Connect Screenshot Upload Errors and What Causes Each
Apple's help pages list the rules and leave out the error messages. The wording below is what developers have reported on Apple's own Developer Forums, with the cause that matches Apple's published rules. Each message was read in the linked thread on October 12, 2026.
| Message or symptom | Where it is reported | Usual cause | How to fix it |
|---|---|---|---|
| The dimensions of one or more screenshots are wrong | Quoted by developers in threads such as this one on Apple's Developer Forums. In other reports the message goes on to name the sizes the tab expects. | At least one file in the batch is not an accepted size for the tab you dropped it on. One wrong file is enough, since the message covers the whole batch. | Run every file through the checker, not only the first. Export the odd one again at an accepted size, or move it to the tab that matches its display group. |
| One or more screenshots are in the wrong format | A forum thread that started in October 2020 and still had replies in 2026. Several posters say their pixel sizes were correct. | Posters there point at the file itself, for example a JPEG that was saved incorrectly, and not at its pixel size. | Fixes reported in the thread: export the image again from a design tool, or convert it from PNG to JPEG or from JPEG to PNG. |
| IMAGE_TOOL_FAILURE, or a file that stays marked as processing | A long forum thread on failed screenshot uploads, with bursts of reports on the same days. | Posters had correct sizes, and many people hit it at once, which points at App Store Connect and away from your files. | Check the files once so you can rule them out, then try again later. One poster suggested renaming the files and uploading them one at a time. |
| A rejection that mentions alpha channels or transparency | The rule is in Apple's screenshot specifications: images cannot include alpha channels or transparencies. | A PNG exported with a transparent background or with rounded corners that have nothing behind them. | Flatten the PNG onto a solid color or export a JPG. See the transparency section below. |
| No way to add or replace screenshots | Apple's guide to managing App Store assets lists the version statuses that allow uploads: Prepare for Submission, Invalid Binary, Rejected, Metadata Rejected and Developer Rejected. | The version is live or waiting for review, so its screenshots are locked. | Create a new version, or upload to the Asset Library, which the same guide says works independent of an app version. |
Forum posts are reports from developers, not statements by Apple, and the exact wording of a message can change between App Store Connect releases. The rules behind the first, fourth and fifth rows are Apple's own.
The Dimensions of One or More Screenshots Are Wrong on an In App Purchase Screenshot
The same message turns up in a place many people do not expect: the App Review screenshot attached to an In App Purchase or a subscription. The forum thread quoted in the table above is exactly that case, a 1290 x 2796 file refused in the purchase's review slot. Apple's reference for In App Purchase information says this screenshot is seen only by App Review and must meet any of the screenshot specifications your app supports, so the size the checker names should be enough.
In practice developers report otherwise. In a thread from January 2026, a developer who had tried every documented size says the upload went through only after the image was resized to 640 x 920 pixels. If a purchase screenshot fails while the same file uploads fine on the product page, export a 640 x 920 copy of the purchase screen and try that. The background is in the guide to App Store screenshot sizes.
How to Fix a Wrong App Store Screenshot Size in Xcode, Figma and Sketch
A wrong size is fixed where the image is made. Each row gives the setting from the tool's own documentation and an example that lands on an accepted size.
| Where the screenshot comes from | What its documentation says | What to set |
|---|---|---|
| A simulated device in Xcode | Apple's Xcode guide to capturing screenshots says to run the app on a simulated or physical device in Device Hub and click the Screenshot button below the device. The capture is made at the full resolution of that device, whatever the resolution of your Mac's display, and saved to the Desktop. | The device decides the size, so choose one whose screen is on Apple's list. Apple's tech specs for the iPhone 16 Pro Max give a 2868 by 1320 pixel display, which is the accepted 1320 x 2868. If the checker reports a medium display, you ran a smaller phone. |
| A frame in Figma | Figma's guide to exporting puts the Export section in the right sidebar, where you add an export configuration with the plus button. Its page on export formats and settings explains the Scale field: a number followed by x is a multiplier, w sets a fixed width and h sets a fixed height. | Use a multiplier on a frame with the right shape. A 440 x 956 frame at 3x exports at 1320 x 2868. A 430 x 932 frame at 3x gives 1290 x 2796, and a 402 x 874 frame at 3x gives 1206 x 2622. For iPad, 1032 x 1376 at 2x gives 2064 x 2752. Left at 1x, the first frame exports at 440 x 956, which matches nothing. |
| A frame in Sketch | Sketch's documentation on exporting says the Mac app exports everything as a PNG at its actual size, 1x, by default. The Size field in the export presets takes a scale such as 2x or 3x, or a fixed width or height in pixels written as 128w or 128h. | Add a 3x preset to a frame built at phone size in points, with the same arithmetic as the Figma row. Choose JPG in the Format menu if the frame has no background. |
| An existing image, resized in Preview on a Mac | Apple's Preview guide to resizing describes Tools, Adjust Size, with an option to scale proportionally that keeps the shape when you change one number. | This works only when the image already has the shape of an accepted size, for example 2580 x 5592 scaled to 1290 x 2796. If the shape differs, a proportional resize misses the target and a forced one stretches the interface. |
| Many devices and languages at once | The fastlane screenshots guide describes snapshot, which captures screenshots in multiple languages across simulators, and deliver, which uploads them to App Store Connect. | The simulators produce the sizes, so the choice of devices in your configuration is what to check. Drop one file per device into the checker after the first run. |
The fixed width option is the one that causes near misses. A 393 x 852 frame exported at a width of 1320 comes out about 2,862 pixels tall, six short of 2868, because that frame has the shape of the medium display. Export it at 3x and you get 1179 x 2556, which is accepted.
Video: Figma's Own Guide to Export Settings and Scale
Most wrong sizes from Figma come from the Scale field. Figma's tutorial shows where the export settings live and how the scale options change the pixel size of the file.
Why a PNG With Transparency Is Rejected and How to Flatten It
Apple's rule is one line in its screenshot specifications: images cannot include alpha channels or transparencies. An alpha channel is the part of an image that stores how see through each pixel is. In MDN's guide to image file types, the PNG color modes with alpha are described as carrying an extra alpha sample per pixel that says how opaque it is. The same guide states that JPEG does not support an alpha channel at all.
Transparency gets into a screenshot in three common ways. The design has rounded corners with nothing behind them. The frame has no fill, so the export has no background. Or a device frame was placed around the screen and the empty space beside it was exported too. In all three cases the image can look finished on a white canvas and still be transparent in the file.
Figma needs a special note. Its page on export formats says Figma writes 32 bit PNGs in the RGBA color model and that it is not possible to export PNGs without an alpha value. Apple's rule names alpha channels as well as visible transparency, so the safe export from Figma for the App Store is JPG. Give the frame a solid fill first, so you choose the background color and the export does not choose it for you.
In Sketch, a slice has a Background Color option that applies a color behind the export, according to Sketch's exporting documentation. For a file you already have, open it in Preview on a Mac, choose File, then Export, and pick JPEG in the Format menu, the steps in Apple's Preview guide to converting image types. Then drop the new file into the checker to confirm that the size survived and the flag is gone.
Know what the flag does and does not catch. The checker looks for see through pixels, on a reduced copy of the image. A PNG from Figma with a solid fill has none, so no flag appears, yet by Figma's own description the file still holds an alpha value for every pixel. A clean row for a PNG means no visible transparency was found. It does not mean the file has no alpha channel, which is one more reason to send JPGs to the stores.
Google Play has the same requirement in different words. Its preview assets page asks for JPEG or 24 bit PNG with no alpha. A flattened file therefore serves both stores, provided its shape passes Google's 2 to 1 rule.
Why an iPhone Screenshot Fails the Google Play Screenshot Size Check
Google Play does not use a list of sizes. Its Play Console Help page on preview assets sets a minimum dimension of 320 pixels, a maximum of 3,840, and says the maximum dimension cannot be more than twice the minimum dimension. Current iPhones are taller than that. The ratios below are our own arithmetic on Apple's accepted sizes.
| Screenshot size | Long side divided by short side | Google Play result |
|---|---|---|
| 1320 x 2868, iPhone large display | 2.17 | Fails. The long side is more than twice the short side. |
| 1290 x 2796, iPhone large display | 2.17 | Fails for the same reason. |
| 1242 x 2688, iPhone with Face ID, large display | 2.16 | Fails for the same reason. |
| 1206 x 2622, iPhone medium display | 2.17 | Fails for the same reason. |
| 1242 x 2208, iPhone with Home Button, large display | 1.78 | Passes. |
| 2064 x 2752, iPad 13 inch | 1.33 | Passes. |
| 312 x 390, Apple Watch Series 3 | 1.25 | Fails. The short side is under the 320 pixel minimum. |
| 1080 x 1920, a 9:16 export | 1.78 | Passes, and it is the size Google names for its recommendation formats. |
For a 1320 pixel wide image the tallest height Google accepts is 2640, which is 228 pixels less than the iPhone screenshot. Cropping that much cuts into the interface, so lay out a separate 9:16 set at 1080 x 1920 for Google Play. To be eligible for the large recommendation formats, Google asks apps for at least four screenshots at that size or larger, and games for at least three.
How to Check App Store Screenshot Size by Hand on Mac and Windows
You can do the checker's job yourself with tools already on your computer. It takes longer, and the comparison against Apple's list is up to you.
- Step 1
On a Mac, Show the Size Under Each Icon in Finder
Open the folder in icon view, choose View, then Show View Options, and select the option to show item info. Apple's Mac User Guide says item info can include image dimensions, so every screenshot in the folder shows its pixel size at once. The same page describes File, Get Info, or Command I, for a single file.
- Step 2
On a Mac, Open the Inspector in Preview
Open the file in Preview and click the Info button in the toolbar. Apple's Preview guide describes the Inspector window that opens, with a general info tool for the image and a second tool for details by format.
- Step 3
On Windows, Read the Dimensions Property
In File Explorer, right click the file, choose Properties and open the Details tab. The Dimensions row is the image property that Microsoft's Windows reference defines as horizontal pixels x vertical pixels, so the first number is the width. You can also add Dimensions as a column in the Details view to see a whole folder.
- Step 4
Compare Both Numbers With Apple's List
Look the pair up in the table of sizes above or in the full reference of App Store screenshot sizes. Both numbers have to match one entry. Matching the width alone is the classic mistake, because several groups share a width: 1242 wide can be 2688 tall or 2208 tall, and they are different display groups.
- Step 5
Do the Google Play Arithmetic
Check that both sides are at least 320 and at most 3,840 pixels. Then divide the long side by the short side on a calculator. Any answer above 2 fails.
- Step 6
Check the Format Last
Confirm that the extension is .png, .jpg or .jpeg. Transparency is hard to judge by eye, because a transparent area can show as white, black or a checkerboard depending on the viewer. If a PNG came out of a design tool, treat it as suspect and export a JPG.
How to Check and Resize App Store Screenshots From the Command Line
Every Mac includes sips, Apple's command line tool for images, and it can do the checker's reads and a careful resize from Terminal. We ran each command below on macOS 26.6.2 on October 17, 2026, on a test PNG of 1320 x 2868 pixels. Replace the file names with your own.
- Step 1
Read the Size of Every File in a Folder
Inside the folder, run sips -g pixelWidth -g pixelHeight followed by *.png, or *.jpg for JPEG files. sips prints the width and the height under each file name. Compare both numbers with the table of sizes above, since matching the width alone proves nothing.
- Step 2
Ask Whether a File Has an Alpha Channel
Add -g hasAlpha to the same command and sips answers yes or no for each file. This is a stricter test than the flag in the checker, which looks only for pixels that are really see through. A PNG exported from Figma should answer yes even when nothing in it is transparent, because Figma's export documentation says its PNGs always carry an alpha value.
- Step 3
Convert a PNG to JPG to Remove the Alpha Channel
Run sips -s format jpeg shot.png --out shot.jpg to write a JPEG copy. In our test the copy answered no to hasAlpha while the original answered yes. Check the new file, not the old one, before you upload.
- Step 4
Resize by Width, Then Crop to the Exact Size
sips --resampleWidth 1290 scaled our 1320 x 2868 file to 1290 x 2803, keeping its shape. sips --cropToHeightWidth 2796 1290 then trimmed it to 1290 x 2796, an accepted size, taking the extra rows evenly from the top and the bottom. Note the order of the numbers: height first, then width. The crop amounts for the other sizes are in the converter table of the App Store screenshot sizes guide.
- Step 5
Work on Copies
sips overwrites the file you give it unless you add --out with a new name. Duplicate the export folder first, run the commands on the copy, then drop the results into the checker above as a last look.
Is This an App Store Screenshot Resizer?
No. People search for an App Store screenshot resizer when an upload fails, and the checker above deliberately stops at telling you what is wrong. It reads the size, the file type and the transparency of each file and changes none of them.
The reason is that resizing rarely gives a good screenshot. Scaling an image to a size with a different shape either stretches the interface or leaves bars at the edges. Scaling up from a small capture makes text soft, and store screenshots are mostly text and thin lines. Apple accepts several sizes per display group so that you can capture or export at one of them directly.
An export from the source file at the right scale takes a minute and gives a sharp result. The one case where a resize is harmless is an image that already has the exact shape of an accepted size and is larger than it, such as a 3x export that should have been 2x.
The checker also does not look at what the screenshot shows. Apple reviews the content of screenshots too: they should show the app in use, leave out prices and avoid other platforms. Those rules, with the guideline numbers, are in the section on what Apple rejects in the guide to App Store screenshot sizes.
Eight Mistakes That Lead to a Screenshot Wrong Size Error in App Store Connect
Each of these produces a file that looks fine and fails on upload.
Trusting the Canvas Size
Design tools show a frame in points, such as 430 x 932. The file only reaches 1290 x 2796 when the export scale is 3x, and Sketch exports at 1x by default. Check the file, not the canvas.
Fixing the Width and Letting the Height Follow
Typing a width of 1320 on a frame with the shape of a smaller phone gives a height a few pixels away from 2868. Use a multiplier on a frame that already has the right proportions.
Cropping by Hand
A crop dragged with the mouse ends on whatever pixel you let go at. The forum case above was 1240 pixels wide where 1242 was needed. If you must crop, type the numbers.
Dropping a Right Size on the Wrong Tab
1290 x 2796 is accepted for the Dynamic Island large display and refused on the tab for the Face ID large display. Read the display group the checker names before you drag the file in.
Uploading the PNG Straight From Figma
Figma's own documentation says its PNG exports always carry an alpha value. Export JPG for the stores, with a solid fill on the frame.
Reusing the iPhone Set on Google Play
Current iPhone screenshots are about 2.17 times taller than they are wide, and Google stops at 2. The files pass the App Store check and fail the Google Play check in the same row.
Mixing Apple Watch Sizes Between Languages
Apple accepts six Apple Watch sizes and requires you to use the same one across all localizations of the app. A set captured on two different watches fails that rule even though each file is an accepted size.
Checking One File Out of Ten
The dimension message covers the whole batch, so a single odd file blocks nine good ones. Drop the full set into the checker and look for the row that does not name a display group.
What to Do After the App Store Screenshot Size Checker Passes Every File
Size is the first gate. Once every row names a display group, three things are left. Count the set: Apple wants at least one screenshot and takes up to 10 per device size, per its screenshot specifications. Then decide the order and check each language you localize. Which screenshots show in search results, and how localized sets work, is covered in the guide to App Store screenshot sizes.
The rest of the listing has limits of its own. The app name, subtitle, keyword field and promotional text are all counted in characters, and the App Store character counter checks them the way this page checks screenshots. If the upload is part of a release, the app release notes generator drafts the What's New text, and the app launch checklist covers what else to have ready on the day.
Screenshots get reused outside the store too. Before one goes into an ad or a post with a device frame around it, read Apple's App Store marketing guidelines explained. Posts need other shapes than the store does, which are listed under social media image sizes. And when you share the release, an App Store campaign link lets App Store Connect show which post sent the downloads.
What Spreadcast Does With Your App Store Screenshots
The checker on this page is a free tool and stands alone. Spreadcast, the product behind it, starts where the upload ends. You paste your App Store link once on the start page, and Spreadcast checks your App Store listing every day.
Each update, review and rating milestone becomes a designed post built from the listing itself, with the app icon and your own screenshots, and it is published for you on the networks you connect. The Free plan drafts the posts for you to download. It works with App Store listings today.
Frequently Asked Questions
How do I check the size of an App Store screenshot?
Drop the file into the checker at the top of this page. It shows the width and height in pixels and names the Apple display group the file matches, or the closest accepted size and how many pixels off it is. By hand, read the dimensions in Finder or in File Explorer and compare them with Apple's list.
What does "the dimensions of one or more screenshots are wrong" mean?
It is the message developers report when at least one file in an upload is not an accepted size for the device tab it was dropped on. Apple's screenshot specifications list exact pixel sizes with no tolerance, so a file two pixels off fails. Check every file in the batch, since one wrong file triggers the message.
What size should an iPhone screenshot be for the App Store?
For the large display, 1320 x 2868 pixels in portrait is the largest accepted size, and 1290 x 2796 and 1260 x 2736 are accepted too. Apple's list of required sizes also names the medium display, 1206 x 2622 or 1179 x 2556. The full list is in the guide to App Store screenshot sizes.
Can I upload a PNG with a transparent background to App Store Connect?
No. Apple's specifications say screenshots cannot include alpha channels or transparencies. Flatten the image onto a solid background or export it as JPG, which has no alpha channel.
Why does my iPhone screenshot fail the Google Play check?
Google Play requires the long side of a screenshot to be at most twice the short side, per its preview assets page. A 1320 x 2868 iPhone screenshot is 2.17 times taller than it is wide. Make a separate 1080 x 1920 set for Google Play.
Does the screenshot size checker upload my files?
No. The tool reads the width, height and format of each file inside your browser. The files stay on your computer, and there is no account.
Can the checker resize my screenshots to the right size?
No. It reports the size and the problem and leaves the file as it is. Export the screenshot again from the simulator or the design file at an accepted size, then check the new file.
Does a screenshot from the Xcode simulator have the right size?
It has the size of the device you ran. Apple's Xcode guide says a capture is made at the full resolution of the simulated device. That size is accepted when the device's screen is on Apple's list, as it is for the current large and medium iPhones.
Is there a file size limit for App Store screenshots in MB?
Apple's screenshot specifications list formats, pixel sizes and the ban on transparency, and no file size limit. Google Play gives none for phone screenshots either, only 8 MB per Android XR screenshot. If an upload fails, check the pixel size and the alpha channel before you worry about megabytes.
Can I check App Store screenshot sizes from the command line?
Yes, on a Mac. sips -g pixelWidth -g pixelHeight -g hasAlpha followed by the file names prints the size and whether each file has an alpha channel. The section on the command line above also shows how to resize and crop with sips.
Where These Facts Come From
Every outside number, rule and price on this page links to the page it was taken from.
- Screenshot specificationsApple Developer, App Store Connect Help
- Manage your App Store assetsApple Developer, App Store Connect Help
- Add preview assets to showcase your appGoogle Play Console Help
- Capturing screenshots and videos from devicesApple Developer Documentation, Xcode
- iPhone 16 Pro Max tech specsApple Support
- Export static designs from FigmaFigma Help Center
- Export formats and settings for static designsFigma Help Center
- Importing and exportingSketch Documentation
- Convert image file types using Preview on MacApple Support
- View information about PDFs and images in Preview on MacApple Support
- Crop, resize, or rotate an image in Preview on MacApple Support
- Get file, folder, and disk information on MacApple Support
- The image dimensions property in WindowsMicrosoft Learn
- Image file type and format guideMDN Web Docs
- Forum thread on the screenshot dimensions messageApple Developer Forums
- Forum thread on the wrong format messageApple Developer Forums
- Forum thread on a screenshot two pixels too narrowApple Developer Forums
- Forum thread on failed screenshot uploadsApple Developer Forums
- fastlane screenshots guide for iOSfastlane docs
- Video: exporting from Figma, with scale settingsFigma
- In App Purchase information, App Review screenshotApple Developer, App Store Connect Help
- Forum thread on a subscription review screenshot accepted at 640 x 920Apple Developer Forums
Researched and written by Spreadcast. Last checked on October 17, 2026.