Google Play closed testing requirements: the complete 2026 guide
Updated November 2026
If you opened a personal Google Play developer account after 13 November 2023, you can't publish straight to production. Google first wants a closed test with at least 12 testers who stay opted in for at least 14 days in a row. Then you fill in a short production access form and wait for Google's review. This guide explains every part of the rule as Google states it in the Play Console Help Center, what actually trips developers up, and a realistic timeline from first upload to public release.
Who has to do closed testing
Google's Help Center says the requirement applies to personal developer accounts created after 13 November 2023. Until those apps pass it, they are not eligible for distribution on Google Play.
If your account was created before that date, or it is an organization account (a business verified with a D-U-N-S number), the closed testing requirement does not apply to you. Each app on an affected personal account goes through the process before it gets production access.
- Personal account, created after 13 Nov 2023: closed test required.
- Personal account, created before 13 Nov 2023: not required.
- Organization account: not required, but you need a D-U-N-S number and a verified organization website. See the guide on organization vs personal accounts.
The rule in one sentence
Run a closed test with at least 12 testers who have been opted in continuously for at least 14 days, then apply for production access from the Play Console Dashboard.
Google's wording matters. The 14 days must be consecutive. Testers who opt in, test for fewer than 14 days and then opt out do not count. And at least 12 testers must still be opted in on the day you apply.
The number was 20 testers until December 2024, when Google lowered it to 12. The 14 days did not change.
What counts as a tester
- A real Google Account that opted in. Being on your email list or in your Google Group is not enough. Each person has to open the opt-in link and tap to become a tester.
- On the closed track. People who opted into your internal test are not eligible for closed tests until they leave the internal test. Internal testing does not count toward the requirement.
- Opted in the whole time. If someone leaves and rejoins, their consecutive count starts again.
- Using the app. Google does not publish a minimum number of opens, but the production form asks how testers engaged and whether usage matched what you expect in production. Testers who install once and disappear are the main reason applications fail.
A realistic timeline
- Day 0: create the closed track, add testers (an email list or a Google Group), upload an app bundle and send the release for review.
- Hours to a few days later: the release is published and the opt-in link works. Google notes the first test link can take several hours to become available.
- Days 1 to 14: at least 12 testers stay opted in and use the app. Ship at least one update based on their feedback.
- Day 15 or later: click Apply for production on the Dashboard and answer the questions.
- About a week later: Google says the review usually takes seven days or less, but can occasionally take longer. You get an email when it's done.
- After approval: the Production page unlocks. Your first production release still goes through normal app review.
Plan for roughly three to four weeks from your first closed-test upload to a public listing, if nothing goes wrong.
The production access form
Google's form has three parts. Part one is about your closed test: how easy it was to recruit testers, how they engaged, and a summary of their feedback and how you collected it. Part two is about your app: target audience, what value it gives users, and how many installs you expect in the first year. Part three is about production readiness: what you changed after the test and how you decided the app was ready.
Write the answers before you open the form. Google warns that your answers are lost if you leave the page before clicking Next or Apply. Our guide to the production access questions and the free answer tool at https://testerexchange.com/tools/production-answers/ help you draft them from real numbers.
Why apps don't pass
Google's Help Center lists two reasons you may need to keep running your closed test: fewer than 12 opted-in testers, or not enough engagement from testers. In practice developers hit these problems:
- Asking exactly 12 people. One dropout on day 10 and you are at 11.
- Testers who install and never open the app again.
- Many accounts on one phone, or accounts that are not real people.
- No updates and no feedback during the 14 days, so there is nothing to describe in the form.
- Short, generic answers in the questionnaire.
If you already got a "more testing required" reply, read the guide on insufficient testing engagement and the guide on what to do when production access is rejected.
Where to get 12 testers
Google does not say where testers must come from. Friends and family work if you know enough Android users who will open your app daily for two weeks. Test-for-test communities are free but need your time. Paid services are faster.
Tester Exchange does both. Pay once ($12.99 for 12 testers, $14.99 for 15, $22.99 for 25), or get testers free by testing other developers' apps at https://testerexchange.com/earn in your Android phone's browser. Every tester is a real person on their own phone, and you see daily use for each one. We recommend 15 testers so a dropout or two can't push you under 12.
Frequently asked questions
Is it 12 or 20 testers?
12. Google lowered it from 20 to 12 in December 2024. The 14 continuous days stayed the same.
Does the requirement apply to my old account?
Only personal accounts created after 13 November 2023 must run the closed test. Older personal accounts and organization accounts are not covered by it.
Do I need to repeat closed testing for every app?
Production access is granted per app on affected personal accounts, so plan a closed test for each new app.
Does internal testing count?
No. It has to be a closed test. Google also says people opted into your internal test can't join your closed test until they leave the internal one.
Do testers have to use the app every day?
Google doesn't publish a minimum. It asks about engagement in the production form, so regular real use by most testers is the safest pattern.
How long does Google take to review production access?
Google says usually seven days or less, but it can occasionally take longer.