MWM
Contact salesMWM AI
App Store Optimization

TestFlight

Also known asApple TestFlightiOS Beta Testing

Apple's official platform for distributing pre-release iOS app builds to beta testers — supporting up to 10,000 external testers per app, with separate internal testing for the dev team.

Key takeaways

  1. 01TestFlight is Apple's native iOS beta testing platform — supports up to 10,000 external testers per app + 100 internal testers (team).
  2. 02Builds stay valid for 90 days; testers install the TestFlight app and receive notifications when new builds drop.
  3. 03Public links + email invites both work; public link version is most common for broad-audience beta tests.

TestFlight is Apple's official platform for distributing pre-release iOS app builds to beta testers. Developers upload builds through App Store Connect; testers install the TestFlight app on their iOS devices and download the beta build. TestFlight handles version management, expiry, crash reporting, and tester feedback in one workflow.

How TestFlight works

  • Internal testing: up to 100 team members (App Store Connect users with appropriate roles) can test any build immediately, no review required.
  • External testing: up to 10,000 external testers per app. Builds require a one-time Apple beta-app review (usually 1-2 day turnaround) before becoming available.
  • Public links: developers can generate a public link that anyone can use to join the beta. Common for open beta programs and community-driven testing.
  • Email invitations: targeted invites to specific email addresses. Useful for closed beta tests, partner testing, or specific audience-segment testing.

Build lifecycle: each TestFlight build expires after 90 days. The developer uploads new builds as needed; testers automatically receive notifications. Crash reports flow into App Store Connect alongside feedback from in-app TestFlight UI.

TestFlight workflow vs production release: TestFlight builds are separate from production App Store releases. A developer can run multiple TestFlight builds (e.g., dev branch + release-candidate branch) in parallel without affecting production. Once a build is validated through TestFlight, it can be promoted to the App Store with the same Apple review process.

Beta testing: TestFlight vs Google Play

TestFlight (iOS)Google Play
Internal testersUp to 100 (no review)Up to 100
External testersUp to 10,000 (one-time beta review)~10K per closed track
Join methodsPublic link or email inviteClosed (email) + open testing
Build expiry90 daysTrack-based

TestFlight external builds need a one-time Apple beta-app review (1-2 days); internal builds are immediate. Both feed crash reports and tester feedback back into the developer console.

Quick answers

What is TestFlight?

TestFlight is Apple's official platform for distributing pre-release iOS app builds to beta testers. Developers upload builds through App Store Connect; testers install the TestFlight app on iOS and download builds. Supports up to 10,000 external testers + 100 internal testers per app. Free to use; integrated with App Store Connect crash reporting and feedback.

How many testers can use TestFlight?

Up to 10,000 external testers per app (covers most public beta programs) + 100 internal testers (App Store Connect team members with appropriate roles). External tester limit was raised from 1,000 in 2017 — sufficient for almost all consumer-app beta programs without needing alternative distribution.

What is the equivalent of TestFlight on Android?

Google Play offers similar beta testing through the Play Console. Three modes: **internal testing** (small team, up to 100 testers), **closed testing** (email-invited beta testers, up to ~10K per track), and **open testing** (publicly joinable beta). Similar workflow + automatic notifications. Less polished UI than TestFlight historically, but feature-equivalent in 2026.

Next reads

Back to glossary