Overview: Navigating Apple's TestFlight Quotas
Managing pre-release testing on Apple TestFlight requires understanding Apple's platform quotas. Developers who scale up beta programs frequently run into unexpected walls: finding out their internal tester limit is shared across all apps in their account, hitting the 10,000 external tester ceiling, or having builds expire mid-sprint.
Apple divides quotas across different administrative scopes—some limits apply to your entire Apple Developer organization, others apply to an individual application, and others apply to specific beta groups.
Using FlightDeck's Model Context Protocol (MCP) server, your AI coding assistant can audit your group memberships, check active build lifespans, and inspect public link capacity.
This guide provides an authoritative breakdown of Apple's current TestFlight limits, explains how invitation states affect quota consumption, and shows how to check capacity using natural-language AI prompts.
1. Master Summary of Official Apple TestFlight Quotas
Apple governs TestFlight capacity through the following official quotas (current under the Apple Developer Program):
+-----------------------------------------------------------------------------------+
| TESTFLIGHT CAPACITY HIERARCHY |
+-----------------------------------------------------------------------------------+
| |
| [ORGANIZATION / ACCOUNT SCOPE] |
| - Internal Testers: Up to 100 users total across ALL apps in your account. |
| - Team Role Requirement: Must be added under "Users and Access" with an assigned |
| role (Account Holder, Admin, App Manager, Developer, or Marketing). |
| - Device Limit: Each tester can install builds on up to 30 devices. |
| |
| [PER-APPLICATION SCOPE] |
| - External Testers: Up to 10,000 testers total per application (Bundle ID). |
| - Shared Pool: The 10,000 slots are shared across all external groups |
| (email invitations and public link joiners). |
| - Device Limit: Each tester can install builds on up to 30 devices. |
| |
| [PER-BUILD & LIFECYCLE SCOPE] |
| - Build Expiration: Exactly 90 calendar days from upload timestamp. |
| - What to Test Character Limit: Up to 4,000 characters per localization. |
| |
| [PER-GROUP / PUBLIC LINK SCOPE] |
| - Public Link Limit: Configurable from 1 to 10,000 testers per link. |
| - Public Link Cap: Capped by the remaining external tester quota for the app. |
+-----------------------------------------------------------------------------------+
| Resource / Quota | Maximum Limit | Administrative Scope | Review Requirement | Authoritative Source |
|---|---|---|---|---|
| Internal Testers | 100 testers (up to 30 devices each) | Account-Wide (Shared across all apps owned by your Apple Developer team) | Zero. Immediate access upon automated ingestion processing. | Apple Developer Documentation & App Store Connect Help |
| External Testers | 10,000 testers (up to 30 devices each) | Per-Application (Distributed across email invites and public links) | Beta App Review required for the first build of any marketing version. | Apple Developer Documentation & App Store Connect Help |
| Public Link Capacity | 1 to 10,000 | Per-Group (Configurable via publicLinkLimit) | Target build must be approved by Beta App Review. | App Store Connect Help (Overview of TestFlight) |
| Build Lifespan | 90 calendar days | Per-Build (Calculated strictly from initial upload time) | Cannot be extended; must upload new build to continue testing. | Apple Developer Documentation (TestFlight Overview) |
2. Scope Distinctions: Account-Level vs. App-Level
A common misunderstanding is assuming that every application receives 100 internal testers.
The Account-Wide Internal Tester Pool
Your 100 internal testers limit is shared across your entire developer account.
- If you have 5 apps and assign 20 team members to each, you have consumed your entire 100-tester internal quota.
- Adding an internal tester requires creating an Apple account for them under App Store Connect $\rightarrow$ Users and Access. They must hold an assigned role such as Admin, App Manager, Developer, or Marketing. Users with Customer Support or sandbox-only roles cannot be added as internal testers.
The App-Specific External Tester Pool
By contrast, the 10,000 external tester limit applies separately to each individual application.
- App A can have up to 10,000 external testers.
- App B can also have up to 10,000 external testers.
- External testers only require an email address or public link enrollment; they do not consume team user seats in Users and Access.
3. How Tester States Affect Available Quota
When tracking capacity, you must distinguish between different tester enrollment and engagement states:
[Candidate Email] ──> [Invited] ──> [Accepted] ──> [Installed] ──> [Revoked / Removed]
│ │ │ │
Consumes 1 Consumes 1 Consumes 1 Reclaims 1
Quota Slot Quota Slot Quota Slot Quota Slot
- Invited (Pending): When you dispatch an email invitation, Apple immediately deducts 1 tester from your 10,000 external quota, even before the recipient opens the email or accepts.
- Accepted: The user accepted the invitation and linked their Apple ID to your beta program.
- Installed: The user downloaded and launched the build on at least one physical device.
- Revoked / Removed: When you remove a tester from the app or delete their invitation, that slot is immediately reclaimed, increasing your available capacity.
Public Link Quota Mechanics: Testers who join via a public link consume quota only upon tapping Accept in the TestFlight app. If your public link limit is set to 500, but your app already has 9,800 email testers, only 200 public link testers will be able to join before hitting the app-level 10,000 cap.
4. The 90-Day Build Expiration Clock
Apple enforces a strict 90-calendar-day lifespan on every TestFlight build:
- Automatic Deactivation: Exactly 90 days after the build finishes uploading, TestFlight deactivates it. Testers who attempt to open the app will see an alert stating: "The beta for [App Name] has expired."
- No Extensions: Apple does not provide any mechanism to extend the expiration date of an existing build.
- Continuous Delivery Cadence: To prevent testing interruption, engineering teams should establish a release cadence that uploads a fresh build at least once every 60 to 75 days.
- Retracting Broken Builds: If a build contains a critical bug, you do not have to wait 90 days; you can immediately expire it in the App Store Connect portal or retract group distribution via FlightDeck. See our guide on How to Retract or Expire a Broken TestFlight Build Immediately.
5. Auditing TestFlight Capacity via AI Prompts
You can instruct your AI coding assistant to inspect your current beta groups, active build expiration dates, and configured limits using FlightDeck:
Using FlightDeck, inspect the TestFlight beta groups and recent builds for [App Name]. Summarize configured groups, identify internal versus external cohorts, report any configured public link limits, and check the expiration dates of active builds. Clearly note which aggregate account-wide metrics must be verified directly in App Store Connect. Do not stage or execute any changes. What the Assistant Inspects:
- Calls
apps_listto locate the application record. - Calls
beta_groups_list(appId: "<appId>")to retrieve all groups: InspectsisInternalGroupflags. CheckspublicLinkEnabledandpublicLinkLimit. - Calls
builds_list(appId: "<appId>", limit: 10): * Calculates days remaining before the 90-day expiration date for active builds based onuploadedDate. - Explains portal verification steps for account-wide user quotas that Apple's API does not aggregate into a single balance metric.
6. What Can Be Inspected via API vs. Web Portal
Because Apple's REST API exposes certain aggregate metrics only to authenticated web sessions, developers should know where each metric lives:
| Metric / Resource | Inspectable via FlightDeck MCP | App Store Connect Web Portal Location |
|---|---|---|
| Beta Group Names & Types | beta_groups_list | TestFlight $\rightarrow$ Group navigation sidebar |
| Public Link Limits & URLs | beta_groups_list (publicLinkLimit, publicLink) | TestFlight $\rightarrow$ [External Group] $\rightarrow$ Public Link tab |
| Build Expiration Timestamps | builds_list / build_get (uploadedDate + 90 days) | TestFlight $\rightarrow$ iOS Builds table (Shows expiration date) |
| Enrolled Group Testers | Queryable via betaTesters_getCollection | TestFlight $\rightarrow$ External Groups overview header |
| Account-Wide Internal User Quota | Portal only | Users and Access $\rightarrow$ TestFlight Internal Testers tab |
Summary of Best Practices
- Reserve Internal Seats: Because internal tester seats are capped at 100 across your entire developer account, reserve them for active engineering, QA, and executive staff. Use external beta groups for friends, family, and public testers.
- Cap Public Links Conservatively: Always configure
publicLinkLimit(e.g. 250 or 500) when launching public links to prevent uncontrolled quota exhaustion. - Monitor 90-Day Expiration: Set calendar reminders or automate CI/CD pipeline uploads every 30 to 60 days to ensure testers never encounter an unexpected expiration screen.
- Prune Inactive Testers: Periodically review external tester lists and remove users who haven't installed or launched builds in over 60 days to reclaim valuable quota slots.