How to find beta testers for your app (and keep them testing)
Where to find beta testers for an app or SaaS, how many you need, how to recruit them with TestFlight or Google Play, and how to get feedback you can use.
In short: Recruit beta testers from people who already have the problem, start with five to ten for usability and a larger group for bugs and devices, and give each tester one clear task and an easy way to reply.
To find beta testers, start with people who already have the problem your product solves: your waitlist, your own network, and the communities where those people talk. Then add early-adopter sites and the public invite links built into TestFlight and Google Play. Five to ten well-chosen testers are enough to find most usability problems; you need more for device coverage and crashes.
The hard part is not getting sign-ups. It is getting useful feedback from people who keep using the product for more than a day. This guide covers both. Sources were checked on October 22, 2026.
Decide what the beta is for
Two goals need different testers:
- Usability and value. Does the product make sense, and does it solve the problem? You need a few people who match your target customer closely.
- Quality and coverage. Does it work on many devices, browsers and accounts? You need more people, and they can be less specific.
Write the goal down in one sentence before you recruit. It decides how many people you invite, where you look and what you ask.
How many beta testers you need
For usability, fewer is better than you think. Jakob Nielsen's article Why you only need to test with 5 users explains that each extra user mostly repeats problems you have already seen, and recommends testing with no more than five users and running as many small rounds as you can afford. Run one round, fix what you found, then run another.
For quality, the numbers are set partly by the stores. On Google Play, developers with personal accounts created after November 13, 2023 must run a closed test with at least 12 testers for 14 days before they can apply for production access. Plan for more than 12 invites, because not everyone who agrees will opt in and stay.
Where to find beta testers
1. Your waitlist and network
The people who signed up on your coming soon page asked to hear from you. Email them first, personally, with a short explanation of what you need. Former colleagues and clients who match the target customer come next.
2. Communities where your users already are
Forums, Slack and Discord groups, subreddits and newsletters around the problem (not around startups) give you testers who match your customer. Read each community's rules, take part before you ask, and post a specific request: who you are looking for, what they will test, how long it takes, and what they get. There are also communities made for this, such as Reddit's r/alphaandbetausers, but testers there are often other founders rather than your customers.
3. Early-adopter and launch sites
BetaList lists early-stage startups for people who like to try new products, and accepts startup submissions. Launch platforms such as MegaLaunch, Product Hunt or a Show HN can also bring a first wave of curious users; see the comparison of Product Hunt alternatives for more options. These audiences are good for first impressions, less good for long-term use.
4. Your existing users
If you already have a product, invite your most active users into a beta of the new feature. They know the context and are the most likely to keep testing.
Distribute the beta build
iOS with TestFlight
Apple's TestFlight lets you add up to 100 internal testers from your team and invite up to 10,000 external testers. External testers can be invited by email or through a public link you share on social media or in a newsletter, which is the easiest way to recruit people whose email you do not have. Your first build for external testers must be approved by App Review for TestFlight, so plan a little delay.
Android with Google Play testing tracks
Google Play has three testing tracks: internal testing for up to 100 testers, closed testing for a wider invited group, and open testing for anyone on Google Play. Internal testers are added by email list. Use the closed track for the 12-tester requirement if your account is subject to it.
Web and SaaS products
No store needed: create accounts with a beta flag, or a separate invite-only sign-up link. Keep the beta on the same domain if you can, so testers' accounts carry over at launch.
Get feedback you can use
Testers who are left alone forget the product in a day. Give them structure:
- One task per session. "Create your first invoice and send it to yourself" is better than "try the app".
- One easy reply channel. A short form, an email address or an in-app button. Not five.
- Ask about behaviour, not opinions. Rob Fitzpatrick's The Mom Test is a handbook on talking to customers when everyone is lying to you: ask what people did and how they solve the problem today, not whether they like your idea.
- Follow up after a few days. Ask whether they used it again, and why or why not.
- Close the loop. Tell testers what you changed because of them. It is the best way to keep them for the next round.
Keep a simple log of every problem with how many testers hit it. Fix the most frequent ones first.
Reward testers without buying opinions
Most early testers do not need money. Early access, a free plan or a discount at launch, and credit in the changelog are usually enough. Avoid rewards that depend on positive feedback, because they bias the answers you need most.
When the beta ends, the release steps in how to launch an app and the launch checklist take over. Your testers become your first public users, so invite them to the launch.
FAQ
How many beta testers do I need?
Five to ten well-chosen testers per round for usability. More for devices and crashes, and at least 12 in a 14-day closed test for new personal Google Play accounts.
Where can I find beta testers for free?
Your waitlist and network, communities where your users already talk, early-adopter sites such as BetaList, and TestFlight public links.
Should I pay beta testers?
Usually not for an early beta. Early access, a discount or a free plan at launch is enough for people who have the problem.
How long should a beta last?
Long enough for real use, often two to four weeks per round. Google Play sets a 14-day minimum for the closed test of new personal accounts.
Frequently asked questions
How many beta testers do I need?
For usability feedback, five to ten well-chosen testers per round is enough to find most big problems. For crashes, devices and edge cases you need more, and on Google Play a new personal developer account needs at least 12 testers in a closed test for 14 days before production access.
Where can I find beta testers for free?
Your own network and waitlist, communities where your users already talk, launch and early-adopter sites such as BetaList, and the public link feature of TestFlight. Paid testing panels exist but are rarely needed for a first beta.
Should I pay beta testers?
Usually not for an early beta. Early access, a discount or a free plan at launch is enough for people who have the problem. Paying makes sense for structured usability sessions with people outside your network.
How long should a beta last?
Long enough for testers to use the product in a real situation, often two to four weeks per round. Google Play's requirement for new personal accounts sets a 14-day minimum for the closed test.
Sources
