Home / ASO guides / App Store Review Guidelines explained

App Store Review Guidelines explained

Quick answer: The App Store Review Guidelines are Apple's rules for what apps can do, organised into five sections: Safety, Performance, Business, Design and Legal. You don't need to memorise them; you need to know the dozen points that cause most rejections and check them before every submission. Here they are, in plain language.

How to use the guidelines before you submit

Follow these steps in order. Each one is something we do on client work.

  1. Read the five sections once. Safety, Performance, Business, Design and Legal. Skim, then return to the ones your app touches.
  2. Map features to guidelines. Payments → 3.1; login → 4.8; accounts → 5.1.1(v); user content → 1.2.
  3. Check metadata against 2.3. Screenshots, previews, name and keywords.
  4. Run a completeness pass for 2.1. Final build, working URLs, demo account.
  5. Write review notes. Explain anything a reviewer could misread.
  6. Re-read after each WWDC. Apple updates the guidelines; check what changed.

App Store review guidelines: key rules and context

1. Safety. Objectionable content, user-generated content moderation, kids category rules, physical harm and developer information. Apps with UGC need reporting and blocking tools.

2. Performance. 2.1 completeness, beta testing rules, 2.3 accurate metadata, hardware compatibility and software requirements.

3. Business. Payments: 3.1.1 In-App Purchase, subscriptions, reader apps, and rules on other business models.

4. Design. Copycats, 4.2 minimum functionality, 4.3 spam, extensions, Apple sites and services, 4.8 login services.

5. Legal. Privacy: 5.1.1 data collection, account deletion, 5.1.2 tracking; intellectual property; gambling; VPN apps.

Common mistakes

  • Reading only after a rejection. Prevention is cheaper.
  • Ignoring user content rules. 1.2 requires reporting and blocking tools.
  • Assuming last year's rules. Guidelines change.
  • No review notes. Reviewers guess.

If you want this handled for you, our pricing page lists every fixed package.

Worked example (hypothetical)

This example is illustrative. The app is made up, and so are any numbers in it.

Suppose GymBuddy adds a community feed and a paid coaching plan. The feed brings in guideline 1.2 (user-generated content: filtering, reporting, blocking). The plan, if it unlocks in-app content, falls under 3.1.1. We'd add report and block buttons, a moderation note in the review notes, and an IAP subscription before submitting.

The guidelines behind most rejections

The table maps each point to the App Store review guidelines context. Apple revises the guidelines, so open the live document before you reply to App Review. Use the row that matches your message to decide whether to fix the build, the metadata or both.

GuidelineWhat it coversUsual fix
2.1 App CompletenessFinal builds, working URLs, no placeholder contentFix crashes, add a demo account, test every link
2.3 Accurate MetadataDescription, screenshots and previews reflect the appRe-shoot screenshots from the real app; remove claims you can't show
2.3.7Unique name, accurate keywords, no trademarked or irrelevant termsRemove competitor names and pricing from metadata
3.1.1 In-App PurchaseDigital features and content unlocked via IAPMove digital unlocks to StoreKit IAP
4.2 Minimum FunctionalityMore than a repackaged websiteAdd native, useful features
4.3 SpamNo duplicate bundle IDs or saturated copycat appsConsolidate apps; show what is unique
5.1.1 Data Collection and StoragePrivacy policy, permissions, account deletion (5.1.1(v))Add policy links, clear purpose strings, in-app deletion

How we measure the result

Once the App Store review guidelines issue is fixed, keep a record. Note the guideline or policy cited, what you changed and the reviewer's reply. Patterns show up quickly once you have a few entries.

Checklist

Copy this list into your release notes or ticket and tick each item off before you ship.

  • Features mapped to guideline numbers
  • Metadata checked against 2.3
  • Completeness pass done
  • IAP used for digital unlocks
  • UGC tools if needed
  • Review notes written

Sources

FAQ

Questions

Where are the official guidelines?

At developer.apple.com/app-store/review/guidelines.

How often do they change?

Several times a year, often around WWDC.

Are rules different by country?

Some, especially payments and certain categories.

Do they apply to updates?

Yes.

Can you check my app before submission?

Yes, as part of the rejection fix package.

How often does Apple change the App Review Guidelines?

Apple updates them several times a year, often around WWDC. Check the page and Apple's developer news before each major release.

Ready when you are

Fix your listing this week.

One fixed price, delivered as copy and files you paste yourself. No calls, no account access.

$99 one-timeDelivered in 2–3 business days2 revisionsNo login needed
Questions? Email us
Rank higher. More installs.Want your app ranked and more installs?
Get HireASO