OOmnistu

Blog / Startup Guides

Startup Guides

TestFlight beta testing for iPhone apps: what Apple's documentation says about internal and external testers

Plan TestFlight groups, beta review, feedback and build expiry using Apple's published internal and external testing guidance.

OOmnistu
Reviewed 2026-11-16 · 4 min read

TestFlight is Apple's tool for sending test builds of an app to testers before it goes to the App Store. If an agency or developer builds your iPhone app, TestFlight is usually how you will first hold it in your hand. This article summarises Apple's own help pages as read on 15 November 2026. Limits and rules change, so check the pages before you plan around any number.

The steps Apple describes

  1. Provide test information: a beta description, what to test, and an email for feedback.
  2. Upload a build to App Store Connect. Apple says you may need to provide app encryption documentation after reading its export compliance page, that builds must include application identifiers within their provisioning profiles, and that a build can be tested for up to 90 days.
  3. Invite testers in groups. Apple's overview gives up to 100 internal testers (App Store Connect users with access to your content) and up to 10,000 external testers.
  4. Testers install the free TestFlight app and accept an invitation by email or public link.
  5. Watch build status and metrics, such as sessions and crashes, and resend invitations.
  6. Collect feedback. On TestFlight 2.3 or later for iOS, macOS and visionOS, testers can send feedback in the TestFlight app or by taking a screenshot inside your beta app; tvOS and older iOS versions send feedback to the email in step 1.
  7. Stop testing by expiring a build. Apple says that if you do not expire a build and then submit it to the App Store, invited testers can still test it after it goes live, and that builds become unavailable after 90 days.

Internal and external testers

Internal testers must be users on your App Store Connect account. External testers are anyone else, invited by email address, CSV import or a public link. Apple's rules on the external page:

TESTFLIGHT: INTERNAL AND EXTERNAL PATHSPrepare + uploadTest information,build and exportcompliance as needed.Internal groupApp Store Connect userswith access to your content.External groupCreate internal group first.First build: full review;later builds may not need it.Test + give feedbackInstall TestFlight,accept invitation,then test the build.External path: testing afterapproval, when review applies.INTERNAL ONLY builds cannot go to external groups. Expire a build to stop testing; builds expire after 90 days.TWO TESTER PATHSPrepare + uploadTest information, build andexport compliance as needed.Internal groupApp Store Connect userswith access to your content.External groupCreate internal group first.First build: full review;later builds may not need it.Test + give feedbackInstall TestFlight and accept invite.External path: after approval,when review applies.INTERNAL ONLY builds cannot goto external groups. Expire a buildto stop testing; builds expireafter 90 days.
A simplified path from Apple's TestFlight overview and external-tester guide. Creating an internal group is required before an external group; internal testers are App Store Connect users with access, while external testers are not. The first submitted external build needs a full review and later builds for the same version might not. This is not a review-time estimate. Builds marked TestFlight Internal Only cannot enter the external path.

Public links

A public link can be open to anyone or filtered by criteria such as device and OS version, with an optional tester limit between 1 and 10,000. Apple warns that anyone can share the link, so testers could join without a direct invite. People who join by public link show as anonymous in App Store Connect, with install date, sessions and crashes still visible. You can change or deactivate the link at any time. People invited by email appear with name and address.

Omnistu advice for a project

Limits

Two Apple help pages, the second only partly read (cut off after the email-invitation steps). The rest of that page and Apple's other TestFlight pages (such as the Apple-hosted background assets, export compliance and API) were not read. Numbers (testers, days, builds) are as Apple states them on that date. No claim about review times; Apple's pages we read give none for TestFlight. App Review Guidelines and privacy rules apply to beta builds too, and legal questions need counsel.

By Omnistu.

Sources

Previous
How to scope an app project before asking for a quote