Quick answer
If your app supports iPad, the App Store needs at least one iPad screenshot at 2064×2752 pixels — the 13-inch iPad Pro size — and Apple reuses that set for every other iPad, from the Air to the mini to the standard model. Files must be PNG or JPEG in RGB with no transparency, and the pixel dimensions have to be exact because App Store Connect rejects anything that's off. You can upload up to ten per language.
Do you even need iPad screenshots?
Before you make a single iPad screenshot, check whether you owe Apple any. The answer hangs on one thing: does your app support iPad? If it's an iPhone-only app, you skip iPad screenshots entirely and Apple never asks. If your app runs on iPad — including universal apps that support both — then iPad screenshots become required, and you can't publish that device family without them.
This catches people who tick the iPad checkbox in Xcode without thinking about the marketing side. The moment your app is available on iPad, its App Store page has an iPad tab, and that tab needs its own screenshots. An empty or phone-shaped set there looks careless and can stall your submission.
So the first decision is honest scope. If iPad is a real, supported experience, commit to proper iPad screenshots. If iPad support is half-hearted or untested, it's often cleaner to ship iPhone-only at launch and add iPad later when you can do the screenshots justice. I've done both, and a focused iPhone-only launch beats a universal one with stretched, sad iPad art.
One more wrinkle worth knowing: Apple checks this at submission, not before, so a missing or wrong iPad set won't warn you while you're building the listing — it surfaces as a rejection once you submit for review. That's a frustrating place to find out, because it costs you a whole review cycle waiting in the queue again. I check that the iPad tab has a proper set before I ever hit submit, right alongside confirming the iPhone screenshots, so a tablet oversight never bounces me back to the start.
This catches people who tick the iPad checkbox in Xcode without thinking about the marketing side. The moment your app is available on iPad, its App Store page has an iPad tab, and that tab needs its own screenshots. An empty or phone-shaped set there looks careless and can stall your submission.
So the first decision is honest scope. If iPad is a real, supported experience, commit to proper iPad screenshots. If iPad support is half-hearted or untested, it's often cleaner to ship iPhone-only at launch and add iPad later when you can do the screenshots justice. I've done both, and a focused iPhone-only launch beats a universal one with stretched, sad iPad art.
One more wrinkle worth knowing: Apple checks this at submission, not before, so a missing or wrong iPad set won't warn you while you're building the listing — it surfaces as a rejection once you submit for review. That's a frustrating place to find out, because it costs you a whole review cycle waiting in the queue again. I check that the iPad tab has a proper set before I ever hit submit, right alongside confirming the iPhone screenshots, so a tablet oversight never bounces me back to the start.
What's the one iPad screenshot size that matters?
Apple simplified iPad screenshots more than most developers realize, and it works in your favor. There's really one size you need: 2064×2752 pixels, which is the 13-inch iPad Pro in portrait. Upload a set at that size and Apple reuses it for every other iPad your app supports — the iPad Air, the iPad mini, and the standard iPad all pull from that single set.
That means you don't produce a separate batch per iPad model. One well-made 2064×2752 set covers the whole lineup. There's a legacy 12.9-inch size at 2048×2732 that App Store Connect still accepts, but you only need it if you're specifically targeting older iPad Pro models, and for a new listing the 13-inch size is the one to build around.
Landscape is an option too, at the swapped 2752×2064, if your app is genuinely landscape-first like a game or a drawing tool. For most apps, portrait is the safer default because that's how people hold an iPad while browsing the store. Pick one orientation and commit — a mixed set looks disjointed in the gallery.
That means you don't produce a separate batch per iPad model. One well-made 2064×2752 set covers the whole lineup. There's a legacy 12.9-inch size at 2048×2732 that App Store Connect still accepts, but you only need it if you're specifically targeting older iPad Pro models, and for a new listing the 13-inch size is the one to build around.
Landscape is an option too, at the swapped 2752×2064, if your app is genuinely landscape-first like a game or a drawing tool. For most apps, portrait is the safer default because that's how people hold an iPad while browsing the store. Pick one orientation and commit — a mixed set looks disjointed in the gallery.
What format and rules does Apple enforce?
App Store Connect is unforgiving about the technical details, so get them right before you upload. Screenshots must be PNG or JPEG, in the RGB color space, and flattened with no alpha channel — any transparency has to be removed or the upload fails. The pixel dimensions have to match exactly; there's no 'close enough,' no aspect-ratio fallback, and no auto-cropping on Apple's end.
You can upload up to ten screenshots per language for the iPad, though you rarely want that many. At least one is required to publish the iPad family. Apple's screenshot specifications reference lists the exact dimensions and formats, and it's the source of truth to check against when an upload gets rejected.
The rule that surprises people is the pixel-exact one. Export at 2063 or 2065 pixels wide and it bounces — the tooling won't nudge it for you. That's why building your screenshots on a canvas locked to 2064×2752 from the start saves a lot of resizing pain later. Set the dimensions once and every export is submission-ready.
You can upload up to ten screenshots per language for the iPad, though you rarely want that many. At least one is required to publish the iPad family. Apple's screenshot specifications reference lists the exact dimensions and formats, and it's the source of truth to check against when an upload gets rejected.
The rule that surprises people is the pixel-exact one. Export at 2063 or 2065 pixels wide and it bounces — the tooling won't nudge it for you. That's why building your screenshots on a canvas locked to 2064×2752 from the start saves a lot of resizing pain later. Set the dimensions once and every export is submission-ready.
How do you make iPad screenshots that don't look like stretched phone ones?
The laziest iPad screenshots are just phone screenshots blown up, and they look exactly that bad — tiny UI floating in a sea of empty canvas, or a phone-shaped app letterboxed with ugly bars. The iPad canvas is wide and tall, and it rewards a design made for it rather than inherited from the phone.
Use the extra room. iPad screenshots have space for a real headline caption plus a generous device shot, and the tablet frame around your app reads as premium when it fits the canvas properly. That's the difference between a set that says 'we built this for iPad' and one that says 'we ticked a box.'
This is where a mockup tool earns its keep. I drop the raw iPad capture into PlayMockUp's studio, wrap it in an iPad from the device frame library, and lay captions into the space that the larger canvas gives me — instead of scaling up a phone layout and hoping. If you want the background on why the frame itself matters so much, my post on device frames for app mockups goes deeper on picking the right one.
Use the extra room. iPad screenshots have space for a real headline caption plus a generous device shot, and the tablet frame around your app reads as premium when it fits the canvas properly. That's the difference between a set that says 'we built this for iPad' and one that says 'we ticked a box.'
This is where a mockup tool earns its keep. I drop the raw iPad capture into PlayMockUp's studio, wrap it in an iPad from the device frame library, and lay captions into the space that the larger canvas gives me — instead of scaling up a phone layout and hoping. If you want the background on why the frame itself matters so much, my post on device frames for app mockups goes deeper on picking the right one.
How many iPad screenshots should you actually upload?
Apple allows ten, but ten is almost never the right answer. The gallery shows the first two or three before anyone swipes, and most people decide right there, so those opening frames do the heavy lifting. A tight set of three to five strong screenshots beats a padded set of ten where the good ones get diluted.
Think of the sequence as a short pitch. The first screenshot states what the app is and why it matters. The next two show the features that seal the deal. Anything after that is for the minority who keep swiping, so it can go deeper but shouldn't carry your core message. If a screenshot isn't pulling its weight, cut it — a lean gallery reads as confident.
The order matters more than the count. I'll draft the sequence, look at just the first two frames as they'd appear in the gallery, and reorder until those two alone tell the story. Building the whole set in one place makes that reshuffling quick, which is half the reason I lay them out in the studio before committing an order.
Think of the sequence as a short pitch. The first screenshot states what the app is and why it matters. The next two show the features that seal the deal. Anything after that is for the minority who keep swiping, so it can go deeper but shouldn't carry your core message. If a screenshot isn't pulling its weight, cut it — a lean gallery reads as confident.
The order matters more than the count. I'll draft the sequence, look at just the first two frames as they'd appear in the gallery, and reorder until those two alone tell the story. Building the whole set in one place makes that reshuffling quick, which is half the reason I lay them out in the studio before committing an order.
What trips people up with iPad screenshots?
A handful of mistakes account for most iPad screenshot headaches. The biggest is uploading phone-size images to the iPad slot — the dimensions don't match, so it rejects outright, and even if they did, they'd look wrong. Right behind it is transparency: exporting a PNG with an alpha channel intact, which App Store Connect refuses because it wants flattened RGB.
Orientation mismatches cause quieter trouble. Mixing portrait and landscape shots in one iPad set makes the gallery look jumbled, so pick one and stay consistent. And letterboxing — showing a phone-ratio app inside black bars on the iPad canvas — screams that the app wasn't really designed for tablet, even when it was.
My pre-upload check is short: confirm every file is exactly 2064×2752, PNG or JPEG, RGB, no alpha, and all the same orientation. Run that once and the iPad tab goes through clean on the very first attempt, no resubmission needed. Getting the iPad set right also pairs well with nailing your other sizes — if you haven't locked those down, my Play Store screenshot sizes guide covers the Android side so both stores are handled.
Orientation mismatches cause quieter trouble. Mixing portrait and landscape shots in one iPad set makes the gallery look jumbled, so pick one and stay consistent. And letterboxing — showing a phone-ratio app inside black bars on the iPad canvas — screams that the app wasn't really designed for tablet, even when it was.
My pre-upload check is short: confirm every file is exactly 2064×2752, PNG or JPEG, RGB, no alpha, and all the same orientation. Run that once and the iPad tab goes through clean on the very first attempt, no resubmission needed. Getting the iPad set right also pairs well with nailing your other sizes — if you haven't locked those down, my Play Store screenshot sizes guide covers the Android side so both stores are handled.
Frequently asked questions
What size do iPad App Store screenshots need to be?
2064×2752 pixels, the 13-inch iPad Pro portrait size. Apple reuses that single set for every other iPad your app supports, so you don't need a separate batch per model. Landscape is the swapped 2752×2064 if your app is landscape-first.
Do I need iPad screenshots if my app is iPhone-only?
No. iPad screenshots are only required when your app actually supports iPad, including universal apps. An iPhone-only app skips them entirely and Apple never asks for them.
Can I use my iPhone screenshots for the iPad slot?
No — the pixel dimensions don't match, so App Store Connect rejects them, and a scaled-up phone screenshot looks wrong on the wider iPad canvas anyway. Build a set made for 2064×2752, and wrapping the capture in a proper tablet frame from the [device library](/frames) keeps it looking native.
What file format does Apple require for iPad screenshots?
PNG or JPEG, in RGB color space, flattened with no alpha channel. Transparency has to be removed before upload, and the dimensions must be pixel-exact because there's no auto-cropping or aspect-ratio fallback on Apple's side.
How many iPad screenshots should I upload?
You can add up to ten per language, but three to five strong ones usually beat a padded set. The gallery shows the first two or three before anyone swipes, so put your clearest, most convincing frames first and cut anything that doesn't earn its place.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.