Google Play 12 Testers & 14-Day Rule Explained
Last updated: 5 November 2026
Quick answer
If you have a personal Google Play developer account created after 13 November 2023, you must run a closed test with at least 12 opted-in testers for 14 continuous days before you can apply for production access and publish your app publicly.
What is the 12 testers / 14-day rule?
In November 2023 Google introduced a new testing requirement for personal developer accounts. Before an app can be released to everyone on Google Play, it must first be tested by real users on the closed testing track. The goal is to reduce low-quality and abandoned apps on the store by making sure every new developer has had real people use their app first.
When the rule launched, the minimum was 20 testers. In December 2024 Google lowered it to 12 testers. The 14-day duration stayed the same.
Who does the rule apply to?
- Applies: personal developer accounts created on or after 13 November 2023.
- Usually does not apply: organization (business) accounts, and personal accounts created before that date.
The simplest way to check is your Play Console dashboard. If the rule applies, you will see an "Apply for production" section with a tester and day counter.
What exactly counts as a tester?
A tester counts towards the 12 when they:
- Are added to your closed test (via an email list or Google Group).
- Opt in using your closed testing link while signed in to that Google account.
- Stay opted in for the whole 14-day period.
Google does not publish a minimum amount of daily usage, but when you apply for production it asks how you recruited testers, how engaged they were, and what feedback you received. Testers who actually install and use the app give you much better answers to those questions.
How do the 14 days work?
The count starts once you have at least 12 opted-in testers on a published closed testing release, and it must run for 14 days in a row. If testers opt out and you fall below 12, you risk the count restarting. That is why it is wise to start with more than the minimum, for example 14 to 20 testers, so one or two drop-offs do not cost you two weeks.
Step-by-step: how to complete the closed test
- In Play Console, open Testing → Closed testing and create a track (or use the default "Closed testing - Alpha").
- Upload your app bundle (AAB) and create a release.
- Under Testers, add an email list or Google Group with at least 12 testers.
- Complete the store listing and app content sections, then send the release for review. Closed testing releases are reviewed too.
- Once it is approved, share the opt-in link with your testers and make sure each of them opts in and installs the app.
- Keep at least 12 testers opted in for 14 continuous days, collect their feedback, and ship fixes.
- When the dashboard shows the requirement is met, apply for production access. See our production access guide.
The hard part: finding reliable testers
Most developers get stuck on finding 12 people who will opt in and stay active for 14 days. Common approaches are:
- Friends, family and colleagues: free, but people forget to opt in or uninstall the app partway through.
- Tester-exchange communities (Reddit, Discord, Telegram): free, but you have to test other people's apps in return, and engagement is often low.
- A managed testing service: paid, but testers are committed for the full period and you get tracking and feedback.
Closed Test Hub is a managed service. You share your opt-in link, upload our tester CSV to Play Console, and real testers on physical Android phones use your app every day. Your dashboard shows a tester-by-day grid for all 14 days, and every plan includes extra testers above the minimum (14 on Starter, 24 on Professional) to cover drop-offs.
Common mistakes that cost you time
- Using internal testing instead of closed testing. It does not count.
- Adding testers but never sharing the opt-in link, so nobody actually opts in.
- Starting with exactly 12 testers and losing one on day 10.
- Not keeping notes on feedback and fixes, which you will need when you apply for production.
Frequently asked questions
Is it 12 testers or 20 testers?
12. Google originally required 20 testers when the rule launched in November 2023, then lowered it to 12 in December 2024. Your Play Console dashboard shows the exact number that applies to your account.
Do the 14 days have to be continuous?
Yes. You need at least 12 testers opted in for 14 days in a row. If you drop below 12 opted-in testers, the count can reset, so it is safer to start with a few more than 12.
Does internal testing count towards the 14 days?
No. Only the closed testing track counts. Internal testing is useful for quick checks with your own team, but it does not satisfy the requirement.
Do organization accounts need to do this?
Generally no. The requirement applies to personal developer accounts created after 13 November 2023. Organization accounts are not normally subject to it, but check your Play Console dashboard to be sure.
Can I use friends and family as testers?
Yes, as long as they opt in with a Google account and stay opted in for the full 14 days. The difficulty is finding 12 or more people who will reliably stay with it for two weeks.
Can I update my app during the 14 days?
Yes. Pushing new builds to the closed track does not reset the clock, and fixing issues that testers report is exactly what Google wants to see.
Need 12+ testers for your closed test?
Closed Test Hub gives you real testers on physical Android phones, a tester-by-day dashboard for all 14 days, and a feedback report you can use in your production application. Plans start at ₹699.
More guides
Closed Test Hub is an independent service and is not affiliated with Google or Google Play. Google can change its policies at any time, so always confirm the current requirements in your Play Console.