How to Find Beta Testers for an iOS App in 2026

Quick answer: start with the people who already care about your app. These are your users, your email list, your social followers and your developer friends. Invite them through TestFlight. After your first build passes Beta App Review, TestFlight accepts up to 10,000 external testers by email invitation or public link.

Then post the public link where people look for betas. Good places are r/TestFlight, r/alphaandbetausers, the TestFlight Public Links area of the Apple Developer Forums and link lists such as awesome-testflight-link. If you have a landing page, Betabound can also announce your beta.

Give each tester a short task list and a deadline. If you do not, many testers install the build and send no feedback.

Finding testers is the easy part. The hard part is to make them open the build and give you useful feedback. This guide covers both parts.

TestFlight basics in two minutes

TestFlight is Apple's beta tool. It is the standard way to put a pre-release build on another person's iPhone. It has two types of testers, and each type has different rules.

The numbers below come from App Store Connect Help, Apple's TestFlight page for developers and its page for testers, as of October 2026.

For external testing, you also complete the test information. Apple's TestFlight page says that you must give a beta app description and Beta App Review information. You also give an email address for tester feedback.

The public link is the tool that makes everything below work. Anyone with the link can join, up to a limit that you can set between 1 and 10,000.

You can also filter testers by device and OS version, so people on an unsupported iOS version cannot join. Testers who join through a public link show as anonymous in App Store Connect. You still see their install date, sessions and crashes.

Where to find beta testers in 2026

We checked each outside source below in October 2026. The list starts with the people closest to you.

1. Your own users, email list and social accounts

People who already follow your work are the best testers. They chose your app and understand the problem that it solves. They also reply when you write to them personally.

Post the public link in your newsletter, on your social accounts and in each community that you run. For an update to a live app, current users are the first choice, because they notice what changed.

Honest note: friends and fans are kind. They tell you that the app is great. Ask them to do specific tasks and tell you where they got stuck, not whether they like the app.

2. Developer friends

Other indie developers know TestFlight. They know how to send a screenshot with notes, and they write bug reports that you can reproduce. Offer a swap: you test their build, and they test yours.

Honest note: developers are not your typical users. They look for edge cases and forgive problems that a typical user does not. Use them for bugs and crashes. Use real users to test onboarding and the first use of the app.

3. r/TestFlight and r/alphaandbetausers

Two subreddits exist for this purpose. r/TestFlight is for finding App Store beta testers. r/alphaandbetausers is broader: makers of apps and websites post there to find early users.

Both work only when your post reads as a message from a person, not as an ad.

• Read the rules in the sidebar before you post. Moderators remove posts that break the rules. The rules can change.
• Say clearly that you made the app. Hidden self-promotion is the fastest way to have your post removed or ignored.
• Post once. If you post again later, post about a new build with a real change.
• Write who the app is for, what it does and what feedback you want.
• Answer every comment. Test other people's apps in the same subreddit.
• Never offer anything in exchange for App Store ratings or reviews. Our guide on review exchanges and Guideline 5.6 explains why.

Honest note: Reddit testers try many apps. Tell them in one line why your app is worth their time.

4. Apple Developer Forums: TestFlight Public Links

The Apple Developer Forums have a TestFlight Public Links area. There, members of the Apple Developer Program share public links and ask for feedback. An Apple engineer's post about the area gives these steps:

• Describe the app and the test cases.
• Choose the platforms.
• Add the App Store category, so people can find the post.
• Turn on notifications, so you see replies.

Honest note: the audience is other developers. So this option works like option 2, developer friends, but at a larger scale. Apple calls it a secondary channel next to the TestFlight app.

When we checked in October 2026, the area did not open for visitors who were not signed in. Sign in with your developer account first.

5. TestFlight public link directories

Some sites list public TestFlight links, so people can join betas. One of them is awesome-testflight-link on GitHub. It has more than 5,000 stars and still received updates in October 2026.

To add your app, open an issue. The list marks each link as open, full, closed or deleted.

Honest note: your beta is in a long list, next to betas of well-known apps. The list is for people who want early access. Use it as a source of installs and crash data.

