How to invite testers to TestFlight: internal, external and public links
How to add internal and external testers in TestFlight, the 100 and 10,000 limits, groups, public links with criteria, and Beta App Review for the first build.

You invite people to TestFlight from App Store Connect, in your app's TestFlight tab. Internal testers (up to 100) must be App Store Connect users on your team. External testers (up to 10,000) can be anyone: you invite them by email or share a public link, and the first build you send them goes through Beta App Review.
Below: the differences, the steps for each kind, groups, public link settings, and a comparison table. Facts are from Apple's TestFlight overview, add internal testers and invite external testers, as of November 2026.
Internal vs external testers
| Internal | External | |
|---|---|---|
| Limit | 100 | 10,000 per app |
| Who | App Store Connect users on your team | Anyone |
| How | Email invitation | Email, or a public link |
| Review | None | Beta App Review for the first build |
| Build use | All builds, 90 days | Approved builds, 90 days |
Apple's TestFlight page says internal testers can be team members with the Account Holder, Admin, App Manager, Developer or Marketing role. Builds uploaded as TestFlight Internal Only from Xcode or Xcode Cloud can only go to internal groups.
Add internal testers
- In App Store Connect, add the person as a user first, with access to your content. Apple says people who aren't in your account can't be added to an internal group.
- Open the app's TestFlight tab and click the + next to Internal Testing.
- Name the group and create it. You can rename it later.
- Add testers (up to 100). They get an email invitation, and accept in the TestFlight app on their device, or with a redemption code on Apple TV.
Apple lets you enable automatic distribution on an internal group, so Xcode delivers new builds to everyone in it. Without that, you add builds by hand. Builds from Xcode Cloud always need to be added by hand.
Managed Apple Accounts in reserved domains can't be used to test builds.
Add external testers
Apple says you must create an internal group before you can create an external one. Then:
- Click the + next to External Testing to create a group.
- Add testers: click + next to Testers and choose Email, Existing, or Import (a CSV).
- Add a build. In the What to Test dialog you can choose Automatically notify testers. If you don't, you notify them after approval.
- Wait for Beta App Review (below). Testing starts once the build is approved.
Apple lists the Account Holder, Admin and App Manager roles as able to do this. Once a tester accepts, their name and email show in the Testers section.
Before you start, fill in your test information: Apple says the Beta App Description is required, and the Feedback Email is where testers reach you.
Groups
Apple's overview says to create groups for testers and assign specific builds to them. In practice that lets you keep, say, a "Friends" group on the stable build and a "Beta" group on the newest. Individual testers can also be added to a build directly (individual external testers can't be added to internal-only builds).
You can turn tester feedback on or off per group.
Public links
A public link lets anyone with the URL join your external beta. In the group, enable it and choose:
- Open to Anyone, or Filter by Criteria.
- An optional Tester Limit, from 1 to 10,000.
- Criteria by platform and OS: a range, a minimum OS version, a maximum OS version, or all supported versions. Apple requires at least one entry when you filter.
You can change the criteria, change the limit or disable the link from Manage at any time. Apple's TestFlight page suggests disabling the link once you reach your limit, so new people know it's closed.
Testers who join through a link are shown as anonymous in your list, though installs, sessions and crashes still appear. Treat the link like a password: anyone who gets it can join until it fills or you turn it off.
Beta App Review for the first external build
When you add the first build of a version to an external group, it goes to TestFlight App Review. Apple says the first build for a version gets a full review and later builds for it might not. Rejected builds show Rejected, and you upload a new build.
- Only one build of each version can be in review at a time.
- You can submit up to six builds for TestFlight App Review in 24 hours.
- Admins get an email when a build is approved.
Apple doesn't publish a TestFlight review time. For App Store review timing, see how long App Store review takes. Beta review is separate from the review of your App Store submission, so passing one doesn't skip the other.
Following your release
Storewatch shows where a version stands (Build uploaded, TestFlight, In review, Approved, Live), and what it's waiting for, next to your other apps. It doesn't manage testers; invitations happen in App Store Connect.
Frequently asked questions
How many testers can I invite to TestFlight?
Up to 100 internal testers and up to 10,000 external testers per app, according to Apple.
Do internal testers need Beta App Review?
No. Beta App Review applies when you add builds for external testers.
Can I add someone as an internal tester without making them a user?
No. Internal testers must be App Store Connect users with access to your content. Use external testing for everyone else.
Can a TestFlight public link have a tester limit?
Yes. You can set a limit from 1 to 10,000, filter by platform and OS criteria, and disable the link at any time.
How do testers install the app?
They install the free TestFlight app, accept your email invitation or open your public link, then install the build.
Why does the first external build take longer?
It gets a full Beta App Review. Later builds of the same version might not.