TestFlight Overview

iOS visionOS macOS tvOS watchOS

TestFlight lets you distribute beta builds of your app, manage beta testers, and collect feedback. Learn more.

Make improvements to your app and continue distributing builds until all issues are resolved before you submit your app for review.

Your macOS apps must be built with Xcode 13 or later to use TestFlight for Mac. If your app includes an App Clip, you can invite testers to test the App Clip experience on its own. Testers who are invited to test your app can test both the app and the App Clip. Either the app or the App Clip can be installed on a device at a time, and testers can choose to switch between the two at any time.

Learn how to manage beta testing with the App Store Connect API.

Step 1: Provide test information

Provide test information about your app, such as a beta app description, an explanation of features to test, and an email address where feedback can be submitted. You can also choose to show approved app screenshots and your app category.

Step 2: Upload your build

Upload your build to App Store Connect. Read Cryptography and U.S. export compliance to determine if you need to provide app encryption documentation for your app. You can test a build for up to 90 days.

Note: Builds with provisioning profiles must contain application identifiers in order to be eligible for TestFlight.

Step 3: Invite internal and external testers

Create groups for testers, then assign specific builds to them. After you've added builds to a group, you can add external testers (up to 10,000 people) and internal testers (up to 100 App Store Connect users with access to your content) to test your app. If you invite external testers, your beta build may require review. When you add the first build of your app to a group, the build gets sent to App Review to make sure it follows the App Review Guidelines. A review is only required for the first build of a version and subsequent builds may not need a full review. Testing can begin once a build is approved.

Note: A Managed Apple Account can’t be used to test builds.

Step 4: Testers download TestFlight and accept your invitations

Testers install the free TestFlight app on their devices. Then they use their invitation email or a public link to accept invitations, install your app, send feedback, and get updates. Testers download and install thinned variants of your app.

Note: Setting specific criteria for your public link invitations can limit the number of external testers who can test your app.

Step 5: View tester and build information

Track tester engagement and your app’s performance by viewing build status and metrics, such as number of sessions and crashes. You can also resend email invitations to testers who haven't accepted their invitation.

Step 6: Collect feedback from testers

Testers running TestFlight for TestFlight 2.3 or later can send feedback through the TestFlight app or directly from your beta app by taking a screenshot. This feature is also available in TestFlight for Mac and Apple Vision Pro. You can view this tester feedback in the TestFlight Feedback section in App Store Connect. Testers running tvOS or earlier versions of iOS can send feedback to the email address you specified in step 1.

Step 7: Stop testing

When testing is done, you can optionally expire a build to stop testing it. If you don’t expire your build and submit it to the App Store, testers that received an invitation to test will still be able to test your build even after it goes live on the App Store. Your build will become unavailable for testers after 90 days.