Internal vs External TestFlight Testing: Differences Explained

TestFlight divides testers into internal and external. The difference affects who can test, whether Apple review is required, and how you distribute your build. This post explains both and where a public link or automation fits in.

Internal Testing

Internal testers are people in your App Store Connect team—developers, admins, and other roles you have added. You can have up to 100 internal testers. They get builds as soon as you upload them; no Beta App Review and no public link are involved. Best for: quick iteration with your own team. Limitation: only team members, so not for clients or external beta testers.

External Testing

External testers are anyone outside your team—clients, QA, early adopters. You can have up to 10,000. To give them access, you either submit your build for Beta App Review and then get a public link, or you invite them one by one (add user, send invite, add to TestFlight group when they accept). The public link is anonymous and only available after approval. Invitations work for private apps but are manual unless you automate them. See iOS TestFlight public link for private apps for an automated single-link approach.

Comparison Table

Limitations and Public Link

The main limitation for external testing of private apps is that Apple does not offer a public link until Beta App Review is done. If you do not want to submit for review, you must use the invitation path. That path is manual by default: add user, send invite, add to group. Automation (e.g. TF Invites) gives you one shareable link, collects emails, and handles invites and TestFlight group assignment so you get a public-link-style experience for private apps.

FAQ

What is the difference between internal and external TestFlight?

Internal = team members in your App Store Connect account (up to 100), no review. External = everyone else (up to 10,000), either via public link after Beta App Review or via per-user invitations.

Can I use a public link for external testers without Beta App Review?

Not Apple's public link. You can use an automated invite link: one URL, testers enter email, and the tool sends the invite and adds them to TestFlight. See iOS TestFlight public link for private apps.

When should I use internal vs external?

Use internal for your own team. Use external for clients, beta testers, or QA when you need more than 100 people or people outside your org.