# Guideline 2.3.3 Accurate Metadata: screenshots

> Rejected under Guideline 2.3.3 because screenshots don’t show the app in use or the iPad set is a stretched iPhone image? How to fix the listing.

**Guideline 2.3.3 — Accurate Metadata: screenshots don’t show the app in use.** Your screenshots are mostly marketing art, a splash or login screen, or the wrong device — a stretched iPhone screenshot in the iPad slot is the classic.

- App Store · Guideline 2.3.3. Accurate Metadata: screenshots don’t show the app in use.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

Your screenshots are mostly marketing art, a splash or login screen, or the wrong device — a stretched iPhone screenshot in the iPad slot is the classic.

## Why reviewers send it

Screenshots are a promise about what people will get. Apple rejects sets that are mostly marketing art, splash or login screens, or captures from the wrong device — a stretched iPhone image in the iPad slot is the most common one.

## The message App Review sends

```
Guideline 2.3.3 - Performance - Accurate Metadata

We noticed that your screenshots do not sufficiently reflect your app in use. Specifically, your 13-inch iPad screenshots show an iPhone image that has been modified or stretched.
```

The exact wording changes from one review to the next; the guideline number is what to look for.

## How to fix it

1. Use screenshots of the app’s real screens in use. Captions and frames are fine, but the app has to be what people see.
2. Use iPad screenshots taken on an iPad (13″ size), or stop offering the app on iPad.
3. Skip the login and splash screens; show the main features.
4. Replace them in App Store Connect and resubmit. A metadata-only fix keeps the same build.

The [screenshot size checker](https://capwr.app/free-tools/app-store-screenshot-sizes) tells you which App Store slot each screenshot fits and exports the missing sizes.

## What to reply in App Store Connect

Replace the [brackets] with what you actually changed:

```
Guideline 2.3.3 — We replaced the screenshots with captures of the app in use on [iPhone 6.9″ / iPad 13″], showing [screens].
```

## Got a different message?

Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other App Store rejections

- [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam)
- [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality)
- [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness)
- [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account)
- [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design)
- [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms)
- [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon)
- [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple)
- [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion)
- [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string)
- [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required)
- [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy)
- [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency)
- [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase)
- [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions)
- [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url)

## Fixed it? Send the build back to App Review

CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)