TestFlight public link: how to get beta testers for your iOS app before launch

A TestFlight public link is the fastest way to put a beta of your iOS app in front of real people: one URL, no email list, up to 10,000 testers. It is also where many launches quietly stall. The link says "This beta isn't accepting any new testers right now", the first build sits in Beta App Review, or a few hundred people tap the link and nobody sends feedback.

This guide covers how to create a TestFlight public link, what Apple reviews before anyone can join, how to filter testers by device and OS version, how to read the public link metrics, how to fix the most common error, and where indie developers actually find beta testers. Every limit below comes from Apple's own documentation, linked throughout.

Key takeaways

• External testing allows up to 10,000 testers per app, and a build can be tested for up to 90 days.
• The first build you add to an external group goes to Beta App Review. Later builds of the same version may not need a full review.
• A public link can be Open to Anyone or Filter by Criteria (device and OS version), with an optional tester limit between 1 and 10,000.
• Testers who join by public link are anonymous, so collect emails some other way if you want to reach them on launch day.
• The usual causes of the "not accepting testers" error are no approved build in the group, an expired build, a disabled link or a full tester limit.

What a TestFlight public link is, and its limits#

TestFlight has two kinds of testers. Internal testers are members of your App Store Connect team; external testers are everyone else. You can invite external testers by email, or by a public link that anyone can open on their device to join through the TestFlight app. Apple's external testers help page says plainly what that implies: "Anyone can share this link, so testers could potentially join your testing group even if you do not invite them directly."

The numbers that shape a beta program:

Two practical consequences. The 90-day window means a long beta needs fresh builds, not one build left running. And because a public link travels, a tester limit is your only real control over how many people arrive, which matters if your backend or your own time for reading feedback is small.

Before you create the TestFlight public link#

A public link belongs to an external group, and Apple has three prerequisites:

1. An internal group first. Apple says you "must first create an internal group for internal testing" before you can create an external one. Add yourself and anyone on the team, and catch the obvious crashes there.
2. A build that is allowed in external groups. Builds uploaded as TestFlight Internal Only "can only be added to internal tester groups." If you used that option in Xcode, upload a new build without it.
3. Test information. In the TestFlight tab, the Beta App Description is required, and the Feedback Email is where testers reach you and the reply-to address on email invitations (provide test information). The App Information checkbox is on by default, which puts your approved screenshots and app category into the invitation.

You need the Account Holder, Admin or App Manager role for all of this.

Write the Beta App Description for a stranger, not for your team. It is the first thing a person who tapped your link reads, and as you will see in the metrics section, "I am not clear what this app does" is one of the reasons Apple lets people give for declining.

How to create a TestFlight public link, step by step#

1. In App Store Connect, open your app and select the TestFlight tab.
2. Under External Testing, click the add button next to the heading, name the group and click Create.
3. Select the group, click Add Builds and choose a build. You can add only one build at a time. Tick Automatically notify testers if you want testers told when it is approved.
4. Click Submit Review to send the build to Beta App Review.
5. On the group's testers tab, click Create Public Link.
6. Choose Open to Anyone or Filter by Criteria.
7. Optionally, under Tester Limit, click Set Limit and enter a number between 1 and 10,000.
8. Confirm, then copy the link and share it.

To change the criteria or the limit later, or to switch the link off, click Manage next to Public Link, make the change and click Save.

Open to Anyone or Filter by Criteria?#

Filter by Criteria lets you require a device or platform and an OS version range: from one version to another, newer than or equal to, older than or equal to, or all supported versions. Apple's TestFlight page describes the point: "To more easily enroll qualified testers and get more relevant feedback, you can set criteria, such as device type and OS version."

Use criteria when the beta depends on hardware or a new OS. A feature built for iOS 27, an iPad-only layout or a camera feature that needs a recent iPhone is wasted on testers who cannot run it. Leave the link open when you want breadth, such as a general usability beta, and use the tester limit to cap the load.

Beta App Review for external testing#

