Why Apple Rejects App Preview Videos

Why rejections happen

Apple's app preview review is not subjective. Reviewers are checking against a specific set of technical and content requirements. Most rejections are not close calls — they are clear violations of rules that, once you know them, are easy to avoid.

The challenge is that many founders only learn these rules the hard way: by submitting, waiting, and receiving a rejection that delays the launch timeline. After reviewing hundreds of real Apple rejection messages across our client base, the causes cluster into a predictable short list. This post walks through each, in order of frequency, with the exact fix for each.

The top ten rejection reasons at a glance

1. First frame is not in-app footage
2. Wrong file format, codec, or dimensions
3. Duration outside 15–30 seconds
4. Simulator footage (subtle but detectable)
5. Misleading claims or features not in the app
6. Non-app footage elsewhere in the video
7. Pricing or offers that do not match the listing
8. Unrelated promotional text overlays
9. Competitor logos or comparisons
10. Age-rating mismatch with shown content

1. Non-app footage in the first frame

The opening frame of your preview doubles as the poster image — the still users see before tapping play, and the frame that autoplays silently in search. Apple requires this to be in-app footage.

Common mistakes: opening with a logo card, a black title screen, a lifestyle photo, a rendered device mockup, or a blank frame before the app loads. All of these can trigger rejection.

The fix: trim any intro down to zero and start on actual app UI. If you feel you need a title card, move it to a mid-preview beat or the closing frame. Never the opening.

2. Wrong file format or dimensions

Apple accepts .mov or .mp4 files encoded in H.264 or HEVC (H.265). Other codecs — ProRes, DNxHD, VP9 — fail the upload.

Dimensions must match exactly the device class you are targeting:

• 6.9": 886 × 1920 or 1080 × 1920 (portrait); 1920 × 886 or 1920 × 1080 (landscape)
• 6.5": same as 6.9"
• 5.5": 1080 × 1920 or 1920 × 1080
• iPad 13" / 12.9": 1200 × 1600 or 1600 × 1200
• iPad 11" / 10.5" / 9.7": same as 13"

Any other dimensions — even close approximations like 1079 × 1920 — will fail the upload check silently.

The fix: set the export preset to exactly one of the accepted pairs. Do not rely on "close enough." Also match 30fps frame rate exactly — 24 or 60 fails.

3. Duration outside 15–30 seconds

Under 15 seconds: rejected. Over 30 seconds: rejected. App Store Connect enforces this at upload — it will not accept files outside the range. This sounds obvious but catches teams who edit to "about 30 seconds" and end up at 30.2.

The fix: check duration to hundredths of a second in your editor. If you are at the edge, trim a few frames rather than trying to push closer to 30.

4. Simulator footage

Apple wants footage captured from a real device, not Xcode Simulator. Simulator footage has subtle visual differences — different shadow rendering, font anti-aliasing quirks, status bar appearance, occasional color shifts — that reviewers can identify.

Reviewers do not always catch simulator footage, but when they do, rejection is immediate and the written reason usually includes "must show the app running on a real device."

The fix: always record from a physical iPhone running the production build. Use QuickTime screen recording (connect device to Mac, File → New Movie Recording, select the iPhone as the source).

5. Misleading feature representations

This is the trickiest rejection category because it involves judgment, not just specs. Apple's reviewers will flag previews that:

• Show features the app does not have
• Imply pricing or terms not reflected in the listing
• Demonstrate outcomes users cannot actually achieve
• Include text claims that cannot be verified in the app itself
• Use mockup UI that is not yet built

Fitness, finance, dating, and health apps get the most scrutiny because misleading content in these categories can cause real harm.

The fix: only show what your app actually does today. If a feature is coming soon, wait. If a claim is aspirational ("lose 10 lbs"), rewrite to something the app can demonstrate.

6. Non-app footage elsewhere in the video

Even if the first frame is in-app, any non-app content in the body of the preview is a rejection risk. Specifically:

• Stock footage of people using devices
• Hands holding phones (even if the phone shows the app)
• Rendered 3D device frames wrapping the UI
• Product photography b-roll
• Cinematic b-roll unrelated to the app itself

The fix: if you want to show the device, use screen-only recording without a device frame. Apple's own marketing guidance explicitly asks for screen captures, not hands-on-phone shots.

7. Pricing or offers that do not match

If your preview shows "Free" but the app has required in-app purchases, that is a mismatch. If it advertises "50% off" and the listing does not reflect that price, that is a mismatch. Apple cross-checks preview claims against your App Store listing metadata.