Put your feedback request in the What to Test note. That note may be the only text these testers read.

6. Betabound

Centercode runs Betabound. Betabound announces beta tests to its tester community for free. Its developer FAQ lists these conditions:

• A landing page that calls the product a beta.
• Clear instructions to join.
• A complete product of reasonable quality.
• No charge for access.

Betabound does not post every submission.

Honest note: you need a landing page, not only a TestFlight link. The Betabound team picks the betas that fit its audience. Betabound suits a polished beta more than an early prototype.

7. BetaList

BetaList shows pre-launch and recently launched startups. As of October 2026, its FAQ says that all submissions are paid and that there is no free option. If BetaList does not select you, you get a full refund.

Your product needs its own domain. BetaList does not accept direct App Store links or free hosting subdomains.

Honest note: BetaList is a launch audience, not a testing tool. Pay for it when you have a landing page and want early signups. To find TestFlight testers, try the free options above first.

8. Beta Family

Beta Family is a crowdtesting platform for mobile apps, with tasks, questions and test reports. As of October 2026, its free Starter plan lets you invite your own testers and Beta Family's unrated testers. Paid plans start at $49 a month.

Honest note: if you can pay and want structured reports from strangers before launch, Beta Family is a better choice than the free channels above. We compare Beta Family with Raizy on our Beta Family alternative page.

How to write a recruiting post

One post works for Reddit, the forums, your newsletter and a landing page. Keep it short. Make your request specific.

1. A title with the app type, the audience and the word TestFlight. "TestFlight beta: a budget app for people paid weekly" works better than "Check out my app!" If a subreddit's rules ask for title tags, add them.
2. One or two sentences about the problem that the app solves.
3. Who you need: the type of user, and the iPhone model or iOS version if it is important.
4. The request: how long, what to do and by when. For example: "15 minutes, three tasks, before Friday."
5. How to send feedback: take a screenshot in the app, tap the thumbnail, then tap Share Beta Feedback.
6. What testers get: early access, a thank-you in the release notes, or a free upgrade at launch.
7. The public link, with a tester limit and device criteria already set.

An example:

TestFlight beta: Weekly, a budget app for people paid every week. I'm a solo developer. I built it because monthly budgets never matched my pay. I need 10 people who track spending on their iPhone. The test takes about 15 minutes: set your payday, add three expenses and check the weekly summary. Please send feedback by Friday. Take a screenshot anywhere in the app, tap the thumbnail, then tap Share Beta Feedback. Every tester gets a thank-you in the release notes. The link is below. You need iOS 17 or later.

How many testers to invite

Invite fewer testers than you think, and run more rounds than you think. Research by Nielsen Norman Group shows that about five users per round find most usability problems. It also shows that three small rounds teach you more than one big round.

Invite a few more than five testers, because not everyone who joins opens the build. Our guide on how many testers you need covers the numbers.

Crashes are different. More installs mean more devices and more crash reports. To find crashes, use a public link with a higher tester limit.

How to get feedback you can use

Testers send no feedback when they do not know what you want. Three habits fix most of this problem:

• Write the What to Test note as a short task list. Apple's TestFlight tech talk says that testers see this note first when they open TestFlight.
• Set a deadline. Send one reminder.
• Tell testers how screenshot feedback works. Many testers have never used it. It is the easiest way for them to show you a problem.

Our guide to getting TestFlight testers to send feedback has the full process and a message template.

After launch: feedback on the live app

After your app is on the App Store, your beta testers stop testing. But you still need people to try the app and tell you where it fails. Raizy is a free feedback exchange for indie iOS developers, made for this stage.

You add your app with its App Store link and optional instructions for testers. Another indie developer installs the app from the App Store on their own iPhone. They upload a short silent screen recording or a screenshot and write notes.

A moderator checks every feedback session before any credit moves. You earn one credit for each approved feedback session that you give. You spend one credit for each feedback session on your app.

Raizy does not accept TestFlight builds. So Raizy is the next step after this guide, not a replacement for it. See how feedback on a live iOS app works.