Google Play Closed Testing Requirements 2026
A one-page checklist of the closed testing requirements, from the 12 testers to the production access questionnaire.
Read the guide →Google Play 12 Testers Rule vs the Old 20 Testers
Quick answer The current rule is 12 testers, not 20. Google reduced it on December 11, 2024. Testers must stay opted in for 14 days, so recruit 15 to 20 to be safe.
Search for Google Play testing requirements and you will find two numbers: 20 and 12. Both were correct at some point. Twenty testers was the original rule when Google introduced closed testing for new personal accounts, and in December 2024 Google reduced it to 12. Outdated guides cause real mistakes, from developers paying for 20 testers they do not need to developers planning for exactly 12 and failing when one leaves. This guide sets out the timeline, what changed, what did not, and how many testers to recruit.
How many testers does Google Play require now?
You need 12 testers, not 20. They must stay opted in for 14 continuous days. Google states this on its testing requirements help page. If a guide, video or forum post says 20, it was written before December 2024.
The history
- November 9, 2023Google announced on the Android Developers Blog that newly created personal Play Console accounts would need to test with at least 20 people for a minimum of two weeks before applying for production access. The post gave improved app quality as the reason.
- November 13, 2023The cut-off date. Personal accounts created after it are the accounts affected.
- December 11, 2024Google updated its announcement: the number of testers for personal accounts was reduced from 20 to 12, because developers with small audiences found 20 hard to recruit.
- December 2024 onwardIndependent publications such as Android Authority reported that the help page now says a minimum of 12 testers.
You can read Google's own wording in the original blog post and its update, and the news report on the support page change.
Then and now
| Original rule (Nov 2023) | Current rule | |
|---|---|---|
| Testers needed | 20 | 12 |
| Time | At least two weeks | 14 days continuous opt-in |
| Accounts affected | New personal accounts | Personal accounts created after November 13, 2023 |
| Closed test required before production | Yes | Yes |
| Production access questionnaire | Yes | Yes (three parts) |
| Testers who leave early count? | No | No |
| Rejoining testers | Not clearly stated in the announcement | The 14 days must be consecutive |
Who it applies to
The requirement applies to personal developer accounts created after November 13, 2023. If you registered earlier or you use an organization account, check what your Dashboard shows, because the options for your account may differ. For the full list of steps, see our closed testing requirements checklist.
Why recruit more than 12 testers?
Google counts testers who are currently opted in and who have been opted in for 14 days in a row. If a tester leaves, they do not count. If a replacement joins later, they need their own 14 days. That is why recruiting exactly 12 is risky. Use this planning table:
| If you expect this many to drop out | Recruit at least | Why |
|---|---|---|
| 10% (1 or 2 people) | 14 | 12 ÷ 0.9 is about 13.3, rounded up |
| 20% (2 or 3 people) | 15 | 12 ÷ 0.8 = 15 |
| 30% (3 or 4 people) | 18 | 12 ÷ 0.7 is about 17.1, rounded up |
| 40% (4 to 6 people) | 20 | 12 ÷ 0.6 = 20 |
Friends and family often fall in the 20 to 40 percent range, because people forget. Professional testers and well-briefed communities are more reliable. Read how to get 12 testers for the options, and what to do if testers leave for a recovery plan.
How to confirm the current rule
- Open Google's testing requirements help page and read the first paragraph.
- Check the date on any guide you read. Anything before December 2024 may say 20.
- Look at the production access section on your Play Console Dashboard.
- Remember that rules can change again. Check before you plan, and again before you apply.
Your tester plan
- Recruit 15 to 20That gives you a safety margin above the 12 minimum.
- Brief themTell them to stay opted in for 14 days and open the app regularly.
- Share the linkSee how to share the closed testing link.
- Track the countCheck the opted-in number weekly. If it is below 12, add replacements immediately.
- Apply when readyFollow how to apply for production access.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Android Developers Blog: Ensuring high-quality apps on Google Play
- Google Play Console Help: App testing requirements for new personal developer accounts
- Android Authority: report on the change from 20 to 12 testers
Quick reference card
| Question | Answer |
|---|---|
| How many testers? | 12 minimum |
| How long? | 14 continuous days |
| Who? | Personal accounts created after Nov 13, 2023 |
| How many to recruit? | 15 to 20 |
| What if one leaves? | Replace at once. See the recovery plan |
Frequently asked questions
Does Google Play still require 20 testers?
No. Google's Android Developers blog says that on December 11, 2024 the requirement for personal developer accounts was reduced from 20 testers to 12. The 14-day (two-week) minimum was not mentioned as changing.
Who has to run the closed test?
Developers with personal Play Console accounts created after November 13, 2023.
Is 12 testers enough?
Twelve is the minimum, and they must stay opted in continuously for 14 days. Because testers who leave early do not count, most developers recruit 15 to 20 to be safe.
Why do some guides still say 20?
Because the original requirement, announced in November 2023, was 20 testers for at least two weeks. Many older articles, videos and forum posts were never updated.
Did the 14 days change too?
The Google post announcing the change to 12 testers did not mention any change to the two-week minimum, and Google's current help page still says 14 days.
Where should I check the current rule?
Google's Play Console Help page on testing requirements. Rules can change, so check it before you plan your launch.
