A finished build can still fail App Review because of its App Store screenshots or metadata.
Apple treats the product page as part of the submission. Its guidelines require descriptions, screenshots, previews, privacy information, and other metadata to reflect the app's core experience accurately.
Some problems stop you before review. App Store Connect may reject an unsupported screenshot format, incorrect dimensions, transparency, or a missing field. Other problems reach a reviewer but can lead to rejection because the content is inaccurate, misleading, irrelevant, or uses protected material.
Screenshot mistakes that can trigger rejection
Apple's guideline 2.3.3 says screenshots should show the app in use, rather than only title art, a login page, or a splash screen. Text and image overlays are allowed, but they must explain the real experience.
Check that your screenshots:
Show current app functionality
Match the submitted build and platform
Don't advertise unavailable features
Identify content requiring an In-App Purchase or subscription
Use fictional account information instead of personal data
Avoid misleading imagery or unsupported claims
Meet Apple's current specifications
Apple accepts between one and ten screenshots in JPEG or PNG formats. Exact dimensions depend on the platform and display class, so use the current App Store screenshot guidelines rather than an old export preset.
Correct dimensions solve only the technical part. A perfectly sized screenshot can still violate content rules.
Metadata must describe the app people receive
Guideline 2.3 requires metadata to remain accurate and current. This includes the app name, subtitle, description, keywords, screenshots, previews, and privacy information.
Common risks include:
Describing a feature reviewers can't access
Hiding that shown content requires an additional purchase
Leaving placeholder copy or broken URLs
Adding false prices or unverifiable claims
Using irrelevant keywords, popular app names, or competitor terms
Showing an experience that differs from the submitted version
Review notes aren't public marketing copy. Use them to explain non-obvious features, provide access details, and tell the reviewer how to reach anything shown on the product page.
The App Store metadata checklist provides a field-by-field review. The publishing guide covers the complete submission workflow.
Localization errors create visible inconsistencies
A French product page shouldn't contain Spanish screenshot copy. Even when that doesn't create a specific rejection by itself, it creates an obvious quality and accuracy problem.
App Store Connect uses your primary language or the next relevant localization when no matching localization is available. Apple also says that when you add a language, screenshots initially default to the primary language.
Inspect every locale manually. Check the screenshot language, visible UI, app name, subtitle, purchase wording, and claims together. Don't assume fallback behavior produced the intended page.
The App Store localization guide explains how to manage metadata and visual assets as one system.
Apple trademarks require particular care
Apple's trademark list identifies “App Store” as an Apple service mark. Guideline 2.3.7 also says developers shouldn't pack metadata with trademarked terms, popular app names, pricing information, or irrelevant phrases to manipulate discovery.
This became a real issue during a Shipper submission. The metadata included “App Store”, and Apple rejected the submission because it used an Apple trademark.
That experience is useful, but it doesn't prove that every contextual mention of “App Store” is prohibited. The field, purpose, wording, and current guidance matter. Describing legitimate compatibility differs from inserting a protected term into an app name, subtitle, or keyword field to attract searches or imply endorsement.
Review Apple's current trademark guidance whenever metadata uses Apple product or service names. Remove competitor trademarks unless you have a valid and authorized reason to use them.
Final screenshots and metadata checklist
Screenshots
Show the app in use
Match the submitted build
Use supported formats and dimensions
Identify paid content where required
Remove personal data
Verify every claim
Metadata
Remove placeholders and broken URLs
Describe only available functionality
Use relevant keywords
Avoid false pricing and unverifiable claims
Explain non-obvious features in review notes
Localization
Open every locale in App Store Connect
Match screenshot copy with its localization
Check localized UI and purchase language
Confirm fallback assets intentionally
Trademarks and consistency
Review Apple and third-party trademark use
Compare the build, screenshots, and metadata
Confirm that they tell one accurate story
Shipper can help organize screenshot sets and metadata, keep localizations aligned, adapt layouts to Apple specifications, preview assets, and publish them to App Store Connect. It reduces workflow mistakes, but it can't guarantee approval or replace a compliance review.
FAQ
Can Apple reject an app only because of its screenshots?
Yes. Screenshots are reviewed metadata. Apple can reject a submission when they misrepresent the app, show inappropriate content, use protected material, or violate the App Review Guidelines.
Can I use Apple brands in my app metadata and screenshots?
Context matters. Apple prohibits stuffing metadata or screenshots with trademarked terms. Review the relevant field and Apple's current trademark guidance rather than assuming every use is allowed or forbidden.
Do screenshots need to match each localization?
Localized screenshots should match the language and experience presented to that audience. Check each locale because primary-language or fallback assets may appear when localized assets are missing.
Conclusion
An App Store metadata rejection is often preventable. Keep screenshots truthful, metadata specific, localizations consistent, and trademark use careful.
Treat the product page as part of the product Apple reviews. A final side-by-side check of the build, screenshots, and metadata can catch small mistakes before they delay your release.
