TestFlight Public Link: How to Recruit iOS Beta Testers Without Collecting Emails

Short answer: a TestFlight public link lets anyone with the link join your external beta without you needing their email address. You create it on an external group in App Store Connect, can limit who enrolls by device type and OS version, and can see how many people viewed and installed. Share it where your audience already is and disable it when you hit your tester limit.

When a public link is the right choice

Apple says public links are a good way to establish a group of testers if you're new to beta testing, because you don't need anyone's contact information. Email invites still suit small, known groups. Public links suit newsletters, social posts, communities and your website.

Before you create the link

The link belongs to an external group, so you need the usual external setup: test information, a beta app description, beta app review information, and a first build approved by App Review for TestFlight.

Setting criteria

Apple lets you set criteria such as device type and OS version for people who enroll through your public link. Use this when you only support recent iOS versions, or when you specifically need iPad testers. App Store Connect also shows how many people didn't meet your criteria, which tells you whether your audience matches your requirements.

Where to share it

Your own channels

Newsletter, website banner, app waitlist emails.

Communities

Subreddits, Discord servers and forums for your niche, following each community's rules on self-promotion.

Social media

A short post explaining what the app does, what you want tested and how long you need people.

Measuring the link

App Store Connect shows how many testers viewed and installed your beta from the public link. If views are high and installs are low, your beta description isn't convincing. If installs are high but feedback is low, add clearer tasks.

When to turn it off

Apple advises being thoughtful about where you share the link and when to remove it. If you reach your tester limit, disable it so people who try to join know it's closed rather than hitting an error.

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

Can I have more than one public link?

Public links belong to groups, and you can create multiple groups for different purposes.

Is a public link safe for unreleased features?

Anyone with the link can join, so assume the beta may be talked about publicly.

Do public link testers count toward the 10,000 limit?

They're external testers, and Apple's external limit is 10,000.

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.