Google Play 20 to 12 Testers: What the Policy Change Means in 2026
Google reduced the closed testing requirement from 20 to 12 testers in December 2024. What the change means for developers in 2026 and what stayed the same.
2 min read
In this article
On December 11, 2024, Google updated its closed testing policy for personal Google Play developer accounts, reducing the minimum tester requirement from 20 testers to 12 testers for 14 consecutive days. In 2026, this reduced threshold remains in effect. Here is exactly what changed and what the implications are.
The Original Policy: November 2023
When Google introduced the mandatory closed testing requirement in November 2023, the threshold was 20 testers for 14 days. This applied to all personal Google Play developer accounts created on or after November 13, 2023.
The 20-tester requirement was immediately criticized by independent developers as an unnecessarily high bar. Finding 20 reliable testers, managing their participation for 14 consecutive days, and handling dropouts was a significant operational burden for solo developers building their first app.
The December 2024 Change: From 20 to 12
Google reduced the minimum from 20 to 12 testers on December 11, 2024. The 14-day duration remained unchanged. This reduction was widely welcomed by the developer community.
Google has not published detailed reasoning for the change, but developer feedback on Reddit and the Google Play Help community indicates that widespread complaints about the 20-tester barrier for legitimate independent developers drove the revision. The 12-tester threshold maintains the spam-deterrent effect - it is still genuinely difficult to fake 12 real people for 14 days - while being meaningfully more achievable for solo developers.
What Stayed the Same in 2026
The 14-consecutive-day requirement is unchanged. All 12 testers must remain opted in for all 14 days without the count dropping below 12.
The account eligibility remains the same. Personal accounts created after November 13, 2023 must complete closed testing. Organization accounts and older personal accounts remain exempt.
The engagement requirement is unchanged. Google evaluates genuine participation, not just install counts.
What Is New in 2026
Google introduced developer identity verification in 2026, rolling out to Brazil, Indonesia, Singapore, and Thailand from September 30, 2026. This is separate from the testing requirement but affects production access in those regions.
Apps must now target Android 16 (API level 36) or higher as of August 31, 2026. Build against the current API to avoid triggering a separate rejection reason.
Google's production access questionnaire has become more detailed and is reviewed by human moderators with specific expectations for the depth of testing evidence provided.
Is 12 Enough or Should You Get More?
For the technical requirement, 12 testers is sufficient. Many testing services, including TestSlot, recommend a small buffer above 12 to protect against dropout-related issues. If one tester drops on day 11 and you only had exactly 12, you may need to extend your timeline. If you had 14, you can absorb that dropout without impact.
TestSlot handles this automatically. The platform maintains the required tester count and replaces dropouts from its active pool. You never need to worry about buffer management.
Start your 12-tester closed test at testslot.io.
Need 12 testers for your closed test?
TestSlot gives you real, verified testers who keep your app installed for the full 14 days - with daily proof, a live dashboard, and a money-back guarantee.