External testing is not instant. Apple's overview says: "When you add the first build of your app to a group, the build gets sent to App Review to make sure it follows the App Review Guidelines. A review is required only for the first build. Subsequent builds may not require a full review. Testing can begin once a build is approved."

A few rules from the external testers page are worth knowing before launch week:

• You can only have one build of each version in review at a time.
• You can submit up to six builds for TestFlight review in a 24-hour period.
• If a build is rejected, its status shows Rejected, and the details are under App Review in the sidebar.

Treat the first external build as a rehearsal for the real submission. A beta rejected for a missing demo account or a broken sign-in will be rejected for the same reason later, so it is better to find out now. Our guides to App Store rejection reasons and how long App Store review takes cover the common blockers and why sending an external build three to four weeks before launch saves time.

A public link can bring in thousands of testers. The useful ones are the people who match your app's audience. Photo: fauxels / Pexels

Where to find beta testers for your iOS app#

The link is the easy part. Getting the right people to tap it is the work. In order of how well they tend to convert:

1. Your own waitlist. Anyone who gave you an email because they wanted the app is your best tester. Send them the link with one sentence on what you want tested.
2. Your website and social profiles. Put the TestFlight link on your landing page as "Join the beta", next to the App Store link you will add at launch. Our guide on how to promote your app for free covers turning a website into an install channel.
3. Users of your other platforms. If you already have an Android app, a web app or a browser extension, its users are the most qualified iOS testers you will find.
4. Communities where your users already talk. A subreddit, Discord server or forum about the problem your app solves will often welcome a beta that is free and specific. Read each community's self-promotion rules first, and post as a person asking for feedback, not as an ad.
5. Beta directories. In an Apple Developer Forums thread about finding testers, another developer suggested Airport, "an App Store style app to find TestFlights." Treat directories as a bonus: their audience is people who like trying apps, not necessarily your users.

Two habits make every channel work better. Say exactly what kind of tester you need ("people who track running mileage on an iPhone") so the wrong people self-select out, and say how long the beta runs, so testers know when to expect the App Store version.

How to read your TestFlight public link metrics#

Each external group's public link shows four numbers for the last 30 days, according to Apple's tester information help page:

The most useful detail is hidden behind an information icon on Didn't Accept. People who decline can choose "It's not relevant to me", "I am not clear what this app does" or "I didn't find this app interesting." That is free conversion research for your future App Store page:

• "Not clear what this app does" means the Beta App Description and screenshots do not explain the app. Fix them now, because your store listing will have the same problem. Our guide to writing a store listing that converts helps.
• "Not relevant to me" means you shared the link in the wrong place, or your criteria are too loose.
• High Didn't Meet Criteria means the people you are reaching do not have the device or OS you require. Either loosen the criteria or change channels.

Testers who join by public link appear as anonymous and are not included in the CSV export. Their installation date, sessions and crashes still show, and tester metrics can take up to 24 hours to appear.

How to collect useful feedback from TestFlight testers#

Testers on TestFlight 2.3 or later on iOS, macOS and visionOS can send feedback in the TestFlight app or by taking a screenshot inside your beta app, which they can mark up. If the app crashes, you get a crash report, and the tester can add context. Feedback and crashes appear in App Store Connect under the TestFlight tab.

Most testers will not volunteer much, so ask for something specific. A short What to Test note for each build works better than "let us know what you think":

Build 42: new onboarding and offline mode

Please try:
1. Install fresh and finish onboarding without skipping.
2. Turn on Airplane Mode, add two entries, then reconnect.
3. Tell us (screenshot + note) anywhere you got stuck.

Known issue: dark mode colors on the settings screen.

Keep a simple rule for yourself as well: read every piece of feedback within a day during the first week. Testers who see their report fixed in the next build send more reports.

Each build lives for 90 days. A fresh build with a clear What to Test note keeps a beta active. Photo: Efrem Efre / Pexels

"This beta isn't accepting any new testers right now": how to fix it#

