All posts

TestFlight beta testing: external testers and public link

· 6 min read

You have an iOS build and you want people outside your team to try it before the App Store. TestFlight is Apple's tool for that. This post covers internal and external testers, how to invite people by email or public link, what Apple says about Beta App Review, how long a build lasts, and how to get feedback you can use.

I checked Apple's pages in November 2026. Apple changes these pages, so check the numbers again before you rely on them. The overview is Apple's TestFlight page.

Internal and external testers

Apple's TestFlight overview splits testers into two kinds.

  • Internal testers are App Store Connect users on your team. Apple says you can have up to 100 of them. On the TestFlight page, the roles that can be internal testers are Account Holder, Admin, App Manager, Developer and Marketing.
  • External testers are everyone else. Apple says you can invite up to 10,000 of them.

Apple says that if you invite external testers, your build may need review. When you add the first build of your app to an external group, it goes to App Review to check it follows the App Review Guidelines. Apple says a review is required only for the first build, and later builds may not need a full review. Testing can begin once a build is approved. Apple's page doesn't say whether builds for internal testers need review.

If you have no team, you are the internal tester. To get anyone else on your build, you need an external group.

Inviting external testers: email or public link

Apple's page Invite external testers has the steps. Your role must be Account Holder, Admin or App Manager. Apple also says you must create an internal group before you can create an external one.

By email. In your app, open the TestFlight tab and pick a group under External Testing. Click the plus next to Testers. You can add new testers by email address, add existing testers, or import a CSV file. Each person gets an invitation email.

By public link. In the same group, click Create Public Link. Apple says this is useful when you don't have testers' contact details. You then choose one of two options:

  • Open to Anyone. Anyone can join with the link.
  • Filter by Criteria. You filter by device or platform and OS version. You must add at least one criterion.

You can also set a Tester Limit, a number from 1 to 10,000. Apple says to disable the link when you reach your limit, so people know it no longer takes testers. A public link is the easy way to put a build in front of strangers, which is what you want when you post it somewhere. It also means you need to watch the limit.

Testers who join through a public link show up as anonymous in App Store Connect. You still see when they installed, their sessions and their crashes. You don't get their name or email, so you can't thank them or ask a follow-up question unless they send feedback.

What testers need

Apple says testers install the free TestFlight app on their device and accept your invitation, from the email or the public link. They then install your app from inside TestFlight. For the built-in feedback, Apple says they need TestFlight 2.3 or later on iOS, macOS or visionOS. Testers on tvOS or older iOS versions send feedback by email to the address you set. Apple also says Managed Apple Accounts created in reserved domains can't be used to test builds.

Apple's TestFlight page says a tester can use your builds on up to 30 devices. Write the steps in your invite anyway: install TestFlight, open the link, tap Install.

What to prepare for Beta App Review

Apple's page on providing test information says the following are needed to share your beta with external testers:

  • Beta App Description. Apple marks this field as required.
  • Feedback Email. This is where testers can reach you through TestFlight. It is also the reply-to address on email invitations.

Apple's TestFlight page also says your builds are sent for review automatically once they're added to a group. Apple's pages don't give a review time, so don't plan your launch around one.

If your app needs a login, plan for it. I couldn't find a TestFlight-specific page that lists the sign-in fields. The related page for App Store submissions, App Review information, says that if your app requires a login, you give demo account details, and that the demo account must not expire. It also has a Notes field for anything the reviewer needs to test your app. That page is about App Store review, so check what App Store Connect asks for in your own TestFlight screen. The safe habit is the same: a working demo account that stays working.

Apple also says you can submit up to six builds for TestFlight review in a 24-hour period, and only one build of each version can be in review at a time. Don't upload ten test builds in a day.

Build expiry

Apple says you can test a build for up to 90 days, and after 90 days the build becomes unavailable to testers. You can also expire a build earlier. For a test that matters, plan the dates. Upload a fresh build before the old one runs out, and tell testers to update. If a tester opens an expired build, they have nothing to test until you give them a newer one.

Getting feedback you can use

Apple describes what testers can do in TestFlight. They can take a screenshot in your app, mark it up and send it with a comment. If the app crashes, you get a crash report, and the tester can add context. Apple's page on viewing tester feedback says you read screenshots, crash comments and written feedback in App Store Connect. You can filter by platform, app version, build group, build, OS version or device. Apple also says crash reports can be downloaded for 120 days.

The tool collects feedback. It doesn't make people give it. What works for me is a concrete task. "Tell me what you think" gets a shrug. "Sign up, create one item and tell me where you got stuck" gets a useful answer. I wrote a longer guide here: how to write a test task. For finding testers in the first place, see how to find beta testers for your app. When the notes come in, beta feedback triage turns them into a short fix list. For builds outside TestFlight, see Firebase App Distribution.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps. It is not affiliated with Apple. It doesn't replace TestFlight. It's one place to find people who will open your TestFlight link.

  • Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link.
  • You can add a test login that only signed-in testers see.
  • Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
  • The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

I can't promise how many testers or reviews your app will get. A TestSwap review is a written review on TestSwap, not in TestFlight. If you use a public link, set a tester limit that fits what you can read and act on, and read the idea behind the exchange in give a test, get a test.

Your first TestFlight test: a checklist

  1. Upload a build to App Store Connect.
  2. Create an internal group, then an external group, and add the build to the external group.
  3. Fill in the Beta App Description and a Feedback Email you actually read.
  4. If the app needs a login, have a working demo account ready.
  5. Wait for the first build to be approved. Apple gives no review time.
  6. Create a public link, or invite by email. Set a Tester Limit that you can handle.
  7. Write a short invite: install TestFlight, open the link, tap Install, then do one named task.
  8. Note the build's 90-day expiry date, and upload a new build before then.
  9. Check screenshots and crashes in App Store Connect, and write down what you fixed.
  10. Disable the public link when you hit your limit.

Try it

If you want people to open your TestFlight link, post your app on TestSwap with a test task that says exactly what to do. You get 3 credits to start, and reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).