ShipZen
TestFlight Internal vs External Testers: Limits, Review
Updated August 31, 2026 · by Sardorbek Rakhimov
TestFlight has two kinds of testers, and choosing wrong costs you either reach or speed: internal testers can receive eligible builds after processing without TestFlight App Review but must be App Store Connect users, while external testers can scale to thousands and require review for the first external build. Everything below comes from Apple's current TestFlight documentation.
The decision table
| Internal testers | External testers | |
|---|---|---|
| Who | Eligible App Store Connect users with access to the app | People outside the team invited by email or an eligible public link |
| Limit | Up to 100 people per app | Up to 10,000 people per app |
| Devices | Up to 30 devices per tester | Up to 30 devices per tester |
| Review | No TestFlight App Review; distribution still waits for processing and any required compliance | The first external build requires review; later builds may not require a full review |
| Best for | Daily builds, smoke tests, pre-release checks | Public betas, waitlists, feature validation at scale |
The catch on the internal side: those 100 people must be actual App Store Connect users on your team (Account Holder, Admin, App Manager, Developer, or Marketing) with access to the app. Internal testing is not a way to sneak friends in — adding someone to your team hands them real account permissions. Friends and beta communities belong in an external group. Apple documents the 30-device allowance for testers on its TestFlight overview page.
Beta App Review is not App Review
When you add the first build to an external group, Apple sends it through TestFlight App Review, which checks the build and accompanying beta metadata against the App Review Guidelines before external testing can begin. Later builds for the same version might not need a full review, so do not promise a fixed review path or turnaround. Passing TestFlight App Review does not approve an App Store version; App Store submission remains a separate review workflow, covered by the rejection checklist. See Apple's external-tester workflow.
Groups and public links
Groups are the main way to organize testers and assign builds: you can create multiple groups (say, "Team", "Beta wave 1", "VIP users") and assign specific builds to each. Apple also supports adding eligible individual testers directly to a build. See Add testers to builds. External groups can invite testers two ways:
- Email invites — you invite specific email addresses.
- Public link — anyone who meets any criteria can join until the optional cap you set; criteria can cover device and OS requirements. Apple: Invite external testers.
Feedback, sessions, and crashes
On supported Apple platforms, testers can send feedback through TestFlight, including screenshots and crash context. App Store Connect also reports build and tester metrics such as sessions and crashes. Availability varies by platform and OS version, so check Apple's current feedback documentation and build metrics documentation for the testers you support.
Build expiry and beta hygiene
- A build can be tested for up to 90 days and becomes unavailable after that window. Longer programs need a newer build. Apple: TestFlight overview.
- Apple says you can share up to 100 builds and test multiple builds at once. Apple: TestFlight.
- You can expire a superseded build before automatic expiry; internal and external testers can no longer install it. Apple: Stop testing a build.
Where ShipZen fits
Beta state lives in a different corner of App Store Connect than the release you are preparing, so the "which group has which build, and who gave feedback" question means tab-hopping. ShipZen, a native macOS App Store Connect client, shows TestFlight builds, groups, testers, and feedback alongside your release metadata — one workspace from beta to pre-submission validation, connected through your own API key.
Sources and verification
Verified August 31, 2026 against Apple's current TestFlight overview, internal-tester, external-tester, feedback, metrics, and build-expiry documentation linked above. Limits and workflows can change, so recheck Apple before opening a beta. See About ShipZen for authorship and verification practices, and Security for the product's access and write-approval boundaries.
App Store Connect, the way you need to see it. One email at launch, no spam.
Join the waitlist