In this guide
TestFlight is Apple's way to hand a pre-release build to testers. This is the beginner path from upload to the first tester. Apple changes App Store Connect menus now and then, so compare each step with the linked pages (checked 2026-10-24).
What you need first
- An app record in App Store Connect.
- A build uploaded to App Store Connect. Apple's upload page lists Xcode, Swift Playground, altool, Transporter, the App Store Connect API and Xcode Cloud.
- A role of Account Holder, Admin or App Manager for the steps below, as Apple's pages state.
Step 1: upload a build
Upload your build and wait until it appears under the TestFlight tab of your app. If the upload is refused, the cause is often a repeated build number; see version vs build number.
Step 2: add test information
Apple's page on test information lists a Beta App Description (required) and a Feedback Email, which is where testers can contact you through the TestFlight app and also the reply-to address in invitation emails. External testing goes through TestFlight App Review, which may ask for further information such as sign-in details; check Apple's current pages for the fields. Writing a useful focus text is covered in what to write in test information.
Step 3: choose internal or external
- Internal testers are App Store Connect users with access to your content, up to 100 according to Apple's overview.
- External testers are everyone else, up to 10,000.
Apple's page on external testing says that to create an external group you must first create an internal group. Start internal: it is the fastest way to catch obvious problems.
Step 4: create a group and add the build
For external testing, Apple describes this path: open the TestFlight tab, click the add button next to External Testing, name the group, then choose Add Builds. A "What to Test" dialog appears where you enter what testers should focus on. Depending on the build status you then submit for review or start testing.
The first build you add to an external group goes to TestFlight App Review; Apple says the first build needs a full review and later builds for the same version might not. Plan time for this before a tester deadline.
Step 5: invite testers
You can invite by email, from existing testers or by CSV import, or create a public link (open to anyone, or filtered by criteria such as device or platform). For a public link you can set a tester limit between 1 and 10,000. Testers install the free TestFlight app and accept the invitation.
Step 6: make feedback easy
Per Apple's overview, testers on TestFlight 2.3 or later on iOS, macOS and visionOS can send feedback in the TestFlight app or by taking a screenshot in your beta app; testers on tvOS or earlier versions send email to your feedback address. Tell testers what you want them to try. Instructions to send TestFlight testers helps with that.
Things that trip people up
- A build is available for testing up to 90 days, so a build that sits idle expires.
- You can submit up to six builds for TestFlight App Review in 24 hours, and only one build of each version can be in review at a time (Apple's page).
Next: what to write in test information and plan TestFlight groups. Hub: iOS app testing. Story: TestFlight feedback before App Review.
See how AppReviewX works: private, structured feedback from other developers, in addition to your own testers.