Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

What Is the TestFlight App Used For?

The TestFlight app is Apple's free, official tool for beta testing apps before they reach the App Store. Developers upload a pre-release build to App Store Connect and invite people to try it, while testers install that build through the TestFlight app and send back feedback, screenshots, and crash reports. It is the standard, Apple-sanctioned way to put an unreleased iOS, iPadOS, macOS, tvOS, watchOS, or visionOS build in front of real users and gather real-world feedback without going through the public App Store.

What TestFlight Is and the Platforms It Covers

TestFlight is Apple's beta-distribution platform. Instead of asking testers to wrangle device UDIDs or sign provisioning profiles, a developer pushes a build to App Store Connect, and invited testers receive it over the air inside the TestFlight app. It is meant for pre-release validation: catching bugs, gathering usability feedback, and confirming a build behaves correctly on real hardware before a public launch.

TestFlight works across every current Apple platform:

iOS and iPadOS: the most common use case, covering iPhone and iPad beta builds.
macOS: distribute Mac app betas to testers without a separate channel.
tvOS: beta test Apple TV apps directly on the device.
watchOS: validate Apple Watch experiences before release.
visionOS: test Apple Vision Pro apps and spatial experiences.

Because TestFlight lives entirely inside Apple's ecosystem, it does not exist for Android. Android teams use Google Play's testing tracks instead. If your product ships on both platforms, TestFlight covers only the Apple side.

How Testers Use TestFlight

From a tester's point of view, TestFlight is intentionally simple. Once you have an invitation, the flow looks like this:

Install the free TestFlight app from the App Store on your iPhone, iPad, Mac, Apple TV, Apple Watch, or Vision Pro.
Accept your invite, either by tapping the link in an email invitation from the developer or by opening a public link or redeeming a code shared by the team.
Install the beta build from inside TestFlight. The app shows a short description of what is new and what the developer wants you to test.
Use the app as you normally would, exercising the features the developer flagged for testing.
Send feedback by taking a screenshot, annotating it, and adding written notes; crash reports are captured automatically so the developer sees them in App Store Connect.

Two behaviors are worth knowing as a tester. First, TestFlight can update beta builds automatically when the developer uploads a new version to your group, so you are always on the latest code. Second, every build expires after up to 90 days. When you see an "expired" label, the developer simply needs to ship a fresh build.

How Developers Distribute Builds With TestFlight

For developers, TestFlight is managed through App Store Connect. The distribution flow runs roughly like this:

Add test information in App Store Connect, including a beta description, what you want testers to focus on, and a feedback email address.
Upload the build from Xcode or Apple's Transporter app; the build appears in App Store Connect once processing finishes.
Create tester groups to organize who gets which build, separating internal staff from external testers as needed.
Invite testers by email or generate a public link that lets anyone with the URL join, optionally limited by enrollment criteria.
Track engagement and crash data in App Store Connect to see who installed, how the build performed, and where it failed.
Review tester feedback, then either expire the build, ship a new one, or submit the final version to the App Store.

The first build you send to an external group must pass Apple's Beta App Review, which checks the beta against the App Review Guidelines. Builds for internal testers skip that review and are available right away.

Internal vs. External Testers

TestFlight splits testers into two groups. Internal testers are your own team; external testers are everyone else. The distinction controls how many people you can reach, how fast they get builds, and whether Apple reviews the beta first.

Aspect	Internal Testers	External Testers
Maximum number	Up to 100	Up to 10,000
Who they are	Team members with an App Store Connect role	Anyone invited by email or public link
Beta App Review	Not required	Required for the first build to a group
Build availability	Immediate	After review approval
Best for	Fast internal validation	Broad, real-world feedback

Internal testers: capped at 100, these are people on your team who hold an Account Holder, Admin, App Manager, Developer, or Marketing role in App Store Connect. They get every build the moment it finishes processing, with no review, which makes them ideal for quick smoke tests of fresh code.

External testers: up to 10,000 people from outside your organization, invited individually by email or in bulk through a public link. The first build you push to an external group goes through Beta App Review, after which subsequent builds usually clear faster. This is the path you use when you want feedback at scale before launch.

Build Expiry, Limits, and Beta App Review

A few hard limits shape how you plan a TestFlight cycle:

Build expiry: each build is testable for up to 90 days from upload, then it expires and must be replaced.
Internal tester cap: up to 100 team members with an App Store Connect role.
External tester cap: up to 10,000 testers per app.
Devices per tester: a single tester can install your beta on up to 30 devices.
Concurrent builds: up to 100 builds can be active for testing at the same time.
Beta App Review: required once per external group's first build to confirm the beta follows the App Review Guidelines.

Where Real-Device Testing Complements TestFlight

TestFlight is excellent at getting a build into the hands of human testers, but it depends on those testers owning the right devices and OS versions and remembering to report what they see. That leaves gaps: you cannot guarantee coverage of every iPhone and iPad model, every iOS version, or edge cases that a casual tester never triggers.

This is where a real device cloud complements the TestFlight workflow. You can take the same iOS build you distribute through TestFlight and run it across many real iPhones and iPads on different iOS versions using TestMu AI (Formerly LambdaTest)'s Real Device Cloud, capturing logs, screenshots, and video in controlled, repeatable sessions. TestFlight gathers organic feedback from real people; a real device cloud gives QA teams deterministic coverage across hardware and OS combinations the tester pool may never cover.

Frequently Asked Questions

Is the TestFlight app free to use?

Yes. The TestFlight app is free to download from the App Store, and testers pay nothing to install and try beta builds. Developers need a paid Apple Developer Program membership to upload builds and invite testers through App Store Connect, but the testing itself carries no separate TestFlight fee.

Can I use TestFlight on Android?

No. TestFlight is exclusive to Apple platforms, so it runs on iOS, iPadOS, macOS, tvOS, watchOS, and visionOS only. There is no Android version, and TestFlight invite links cannot be opened on an Android device. Android beta distribution uses Google Play's internal, closed, and open testing tracks instead.

Why did my TestFlight beta build expire?

Every TestFlight build is available for testing for up to 90 days from upload. Once that window passes, the build expires and testers can no longer open it. The developer needs to upload a fresh build to continue testing. Developers can also expire a build manually before the 90 days are up.

What is the difference between internal and external testers?

Internal testers are up to 100 members of your team with an App Store Connect role, and they get builds immediately with no review. External testers can be up to 10,000 people invited by email or public link, and the first build sent to an external group must pass Apple's Beta App Review before testing starts.

Do testers get new TestFlight builds automatically?

When a developer uploads a new build to a tester's group, TestFlight notifies the tester and can update the beta automatically if automatic updates are enabled. This keeps everyone testing the latest code without manually hunting for new versions, which is one of TestFlight's main advantages over manual sideloading.

How do testers send feedback through TestFlight?

Testers can take a screenshot inside the beta app, annotate it, and submit it with written notes directly from TestFlight. Crash reports are captured automatically, and testers can add context. All of this feedback appears in App Store Connect, where the developer can filter it by platform and OS version.