TestFlight Internal vs External Testers: Differences, Limits and When to Use Each

Short answer: internal testers are up to 100 people on your App Store Connect team (Account Holder, Admin, App Manager, Developer or Marketing roles), and they can get new builds automatically. External testers can be anyone, up to 10,000, but they need a group, test information and an App Review–approved first build. Use internal for speed and external for real-world feedback.

Internal testers

Who qualifies

Members of your development team with the Account Holder, Admin, App Manager, Developer or Marketing role.

Limit

Up to 100.

Why use them

You can automatically distribute new builds to internal testers, so they're always on the latest version. That's ideal for checking every build before anyone outside sees it.

External testers

Who qualifies

Anyone you invite by email or public link.

Limit

Up to 10,000.

What you need first

A group, a build added to it, a beta app description, beta app review information, and App Review approval of the first build for TestFlight.

Why use them

They use the app the way your customers will, on their own devices, with their own data and habits.

A two-stage workflow

1. Every build to internal testers. Quick smoke test on team devices.
2. Selected builds to external groups. Once a build is stable, add it to an external group so real users can test it.
3. Different groups for different goals. Apple suggests multiple groups, for example a group focused on a new platform.
4. Read feedback, fix, repeat.
5. Submit the tested build for App Store review from App Store Connect.

Common mistakes

Treating your team as your audience

Your team knows where every button is. Customers don't.

Sending unstable builds to external testers

A crash in the first minute can lose a tester for good.

No test instructions

Apple's invite includes your beta app description, so use it to tell testers what to try.

Where to find more external testers

If your audience is small or you need specific devices, a testing service can supply external testers. TestLancer's iOS app testing works with TestFlight builds and real people on their own iPhones.

The official TestFlight facts

From Apple's TestFlight overview:

• You can add up to 100 internal testers from your team (Account Holder, Admin, App Manager, Developer or Marketing roles).
• You can invite up to 10,000 external testers by email or public link.
• External testing needs a beta app description and beta app review information, and your first build in an external group must be approved by App Review for TestFlight.
• You can share up to 100 builds, and testers can use your betas on up to 30 devices.
• Public links can have criteria such as device type and OS version, and you can see how many people viewed and installed from the link.
• Testers send screenshot feedback and crash reports, which you read in the TestFlight section of App Store Connect.

Quick checklist before you invite external testers

• [ ] Beta app description written in plain language: what's new and what to try.
• [ ] Beta app review information filled in, including a demo account if the app needs sign-in.
• [ ] A feedback email you actually check.
• [ ] Separate groups for different goals (for example, a new-feature group and a regression group).
• [ ] Public link criteria set if you only want certain devices or OS versions.
• [ ] A tester brief with three or four concrete tasks.
• [ ] A plan to read screenshot feedback and crash reports at least every other day.
• [ ] A note of what you'll change before submitting the final build for App Store review.

Mistakes that slow down a TestFlight beta

1. Sending the first external build without review notes. Reviewers need to know how to reach each feature.
2. A demo account that expires. Check it works the day you submit.
3. One giant group. Separate groups keep feedback focused and avoid sending risky builds to everyone.
4. Leaving a full public link open. Apple suggests disabling it once you reach your limit.
5. No "What to test" notes. Testers who don't know what changed rarely find what you care about.
6. Ignoring crash reports until launch week. Read them every few days while testers still remember what happened.
7. Asking testers for App Store reviews. Keep beta feedback private and honest; TestLancer never sells reviews or ratings.

FAQ

Do internal testers need beta review?

Apple's review requirement is described for external testing.

Can someone be both internal and external?

Internal testers must hold a team role. Most people you invite from outside are external.

Is there a cost for external testers?

TestFlight is part of Apple's developer tools. You pay only if you use an outside service to recruit testers.

Next step

If you need real people to test your iOS build on their own iPhones and iPads, TestLancer's iOS app testing recruits testers for TestFlight builds and returns bug reports with steps to reproduce. TestLancer does not sell reviews, ratings or installs, and nobody can promise that App Review will approve a build. You can start a project at testlancer.com.