Google Play Closed Testing
Google Play's 12 Testers for 14 Days Requirement, Explained
If you created a personal Google Play developer account after November 13, 2023, you can't publish to production until you run a closed test with at least 12 testers for 14 consecutive days. Here's exactly what that means, why it trips up most developers, and how to pass it fast.
12
opted-in testers minimum
14
consecutive days
Real
devices & Google accounts
What is the requirement?
Google Play requires new personal developer accounts to complete a closed test before applying for production access. The bar is a minimum of 12 testers who stay opted in for 14 consecutive days. Only after you hold that for the full two weeks can you request production access and distribute your app publicly on Google Play.
Who does it apply to?
The requirement applies only to personal developer accounts created after November 13, 2023. Organization (company) accounts are currently exempt. If you registered your personal account before that date, or you're on an organization account, you may not see this gate.
It used to be 20 testers
When the policy launched, the minimum was 20 testers. On December 11, 2024, Google lowered it to 12 after developers reported that recruiting 20 engaged testers was a serious blocker for small and solo teams. The 14-day duration didn't change.
Why it's harder than it sounds
The number 12 looks small, but the real challenge is the word consecutive. You need 12 people on real Android devices with genuine Google accounts who opt in and stay opted in for two straight weeks. Emulators, bots, and duplicate accounts don't count. Friends and family sign up and then forget, drop out, or never actually opt in — and if your active count slips below 12, you effectively lose progress. For most solo developers, finding and retaining real testers is the single biggest delay to launch.
How to set up closed testing, step by step
- 1
Create a closed testing track in Play Console
In Google Play Console, open Testing → Closed testing and create a new track (or use the default one). Upload your app bundle so there's a build for testers to install.
- 2
Add your 12+ testers
Add testers by email list or Google Group. You need at least 12 real Google accounts. Build in a buffer above 12 in case someone drops out during the 14 days.
- 3
Share the opt-in link
Publish the closed test and share the opt-in URL. Each tester must open the link and accept the invitation — installing alone isn't enough; they have to be opted in.
- 4
Keep 12 testers engaged for 14 consecutive days
Maintain at least 12 opted-in testers for 14 days straight. Monitor drop-offs, because falling under 12 can reset your progress in practice.
- 5
Apply for production access
Once you've held 12 testers for 14 days, go to the Play Console Dashboard, apply for production access, and complete the production-readiness questionnaire.
Common mistakes to avoid
- Counting installs instead of opt-ins — testers must accept the opt-in link, not just install the app.
- Recruiting exactly 12 with no buffer, so a single drop-out breaks the requirement.
- Using emulators or secondary accounts, which Google does not count and may flag.
- Letting engagement lapse mid-window and resetting your 14-day progress.
- Applying for production before holding 12 testers for the full, continuous 14 days.
Pass the 12 testers / 14 days requirement without the headache
TestMate gives you verified testers on real devices who opt in and stay engaged for the full 14 days — with transparent live tracking and a free re-run guarantee on eligible plans. You meet the requirement; we handle the testers.
Frequently asked questions
How many testers does Google Play require?+
Google Play requires at least 12 testers who stay opted in to your closed test for 14 consecutive days. This applies to personal developer accounts created after November 13, 2023.
What does '14 consecutive days' mean exactly?+
At least 12 testers must be opted in and remain opted in for 14 days in a row before you apply for production access. If testers drop out and your count falls below 12, the clock effectively resets, so consistent engagement matters more than a one-time signup.
Did Google change the requirement from 20 to 12 testers?+
Yes. Google reduced the minimum from 20 to 12 testers on December 11, 2024, after developers reported that finding 20 testers was difficult. The 14-day duration stayed the same.
Does the requirement apply to organization accounts?+
No. The closed-testing requirement only applies to personal developer accounts created after November 13, 2023. Organization (company) accounts are currently exempt.
Can I use emulators or fake accounts as testers?+
No. Testers must use real Android devices with genuine Google accounts. Emulators, bots, and duplicate accounts are not counted and can put your account at risk.
Do testers need to use the app every day?+
Google doesn't publish an exact daily-usage rule, but testers must remain opted in for the full 14 days and the test should show genuine engagement. Real, periodic use across the window is the safest way to satisfy reviewers.
What happens after I pass the 14-day closed test?+
You apply for production access from the Dashboard in Play Console. You'll answer a short questionnaire about your app and its testing process, then Google reviews your request before you can publish to production.
How can TestMate help me pass the requirement?+
TestMate provides verified testers on real devices who opt in to your closed test and stay engaged for the full 14 days, with transparent live tracking and a free re-run guarantee on eligible plans — so you meet the requirement without recruiting testers yourself.
This guide is for general information. Google Play policies can change — always confirm the current requirement in the official Play Console Help before applying for production access.