Guide 1 of 7 · Updated October 2026
Google Play's 12-testers rule explained (2026)
Short answer: A personal Google Play developer account created on or after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 continuous days, then apply for production access, before it can publish an app to production. Organization accounts and older personal accounts are exempt. The number was 20 until Google lowered it to 12 in 2025; the card on your Play Console dashboard shows the count that applies to you.
If you created a personal Google Play developer account after November 13, 2023, you cannot publish an app to production until you have run a closed test with at least 12 testers opted in for 14 continuous days and Google has approved your application for production access. This guide explains who the rule covers, where the numbers come from, how the clock works, and what Google is really looking at.
The rule in one paragraph
Before a new personal developer account can release an app on the production track, the app has to go through closed testing with at least 12 testers who stay opted in for the last 14 days continuously. When that bar is met, a button called Apply for production access appears on the app's dashboard in Play Console. You fill in a short form about the test — how you found testers, how they used the app, what they said and what you changed — and Google reviews it. Only after approval can you create a production release. Everything about publishing that was true before (policy review, content rating, data safety form, store listing) still applies on top.
Who it applies to (and who is exempt)
- Applies: personal (individual) developer accounts created after November 13, 2023. The check is per app: each new app on such an account goes through its own closed test and its own application.
- Exempt: personal accounts created on or before November 13, 2023.
- Exempt: organization accounts. They go through a different verification (a D-U-N-S number and business details) instead. If you have a registered business, this is sometimes the faster route — but the verification itself can take weeks, and an organization account is a different legal relationship with Google, not a trick.
Google introduced the requirement together with stricter identity verification for new accounts. The stated goal is to keep low-effort and policy-breaking apps off the store by making every new developer prove that real people have used the app before it goes public.
From 20 testers to 12: the timeline
- November 13, 2023: Google announces the requirement for new personal accounts: a closed test with 20 testers opted in for at least 14 days, then an application for production access. Accounts created from that day on are covered.
- 2025: Google lowers the bar from 20 testers to 12. The 14 days did not change, and neither did the application step. Older articles, videos and tester-swap posts still say "20 testers"; the number in your Play Console dashboard is what counts.
- Today: 12 testers, 14 continuous days, then the application. Your dashboard shows a card for the requirement with the current tester count and whether the 14 days are complete.
What "14 days continuously" means
The wording is "at least 12 testers who have been opted in for the last 14 days continuously". Three practical consequences:
- The clock runs per tester, not per app. The requirement is satisfied on the first day on which 12 (or more) of your currently opted-in testers have each been opted in for 14 days without a break. If your twelfth tester joined on the 1st, the earliest you can expect the requirement to show as met is the 15th. Our 14-day calculator works this out and gives you a day-by-day plan.
- A tester who leaves costs you time. If someone opts out on day 9 and you replace them on day 10, the replacement's 14 days start on day 10. With exactly 12 testers you are one dropout away from waiting again, which is why most people recruit 14–15 and why services that sell testers promise they stay.
- Opt-in is what the counter measures. A tester is "opted in" when they accepted the invitation on the opt-in page (or joined the Google Group / are on the email list and accepted). Installing the app is a separate action. The counter does not drop because a tester did not open the app this week — but installs and usage are exactly what your application answers will be judged on, so you want both.
What Google checks when you apply
The application is not a code review and nobody watches your test live. Google looks at two things:
1. Your answers
The form asks how easy it was to recruit testers, how many of them engaged with the app and how, what feedback you received, and what you changed as a result. It also asks who the app is for and whether you consider it ready. Thin answers — "testers were friends, no feedback, nothing changed" — are the most common reason applications are turned down. The application guide walks through every question with sample answers.
2. Signals from the test itself
Play Console knows how many testers opted in, how many devices installed the app, how many sessions and crashes there were, and whether you shipped any updates to the track during the 14 days. A test with 12 opt-ins, one install and no updates reads as "nobody used it". A test with 12 opt-ins, 12 installs, a few crash reports that were fixed in a second build, and answers that mention those fixes reads as a real test. Google says it also reviews the app against the usual program policies at this point, so the normal pre-launch work (privacy policy, data safety, permissions you can justify) matters too.
What happens after you apply
- Review time: Google says up to 7 days; many developers hear back within a day or two.
- Approved: the production track opens for that app. You create a production release the normal way (it still goes through app review).
- Not approved: you receive a message along the lines of "your app isn't ready for production" with general reasons. There is no appeal form. You improve the app and the test, and you can apply again — Google asks for a further 14 days of closed testing before the next application. The rejection guide lists the six reasons we see and how to fix each one.
Five things people get wrong
- "Internal testing counts." It does not. Internal testing (up to 100 testers, no review) is for your own team. Only closed testing feeds the requirement. See internal vs closed vs open testing.
- "Open testing counts." Also no. The requirement is explicitly a closed test. Open testing is a public beta you can run after production access, or alongside it.
- "Twelve of my own Google accounts will do." Technically each account that opts in is a tester, but twelve accounts on one phone that never open the app give you nothing to write in the application, and Google's whole point is real usage. It is also the pattern most likely to be read as fake.
- "I can pay the $25 again on a new account and skip it." A new personal account is a new account created after November 2023 — it has the same requirement, and creating multiple accounts to dodge enforcement is itself against the Developer Program Policies.
- "Once the 14 days pass, I'm in." The 14 days only unlock the application. Approval depends on what you did during them and what you write.
Short answers
Does the 12-testers rule apply to my account?
It applies to personal developer accounts created after November 13, 2023. Personal accounts created before that date and organization accounts are not required to run the closed test before publishing to production.
How long does the closed test have to run?
At least 12 testers must be opted in continuously for the last 14 days before you can apply for production access. The 14 days are counted for the testers who are currently opted in, so a tester who leaves and is replaced restarts the count for that slot.
Do internal testing or open testing count toward the 12 testers?
No. The requirement is measured on closed testing. Internal testing is for your own team and open testing is a public beta; neither replaces the closed test for a new personal account.
What happens after I apply for production access?
Google reviews the application, which can take up to about 7 days. If it is approved, the production track opens for that app. If it is not, you keep testing, improve the app and the answers, and apply again after a further 14 days of closed testing.