The fix: remove pricing language from the preview entirely. Let the App Store's native pricing field carry that information. It is almost always more flexible for future price changes too.

8. Unrelated promotional text overlays

Apple allows text overlays — as long as they relate to the app's content and functionality. What is not allowed:

• Urgency tactics ("Only today!", "Limited time!")
• Pricing promotions in text
• Editorial praise you cannot substantiate
• Social proof numbers that are not verifiable
• Direct commands that duplicate the install button ("Download now!")

The fix: keep all on-screen text to product-framed language. Name features. Name outcomes. Describe what is on screen. Nothing else.

9. Competitor logos or comparisons

Showing a competitor's UI, logo, or name — even as a reference — will trigger rejection. Direct comparisons ("2x faster than X") are a near-certain reject. Incidental appearances (a competitor app visible in a phone's home screen for half a second) often get caught too.

The fix: frame the full device screen in-app. Never show home screens, app switchers, or third-party apps as part of the preview.

10. Age-rating mismatch

Your preview must match the app's age rating. A 4+ rated app cannot show content that would bump it to 12+ in the preview (mild cartoon violence, some suggestive themes). A 17+ app has more latitude but cannot show content that violates general App Store guidelines.

The fix: check your app's current rating. If the preview shows content the rating does not cover, either soften the preview or raise the rating (and understand the install-base tradeoff).

Less common but still seen

• Audio sync issues. Voiceover noticeably out of sync with on-screen action. Rarely rejected but sometimes flagged.
• Rapid flashing / seizure risk. Fast strobe effects can trigger accessibility-related rejection.
• Text too small to read. Overlays below roughly 20px tend to fail QA for "not legible."
• Third-party payment flows. Showing a Stripe or PayPal checkout can flag if it bypasses Apple's required in-app purchase rules for subject categories.
• Copyrighted media in footage. Music playing in the app (e.g., a demo of Apple Music) can trigger a takedown even post-approval.

What the rejection message actually looks like

Apple's rejection messages are short but specific. Typical formats:

• "Your app preview video does not show sufficient footage of the actual app in use." — Translation: too much non-app content.
• "The first frame of the app preview cannot be a title card, logo, or other non-app content." — Translation: fix the opening.
• "The app preview contains content that does not match the functionality of the app." — Translation: feature or claim mismatch.
• "The app preview duration does not meet the required length." — Translation: too short or too long. Check to hundredths.

What happens after rejection

Apple returns the rejection through App Store Connect with a brief reason. Read it carefully — the reason is usually specific enough to act on. Fix the identified issue, re-export, and resubmit. Most rejections resolve on the next submission.

If you disagree with an interpretation (common for content-judgment rejections), you can reply in the Resolution Center explaining your position. A second reviewer sometimes overturns borderline calls. Do not argue technical rejections — those are mechanical.

Resubmissions typically review same-day. Multiple rejections do not harm your app, but each costs a review cycle, which can delay a launch by 24–48 hours per round.

How to prevent rejections before submitting

A 5-minute pre-submission check catches almost all rejections:

1. Play the preview and confirm the first frame is in-app content
2. Check duration to hundredths of a second (should be ≤30.00)
3. Verify export specs: H.264/HEVC, 30fps, correct pixel dimensions
4. Scrub through and confirm every visible frame is app UI (no hands, no device frames, no stock)
5. Read all text overlays — every one must describe product functionality
6. Cross-check pricing claims against the current App Store listing
7. Confirm any in-app features shown are currently live in the production build

For a more thorough pre-flight, see our App Store preview video submission checklist.

FAQ

How long does Apple's review take?

Typically same-day for established apps, 24–48 hours for new ones or during launch periods.

Can I appeal a rejection?

Yes, through the Resolution Center. It is most effective for judgment-based rejections, not technical ones.

Does a rejection affect my app's ranking?

No. Rejections are silent to users. Only you see them in App Store Connect.

How many rejections before Apple escalates?

There is no hard limit. Multiple rejections for the same issue can trigger a human escalation from the review team, but most teams resolve within 1–2 rounds.

Can I run paid ads while the preview is pending review?

Yes — paid UA continues running against the currently live preview until the new one is approved.

The practical takeaway

If you have maintained clean production hygiene from the start — real device, correct format, in-app first frame, honest claims — most of these issues never arise. The teams that get rejected repeatedly are usually rushing or skipping the pre-submission check. Five minutes of careful review before upload prevents 95% of rejections.