How to get 12 testers for Google Play closed testing (free, 2026)

What Google actually requires

Google's own wording, from the Play Console Help page App testing requirements for new personal developer accounts:

"Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."

Three details in that sentence decide everything:

• Closed test. Internal testing doesn't count. Open testing only unlocks after you get production access.
• Opted in. Adding an email address does nothing by itself. The tester has to accept the invitation.
• Continuously, for the preceding 14 days. When you apply, at least 12 testers must have been opted in for the 14 days before. Google says testers who opt out before 14 days don't count, and someone who opts out and back in has to start a fresh 14 days.

Who the rule applies to

Until you meet the requirement, Production and Pre-registration stay disabled in Play Console.

Setting up your closed test, step by step

1. Finish your app setup. Closed testing unlocks once the required declarations on your Dashboard are complete.
2. Open Closed testing. In Play Console go to Test and release → Testing → Closed testing and click Manage track.
3. Add countries. Testers outside the track's countries can't get the app.
4. Add testers. Use an email list (up to 2,000 people per list) or a Google Group. A Google Group is easier if your tester list will change.
5. Add a feedback URL or email. It appears on the opt-in page.
6. Upload a release and send it for review. If Managed publishing is on, remember to publish once it's approved.
7. Copy the opt-in link once the track shows as published. On a first publish the link can take several hours to work.
8. Testers opt in and install while signed in with the exact Google account you added.

Google's full instructions: Set up an open, closed, or internal test.

Why closed tests fail

• Listed, not opted in. The tester never tapped "Become a tester" or never installed the app.
• Wrong Google account. The phone's Play Store is signed into a different Gmail from the one you added.
• Stopping at exactly 12. One dropout on day 10 and you're under the minimum.
• No real use. Google lists "fewer than 12 opted-in testers or insufficient tester engagement" as reasons you may need more testing.
• No changes. The application asks what you changed based on testing. Ship at least one update with fixes from tester feedback.

Ways to get 12 testers, compared

Google's community guide says recruiting through specialised testing companies doesn't break the policy, so paying is a legitimate choice. If you have more time than money, the free routes work just as well when the testers are real and stay engaged. For a deeper look, read Free vs paid Google Play testers.

Getting your testers free on App Circle

App Circle is a free community of Android developers in the same position as you. Your testing time is the currency. No real money changes hands.

1. Create a free account and add the Google Play email you test with.
2. Test other developers' apps. Apply to a campaign, get approved, join its Google Play test, and use the app. You earn virtual coins for eligible testing.
3. Post your own campaign with your opt-in link and fund it with the coins you earned.
4. Approve testers as they apply and add their emails to your Play Console list or Google Group.
5. Let the companion app do the checking. The App Circle Android companion shows testers their tasks and reports app usage, so you can see who's actually opening your app.

So far, 141 developers have run campaigns on App Circle, completing 1,569 tester jobs across 128 Android campaigns (live figures on appcircle.co.uk). A completed App Circle campaign doesn't guarantee Google's approval. Only Google decides production access.

Applying for production access

Once you've had 12 testers opted in for 14 continuous days, open your Dashboard and click Apply for production. The form has three parts:

• About your closed test: how easy recruiting was, how testers engaged, and a summary of their feedback and how you collected it.
• About your app or game: your audience, the value it offers, and expected installs in year one.
• About your production readiness: what you changed after testing, and how you decided it was ready.

Google says review usually takes seven days or less. Stuck on what to write? App Circle's free Play Console response generator drafts short starting answers in your browser. Edit them so they describe your real app and test.

Frequently asked questions

How many testers does Google Play need for closed testing?

At least 12, opted in continuously for 14 days, for personal accounts created after 13 November 2023. It was 20 until December 2024.

Does the 12 testers rule apply to my account?

Only to personal accounts created after 13 November 2023. Organisation accounts and older personal accounts aren't affected. Your Play Console dashboard will show the requirement if it applies.

What happens if a tester leaves during the 14 days?

They don't count, and if they rejoin their 14 days start again. Recruit 15–18 testers so a dropout doesn't put you under 12.

Is it enough for testers to just opt in?

It's the minimum, but Google can ask for more testing if engagement was too low. Testers should install, use the app, and send feedback, and you should act on it.

Can I get 12 testers for free?

Yes. Friends, family, communities and test-for-test exchanges are free. On App Circle you earn coins by testing and spend them on testers.

Is it allowed to use paid tester services?

Google's community guide says specialised testing companies don't violate the policy, but warns about scams charging for access to groups. Testers must be real people using your app.

How long does production access review take?

Usually seven days or less, according to Google, but it can take longer.

What questions are on the production access form?

About your closed test, about your app or game, and about your production readiness. The Play Console Helper drafts starting answers.