# How to Create App Store Screenshots for Mac Apps: Sizes, Guidelines & Tools

LazyScreenshots publishes a public search API over its indexed pages; the guide is at https://www.lazyscreenshots.com/agent-access.

Source: https://www.lazyscreenshots.com/blog/app-store-screenshots-mac/
Source observed: 2026-09-19T03:00:33.180Z
Last checked: 2026-10-08T01:32:22.339+00:00
Indexed: 2026-09-19T03:07:17.695+00:00

---

# How to Create App Store Screenshots for Mac Apps: Sizes, Guidelines & Tools

**April 5, 2026 · LazyScreenshots Team**

This guide covers Mac App Store screenshot dimensions, file rules, capture and resizing commands, staging, device frames, common rejections, Xcode automation, and the complete upload workflow.

## Why App Store screenshots matter

App Store screenshots are the first visual material people see when finding a Mac app. Incorrect dimensions, blurry images, or screenshots showing the wrong features can hurt a listing. App Store Connect rejects incorrect dimensions, while listings without polished visuals can look less professional.

## Mac App Store screenshot size requirements

| Display | Required size (pixels) | Aspect ratio |
|---|---:|---:|
| Mac with Retina display | 2880 × 1800 | 16:10 |
| Mac with Retina display (alt) | 2560 × 1600 | 16:10 |
| Widescreen Mac display | 1280 × 800 | 16:10 |
| Ultra-wide (optional) | 2560 × 1440 | 16:9 |

You can upload up to **10 screenshots per localization**. The minimum is **1**; Apple recommends at least **3**. Screenshots may be landscape or portrait, although landscape is standard for Mac apps.

## File format and technical rules

- **Format:** PNG or JPEG only; PNG is recommended for UI screenshots.
- **Color space:** sRGB or Display P3; no CMYK.
- **Alpha channel:** prohibited. Flatten transparent PNGs before uploading.
- **File size:** there is no stated official hard cap, but keep images under 10 MB to reduce upload timeouts.
- **Device bezels:** do not include conflicting bezels in the screenshot itself; Apple adds frames automatically in some contexts.

Transparent regions at the edges are a common rejection cause. Flatten the image onto a solid background before uploading.

## Capture exact dimensions

A full-screen Retina MacBook Pro screenshot is described as natively producing **2880 × 1800**. Capture the full screen with **Cmd + Shift + 3**, then inspect dimensions:

```sh
sips -g pixelWidth -g pixelHeight ~/Desktop/Screenshot*.png
```

Resize to 2880 × 1800:

```sh
sips --resampleHeightWidth 1800 2880 screenshot.png
```

Resize to 2560 × 1600:

```sh
sips --resampleHeightWidth 1600 2560 screenshot.png
```

Flatten transparency by converting to JPEG and back to PNG:

```sh
# Convert to JPEG and back to flatten transparency
sips -s format jpeg screenshot.png --out screenshot.jpg
sips -s format png screenshot.jpg --out screenshot-flat.png
rm screenshot.jpg
```

## Stage your app

Before capturing:

1. Use plausible **sample data**, such as realistic project names, messages, or documents. Empty states and lorem ipsum look unfinished.
2. Hide personal or debug information, including real names, email addresses, test data, debug menus, and console output.
3. Set the app window to a clean size with balanced margins.
4. Use a clean Desktop if it appears in the capture.
5. Lead with the feature that communicates the app’s core value; do not lead with settings or preferences.

## Add device frames and marketing text

A MacBook device frame and a short headline can improve the perceived polish of a listing. Free tools described here include:

- **Shots.so** — browser-based drag-and-drop device frames with customizable backgrounds; free tier for basic needs.
- **AppMockUp Studio** — App Store screenshot templates for Apple device sizes.
- **Pika.style** — background and shadow effects.
- **Figma / Sketch** — design tools that can use Apple device-frame templates.

Keep marketing text to one short line per screenshot. Use the app’s primary font or a clean sans-serif, and describe the benefit shown rather than repeating the app name.

## Common rejection reasons

| Rejection reason | Fix |
|---|---|
| Wrong dimensions | Resize to the exact pixel values. Even 1 pixel off can trigger rejection. |
| Alpha channel present | Flatten PNG transparency onto a solid background. |
| Features do not exist | Screenshot only the shipping build; do not mock up unreleased features. |
| Pricing information in screenshots | Do not put `$4.99` or `Free` in marketing text; Apple controls pricing display. |
| Text is unreadable | Use large, high-contrast text and test at 50% zoom. |
| Inappropriate status-bar content | Hide VPN icons, low battery, and test notifications before capturing. |

## Automate with Xcode

If your Mac app has UI tests, use Xcode screenshot testing:

```swift
func testAppStoreScreenshots() {
    let app = XCUIApplication()
    app.launch()

    // Navigate to the main feature
    let attachment = XCTAttachment(screenshot: app.screenshot())
    attachment.name = "AppStore-Main"
    attachment.lifetime = .keepAlways
    add(attachment)
}
```

Run the UI tests and find screenshots in the test results. This keeps images aligned with the latest build and allows capture across localizations. `fastlane snapshot` can run UI tests across multiple device sizes and languages and organize output by locale and device class.

## Complete workflow: capture to upload

1. Stage the app with realistic data, a clean Desktop, and the correct feature visible.
2. Capture full-screen at native Retina resolution with **Cmd + Shift + 3**.
3. Verify dimensions with `sips -g pixelWidth -g pixelHeight`.
4. Resize to **2880 × 1800** or **2560 × 1600** if needed.
5. Flatten transparency if an alpha channel is present.
6. Add device frames and text using Shots.so, AppMockUp, or Figma.
7. Export as PNG, sRGB, no alpha, at exact required dimensions.
8. Upload to App Store Connect under the app’s version screenshots section.

Repeat for every localization. Each language needs its own screenshot set and localized marketing text.

LazyScreenshots captures pixel-perfect Mac screenshots and lets you annotate, resize, and export in one keystroke. We offer it for **$29 one-time**.

[Try LazyScreenshots — $29 one-time](https://www.lazyscreenshots.com/)

## Related

- [How to Resize and Compress Screenshots on Mac](https://www.lazyscreenshots.com/blog/resize-compress-screenshots-mac/)
- [Retina Screenshots on Mac: Fix DPI & Resolution](https://www.lazyscreenshots.com/blog/retina-screenshot-mac-dpi/)
- [How to Make Your Mac Screenshots Look Professional](https://www.lazyscreenshots.com/blog/make-screenshots-look-professional-mac/)

---

[Read this page’s summary](https://www.lazyscreenshots.com/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.lazyscreenshots.com%2Fblog%2Fapp-store-screenshots-mac%2F&trace=t_4cf8b4143ec0)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from LazyScreenshots’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Only q is required. No account or setup.

`GET https://www.lazyscreenshots.com/agent/faq?q={question}&trace=t_4cf8b4143ec0`

[Tool guide and examples](https://www.lazyscreenshots.com/agent-access) · [OpenAPI](https://www.lazyscreenshots.com/api/public/v1/openapi.json) · [Page TLDR form](https://www.lazyscreenshots.com/agent-tools/page-tldr?url=https%3A%2F%2Fwww.lazyscreenshots.com%2Fblog%2Fapp-store-screenshots-mac%2F). Opening a form does not execute a tool.