This is the error testers see most often, and it has its own long-running Apple Developer Forums thread. Check these in order:

• Is there an approved build in the group? A link with no build, or with a build still waiting for Beta App Review, cannot take testers. Add a build to the external group, and once it is approved, notify testers if you did not choose automatic notification.
• Has the build expired? After 90 days a build is no longer available to testers. Upload and add a new one.
• Is the link enabled? Open the group, click Manage next to Public Link and check its availability.
• Is the tester limit reached? Raise it, up to 10,000 per app. Apple itself recommends disabling the link once you hit your limit, so people "will know it's no longer accepting new testers."
• Does the tester meet your criteria? Someone on an older iOS version than your criteria allow cannot join, which shows up as Didn't Meet Criteria.

From TestFlight to launch day: keep your testers#

A beta that ends with nothing but bug reports has wasted its best asset: a group of people who already like your app. Plan the hand-off before launch:

• Collect emails separately. Public link testers are anonymous to you, so offer a newsletter or launch list in the app or on your site. That list is how you tell them the app is live.
• Line up demand for launch day. App Store pre-orders turn interest into downloads on day one; our guide to Google Play pre-registration covers how iOS pre-orders compare.
• Thank testers with something real. If your app is paid or has In-App Purchases, a free unlock for testers is a common thank-you. Our guide to App Store offer codes explains how to create and share them.
• Follow a launch plan. The launch-week visibility checklist and our list of where to submit your app cover what to do in the first days.

Once the app is live on the App Store, you can also list your app on the AppRanker leaderboard, a pay-to-rank board for mobile apps and browser extensions where the order is a plain sort on what each listing has paid and every row links straight to your App Store page. It is a simple way to keep the attention your beta built from fading after launch week.

The Android equivalent#

On Google Play, personal developer accounts created after November 13, 2023 have a stricter path: a closed test with at least 12 testers who stay opted in for 14 days in a row before the app can apply for production access. Our guide to Google Play's 12 testers rule covers it, and the same testers can often join both betas if your app ships on both platforms.

TestFlight public link checklist#

• Internal group created and the build tested there first.
• Build uploaded without the TestFlight Internal Only option.
• Beta App Description written for a stranger, and Feedback Email set.
• External group created and the first build submitted to Beta App Review.
• Public link created, with criteria if the beta needs a specific device or OS.
• Tester limit set to what you can support.
• Link shared with a waitlist, your website and one relevant community.
• What to Test note written for every build.
• Public link metrics and Didn't Accept reasons checked weekly.
• A way to collect tester emails before launch.

FAQ#

How many testers can I add with a TestFlight public link?#

Up to 10,000 external testers per app, across email invitations and public links. You can also set a tester limit on a public link, from 1 to 10,000.

Does a TestFlight public link need App Review?#

The build does. The first build you add to an external group goes to Beta App Review, and testing starts once it is approved. Apple says later builds "may not require a full review."

How long does a TestFlight build last?#

Apple says "you can test a build for up to 90 days." After that, the build becomes unavailable to testers, and you need to upload a new one.

Can I see who joined through my TestFlight public link?#

No. Testers who join by public link appear as anonymous, and they are not in the CSV export. You still see their installation date, sessions and crashes.

Why does my TestFlight link say the beta isn't accepting new testers?#

Usually because the group has no approved build, the build has expired, the link is disabled or the tester limit is reached. Check them in that order.

Can I filter who joins my TestFlight beta?#

Yes. Choose Filter by Criteria when you create the public link and require a device or platform and an OS version range. People who do not match are counted under Didn't Meet Criteria.

Image credits#

• Cover, hands typing on a smartphone next to a laptop: photo by Kaboompics.com on Pexels, Pexels License. Cropped to 1200x630.
• People using smartphones side by side: photo by fauxels on Pexels, Pexels License. Resized.
• iPhone beside a laptop: photo by Efrem Efre on Pexels, Pexels License. Resized.