If you have a personal Google Play developer account created after November 13, 2023, the closed testing requirement is at least 12 testers who stay opted in continuously for 14 days before you can apply for production access. You run a closed test track, add testers by email address or a Google Group, share the opt-in link so they join, and keep at least 12 of them opted in for a full 14 consecutive days. Google previously set this at 20 testers, so if you have seen that number, the current requirement is lower, but the 14 consecutive days still apply.
Short answer
Personal developer accounts must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. Per Google's closed testing requirements, the 14 days must be consecutive, so testers who opt in, test briefly, and opt out do not count. You add testers by email or Google Group, share the opt-in link for them to join, and confirm at least 12 stay opted in for the full period. Google lowered this from 20 to 12 testers, so the older number you may have read no longer applies, but the 14-day continuous rule is unchanged.
The 12 testers, 14 days requirement
The core requirement is simple to state: at least 12 testers, opted in for 14 consecutive days, on a closed test. This applies to personal developer accounts created after November 13, 2023, and it is a gate you must clear before Google lets you apply for production access. The requirement exists so that new accounts demonstrate a real test with real users before shipping to everyone.
It is worth being precise about the number because it changed. Google originally required 20 testers and later reduced it to 12, so both numbers circulate online and the current, correct figure is 12. The 14-day duration did not change. When you read guidance that says 20, treat it as outdated on the count while still accurate on the 14-day continuous period, and plan your test around 12 testers held for two full weeks.
How to find testers
Finding 12 testers is the practical hurdle, and you have a few reliable options. You can invite people you know directly by their Google account email, recruit from communities related to your app, or use tester-exchange groups where developers opt into each other's closed tests. Whoever you recruit, each tester must use a real Google account, since that is the account that opts in and that Google counts.
Add testers in Play Console by creating an email list or by pointing the track at a Google Group you control. A Google Group scales better when you have more than a handful of testers, because you manage membership in one place rather than editing a raw email list. Aim for a margin above 12, since some people opt out or never join, and you need at least 12 opted in for the full 14 days, not just at the start.
Opt-in links and how testers join
Testers join your closed test through an opt-in link, not by searching the store. After you set up the closed track and add someone as a tester, Play Console gives you a web opt-in URL to share with them. The tester opens that link while signed into the Google account you added, accepts the invitation to become a tester, and can then install the test build. Without opting in through that link, being on the list alone does not make them an active tester.
Share the exact opt-in URL and tell testers which account to use, because the link only works for accounts on the list and only when opened while signed into that account. If a tester reports the link failing, the usual causes are that they are not on the list yet, they are signed into a different account, or the change has not synced, which typically takes a few hours. Confirming each tester actually opted in is how you verify your count toward the 12.
The 14 days must be consecutive
The 14 days are continuous, which is the detail people most often miss. Per Google, testers who opt in, test for less than 14 days, and then opt out do not count, and even if they opt back in later, the 14 days have to be consecutive to count toward the criteria. In other words, the clock is about a tester staying opted in without a gap, not about accumulating 14 days of activity over a longer stretch.
Plan around this by getting your testers opted in at roughly the same time and keeping them in for the full two weeks. If several testers drop below the line partway through, your continuous count resets for them, and you may fall under 12 without realizing it. Check the tester count during the period rather than only at the end, so you can recruit replacements early enough for them to complete their own 14 consecutive days.
After you meet the requirement
Once you have held at least 12 testers for 14 consecutive days, you become eligible to apply for production access, which is a separate step you initiate in Play Console. Meeting the testing criteria does not automatically publish your app to production; it grants the ability to request production access, which Google then reviews. Plan for that review as an additional stage after the 14 days, not as something that happens the moment the period ends.
Use the closed test period for its actual purpose as well: gather feedback, fix crashes, and confirm the build behaves for real users on real devices. Treating the requirement as only a box to check misses the value of the test, and a build that testers found broken is not one you want to rush to production. Meet the count, keep the test genuine, then apply for production with a build you trust.
Requirements at a glance
The requirement sits within Google's testing tracks, and comparing them clarifies which one counts. The table below compares the tracks.
| Track | Testers | Counts toward production access |
|---|---|---|
| Internal testing | Up to 100, added by email | No |
| Closed testing | 12 or more, via email list or Google Group | Yes, 12 for 14 consecutive days |
| Open testing | Public, anyone can join | Not the track for this requirement |
| Production | Public release | The goal after eligibility |
Read the table to place your work: the closed testing row is the one that satisfies the requirement for a new personal account, and internal or open testing does not substitute for it.
Setup checklist
Working through setup in order gets you to eligibility. The checklist below covers the steps.
| Step | Action | Done? |
|---|---|---|
| Create closed track | Set up a closed testing release | [ ] |
| Add testers | 12 or more real Google accounts, via list or group | [ ] |
| Share opt-in link | Send the web opt-in URL and the account to use | [ ] |
| Confirm opt-ins | Verify at least 12 actually opted in | [ ] |
| Hold 14 days | Keep 12 opted in continuously, no gaps | [ ] |
| Apply for production | Request production access after the period | [ ] |
The two that decide success are getting more than 12 testers actually opted in and keeping at least 12 of them in for the full 14 consecutive days. Monitor the count during the period, not just at the end.
Test securely, then promote
Closed testing is where you validate a build before production, which also makes it the moment to check that build's security. Meeting the tester requirement gets you eligible to promote the build; it does not tell you whether that build carries risky third-party code, leaked keys, or over-broad permissions.
A scanner like PTKD.com analyzes the same build you are testing and reports findings by severity, mapped to OWASP MASVS, so security issues surface during closed testing rather than after you reach production. To be clear about the boundary: PTKD does not manage your testers, opt-in links, or the 14-day count. It checks the build so the one you promote is clean.
What to take away
- Personal accounts created after November 13, 2023 need at least 12 testers opted in for 14 consecutive days before applying for production access.
- Google lowered the count from 20 to 12, so treat older 20-tester guidance as outdated on the number while the 14-day continuous rule still holds.
- Add testers by email or a Google Group, share the opt-in link, and tell each tester which account to use, since the link only works for listed accounts.
- The 14 days must be continuous, so recruit a margin above 12 and check the count during the period, not only at the end.
- Meeting the requirement only makes you eligible to apply for production; use the closed test genuinely and scan the build with PTKD.com before you promote it.
