TestFlight

Apple's official platform for distributing beta versions of iOS, iPadOS, macOS, tvOS, watchOS, and visionOS apps to testers before App Store release.

Category: Mobile Development (also: Software Engineering)

Author: Atomic Glue Editorial Team

## Definition

TestFlight is Apple's beta testing service for apps across all Apple platforms. It allows developers to distribute pre-release builds to internal testers (up to 100 team members) and external testers (up to 10,000 users per app). TestFlight handles over-the-air installation, automatic update notifications, and crash reporting. Builds expire after 90 days, and external builds require Beta App Review before distribution. TestFlight is the only officially sanctioned way to distribute iOS beta builds outside of enterprise deployment.

## Internal vs External Testing

Two testing tracks exist in TestFlight. **Internal Testing**: Up to 100 team members (App Store Connect users with Admin, App Manager, Developer, or Marketing roles). No Beta App Review required. Builds are available immediately after processing. **External Testing**: Up to 10,000 testers by email or public link. Requires Beta App Review (1-2 days typical, can be expedited). External builds must comply with the same App Store Review Guidelines as the release build. Use internal testing for rapid iteration, then external testing for broader feedback before submission.

## Build Management

Builds uploaded through Xcode or altool appear in App Store Connect. Each build gets an icon, version number, build number, and export compliance designation. You can expire builds manually or wait for the 90-day automatic expiration. TestFlight supports multiple concurrent builds, so internal testers can iterate while external testers stay on a stable beta. You can also use TestFlight for staged rollouts: release to 10% of external testers, monitor crash data, then expand.

## TestFlight vs Other Beta Distribution

TestFlight is mandatory for iOS beta distribution unless you use enterprise certificates (for internal-only apps) or ad-hoc provisioning (limited to 100 devices per device ID). Android alternatives include Google Play's Open/Closed Testing tracks and Firebase App Distribution. TestFlight's advantage is that it's integrated directly into App Store Connect and Xcode. Its disadvantage is the 90-day build expiration, the 10,000 tester cap, and Beta App Review friction for external builds.

## Note

TestFlight does not support Android. For Android beta testing, use Google Play's testing tracks (closed test: up to 100 testers, open test: unlimited) or Firebase App Distribution (unlimited testers via email groups).

## Common questions

Q: How long do TestFlight builds last?

A: 90 days from the date the build is uploaded. After 90 days, the build expires and can no longer be opened. You must upload a new build to continue testing.

Q: Can I use TestFlight for production app distribution?

A: No. TestFlight is for beta testing only. Production distribution goes through the App Store. TestFlight builds are explicitly labelled as beta builds and expire after 90 days.

## Key takeaways

• TestFlight is Apple's official beta testing platform for all Apple platforms.
• Internal testing: up to 100 team members, no review required.
• External testing: up to 10,000 testers, requires Beta App Review.
• Builds expire after 90 days and require re-upload for continued testing.
• The only legitimate way to distribute iOS beta builds outside the enterprise program.

## Related entries

• [Swift (iOS)](atomicglue.co/glossary/swift-ios)
• [App Store Optimization (ASO)](atomicglue.co/glossary/app-store-optimization-aso)

Last updated June 2025. Permalink: atomicglue.co/glossary/testflight