Google Play closed testing: the 12 testers, 14 days rule explained
Last reviewed 21 November 2026
You’ve built the app, opened Play Console, and the Production button is greyed out. If your developer account is a personal one, Google wants proof that real people have tested the app first. Here’s exactly what it asks for, and how not to lose two weeks by doing it slightly wrong.
Personal Play Console accounts created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in for at least 14 days in a row, then apply for production access. Google checks the count when you apply, and testers who leave early don’t count. Organisation accounts, which need a free D-U-N-S number, don’t have this step.
The rule
According to Google’s help page, personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least the last 14 days. Until then, the Production and Pre-registration options stay switched off. Google checks the numbers at the moment you apply.
Some older guides say 20 testers. That was the original rule; Google lowered it to 12 in December 2024.
How the 14 days are counted
- Testers who leave before 14 days don’t count.
- A tester who opts out and back in needs another 14 days in a row.
- Tell your testers to stay opted in, as Google itself suggests. Recruit a few more than 12 in case someone drops out.
Who doesn’t need it
Google applies the testing requirement to personal accounts. An organisation account is for businesses, and is required for some categories such as finance, health and government apps. Most organisations need a D-U-N-S number, which is free but can take up to 30 days to get (known government agencies can verify without one). Google warns about third parties that charge for one.
Setting up the closed test
- Finish the app setup in Play Console. Closed testing needs it; internal testing doesn’t.
- Add testers with an email list (up to 2,000 per list) or a Google Group. Each tester needs a Google account.
- Publish the test release. The opt-in link only appears once the release shows as Published, and it can take a few hours to work.
- Each tester opens the link and opts in. If you used a Google Group, they must join the group first. Closed test apps can’t be found by searching, so share the link.
Testers who can’t see the app have usually not opted in, not joined the group, or are still opted in to your internal test, which blocks the closed one until they leave it. See Google’s testing guide.
Finding 12 real testers
Google suggests your own network and communities. Friends, family, early customers and people on your waiting list are ideal: they’ll give useful feedback, and the production access form asks about it. Paid tester services exist. Google’s policies don’t mention them directly, but they do ban fake installs and engagement, and Google judges whether testers really used the app.
The production access form
When the 14 days are up, you apply from the Dashboard. Google asks three sets of questions:
- About your test: how easy recruiting was, how testers used the app compared with how you expect real users to, and a summary of their feedback and how you collected it.
- About your app: who it’s for, why they’ll use it, and how many installs you expect in the first year. Google says these answers aren’t public.
- About your readiness: what you changed after the test, and how you decided it was ready.
Write specific answers. Mention real feedback and the changes it led to. If the app has a login, give reviewers working sign-in details. Google says review usually takes seven days or less.
If production access is refused
Google names two usual reasons: fewer than 12 testers opted in for the full 14 days, or not enough tester engagement. It may ask you to keep the closed test running. Fix whichever applies, keep testers active, and apply again with better answers. Google gives no fixed waiting period.
Questions founders ask
Is it 12 or 20 testers?
12. Google started with 20 in November 2023 and lowered it to 12 in December 2024.
Do testers have to use the app every day?
Google doesn’t set a daily requirement, but it does refuse access for insufficient engagement, so ask testers to use the main features and send feedback.
Can I avoid the closed test?
Organisation accounts don’t have it, but they need a D-U-N-S number and are meant for registered businesses. If you have a company, it’s often the better account to use anyway.