Google Play closed testing requirements in 2026
The current rules for personal developer accounts: who the 12-tester requirement applies to, what counts, and what has changed.
Who this applies to
Personal developer accounts created after 13 November 2023. Organisation accounts - those registered with a D-U-N-S number - are not subject to the closed testing requirement and can publish to production directly.
If you are choosing an account type now and expect to ship regularly, the organisation route removes this requirement entirely. It also takes longer to set up and requires verifiable business details.
The requirement in one line
At least 12 testers opted in to a closed test, continuously, for 14 consecutive days, before you may apply for production access.
- 12 testers is a floor, not a target
- Opted in means they accepted the invitation
- 14 days must be consecutive, not cumulative
- Closed track only - internal testing does not count
- Each new app clears the requirement separately
What the count is sensitive to
If a tester leaves the programme and your opted-in total drops below twelve, you risk breaking the consecutive streak. Uploading a new build to the same closed track does not reset the clock, but removing the track or letting the test lapse will.
Verification, separately
Developer identity verification is a distinct obligation from the testing requirement, with its own deadlines. Clearing one does not clear the other, and both must be satisfied before an app reaches production.