Did Apple change who can test builds in TestFlight?

Did Apple change who can test builds in TestFlight

Yes. Apple still lets you test builds with two groups, internal testers and external testers, but the rules are not the same. Internal testers are members of your App Store Connect team and are capped at 100 per app. External testers are people you invite by email or public link, and Apple allows up to 10,000 of them per app. Apple’s TestFlight pages describe both limits directly.

The part people get wrong is the internal-testing limit. Internal testing is not 10,000 testers. It is 100. Apple says internal testers are App Store Connect users with access to your content, and the internal tester cap is 100 per app. If you need more people than that, they belong in external testing, not internal testing.

External testing is the large pool. Apple says you can invite up to 10,000 external testers per app, using email or a public link. Apple also says you can set an optional tester limit for a public link, with values between 1 and 10,000. That means the public link can be narrower than the platform maximum, but it cannot exceed it.

The practical split is simple. Use internal testers when the people already sit inside your App Store Connect team and need access to active builds fast. Use external testers when you need people outside the account, such as customers, contractors, or a broader beta group. Apple’s documentation says internal testers can access all active builds, while external testers are invited separately through TestFlight flows.

Apple also keeps a rule that catches teams off guard: managed Apple accounts created in reserved domains cannot be used to test builds. That matters for schools, businesses, and organizations that use managed accounts, because those accounts may exist in your Apple environment but still be unusable for TestFlight testing. Apple calls this out on its TestFlight help pages and glossary pages.

Another detail that matters in practice is review. If you add external testers, Apple says the first build for that app version is sent to TestFlight App Review before those testers can use it. Apple says later builds for the same version may not need a full review. Internal testing does not have that same external-review step when you are only using internal testers.

The limit change people confuse with TestFlight is from Google Play, not Apple. Google Play’s closed testing rules are different, and DevConnect’s guidance follows those rules for Play developers. That is a separate system from TestFlight. If you are deciding where to send testers, keep the two platforms apart. Apple’s TestFlight cap is 100 internal and 10,000 external. Google Play’s testing gate is a different policy entirely.

If your team is trying to move fast, the workflow is usually this: put teammates who already have App Store Connect access into internal testing, then create an external group for everyone else. Apple’s docs say you create groups, add builds, and then invite testers. That sequence matters because external testers need the build routed through the external TestFlight path, while internal testers are tied to your team roles.

For teams comparing beta tools, Apple’s own docs make the boundary clear. TestFlight is for team members, specific external users, or the general public. Internal testers are limited to your App Store Connect team roles. External testers are everyone else you choose to invite, up to the per-app cap. That is the current shape of TestFlight testing, and it has a clean answer: Apple did not blur the categories, it keeps them separate.

If you are checking whether a build can go to TestFlight right now, use this quick test. If the person is in your App Store Connect team with the right role, they can be an internal tester. If they are not, they must be invited as an external tester, and the first external build for that version must clear review. That is the inconvenient part, because the route is different even when the app and build are the same.

For DevConnect readers, the useful takeaway is not that Apple opened TestFlight to more people. The useful takeaway is that Apple gives you two lanes. One lane is for your team, one lane is for outside testers. If you need a place to coordinate real exchange-based testing across apps you own, DevConnect sits outside Apple’s system and points people toward reciprocal testing rather than paid shortcuts. https://devconnectplatform.com

What changed in TestFlight

Apple’s current documentation shows the answer in the limits and categories, not in a new product model. Internal testers are still App Store Connect users with access to your content, and the cap is still 100 per app. External testers are still invited separately, and the cap is still 10,000 per app. The names and thresholds are spelled out in Apple’s help pages and glossary pages.

What should I use if I want more than 100 people to test

Use external testing in TestFlight. Apple’s documentation says external testers can go up to 10,000 per app, and they can join by email or public link. If you need a very large beta group, that is the path Apple provides. Internal testing is not the path for that size.

Do internal testers need App Review

Apple says no extra testing information is required if you invite internal testers only. External testing is different, because the first build of a version goes through TestFlight App Review before external testers can use it. That split is one of the main reasons people choose internal testing first when they are still moving fast.

Can I use a public link for any number of testers

No. Apple lets you create a public link for an external group, and you can set a tester limit from 1 to 10,000. The link is flexible, but the cap is still the cap. If you need more than that, you need another app or another approach, not a bigger TestFlight link.