The core requirement: if you have a personal developer account created after November 13, 2023, you must run a closed test with at least 12 testers for 14 continuous days before you can apply for production access. Meeting the numbers is not enough on its own. Since 2026, Google also checks that those testers genuinely used your app.
This page is the full reference: who the rule applies to, what counts, what does not, and everything else Google requires before your app can go live.
Requirements at a glance
| Requirement | What Google asks for |
|---|---|
| Testers | At least 12, opted in through the closed testing track |
| Duration | 14 continuous days of testing |
| Engagement | Testers must actually use the app, not just install it |
| Who it applies to | Personal developer accounts created after 13 November 2023 |
| App format | Signed Android App Bundle (.aab), not APK |
| Target API level | Android 16 (API 36) from 31 August 2026 |
| Application | 10 questions, 2 multiple choice, roughly 300 characters each |
| Decision time | About 48 hours, then up to 7 days for production review |
Who the 12 testers requirement applies to
This is the question developers get wrong most often, because the rule is not universal.
| Account type | Closed testing required? |
|---|---|
| Personal account created after 13 Nov 2023 | Yes, 12 testers for 14 days |
| Personal account created before 13 Nov 2023 | No |
| Organization account | No |
If you see a requirement for 20 testers rather than 12, you are looking at outdated guidance or a legacy screen. The number was reduced from 20 to 12 on 11 December 2024.
The 12 testers requirement in detail
Twelve is a floor, not a target. Three things decide whether your testers actually count:
- They must opt in. Adding an email address to your tester list does nothing by itself. Each tester has to open the opt-in link, click Become a tester, and install from the Play Store while signed into that same Google account.
- They must stay opted in. Play Console shows a live count of opted-in testers. If people uninstall or leave the programme, that number falls.
- They must use the app. This is the part that catches most developers, and it is covered in full below.
In practice, recruit 14 to 16 rather than exactly 12, so one or two inactive people do not drop you below the line. Our guide to getting 12 testers covers the recruitment channels that work.
The 14 days requirement in detail
The 14 days must be continuous. The clock starts once your release is live on the closed testing track with at least 12 testers opted in.
Two clarifications that come up constantly:
- 14 days is a minimum, not a target. Nothing stops you testing for 20 or 30 days, and a longer test with stronger engagement is more likely to be approved than a bare-minimum one.
- You can ship new builds during the test. Uploading fixes mid-test does not restart anything. It is evidence that your testing is working.
What counts as an active tester in 2026
This is the single biggest change in recent years, and the reason many applications that look compliant get denied.
Google now evaluates whether testers genuinely engaged with your app. Applications are rejected for insufficient testing engagement when testers installed the app but barely used it.
What that means in practice:
- An install with no sessions behind it contributes almost nothing.
- One short session on day one, then nothing, is the pattern most associated with failed tests.
- Regular sessions spread across the full 14 days are what a strong record looks like.
Google has not published an exact session threshold. The safe target is testers opening the app on most days of the test and using real features rather than just the home screen.
What resets the 14-day clock, and what does not
| Event | Does it reset the 14 days? |
|---|---|
| A tester uninstalls or opts out | No |
| Your count briefly drops below 12 | No |
| You upload a new build mid-test | No |
| You add more testers mid-test | No |
| You pause or halt the closed testing track | Yes, testing must be continuous |
Dropping below 12 does not restart the timer, but it does weaken the engagement record Google reviews at the end. The consequence appears at production review, not on the countdown.
Technical requirements
- Android App Bundle (.aab). New apps cannot be published as APKs.
- Play App Signing. Google manages your app signing key and your keystore becomes the upload key. Back up your keystore regardless.
- Target API level 36. From 31 August 2026, new apps and updates must target Android 16. See our guide to the target API level deadline.
- A clean pre-launch report. Play Console runs your app on real devices. Unresolved crashes and ANRs can block production access on their own.
Store listing requirements
These do not block the closed test, but they will block your release afterwards, so complete them early:
- App title, short description and full description
- App icon, feature graphic and at least two screenshots
- Content rating questionnaire, completed
- Data safety form, completed accurately
- A working privacy policy URL
- Target audience and app category
Production access requirements
After 14 days, an Apply for production option appears. Google asks 10 questions about your app and your testing, 2 of them multiple choice, with roughly a 300 character limit per answer.
The questions cover how you recruited testers, how easy recruitment was, what feedback you received, what you changed as a result, and how ready your app is for production. Thin answers are a common reason for denial even after a clean testing period. Our guide to the production access form answers covers all 10 with examples.
Expect a decision in about 48 hours, and allow up to 7 days for the production review itself.
How the rules changed
| Date | Change |
|---|---|
| 13 November 2023 | Closed testing requirement introduced for new personal developer accounts |
| 11 December 2024 | Requirement reduced from 20 testers to 12 |
| 2026 | Engagement checks added. Rejections for insufficient testing engagement begin |
| 31 August 2026 | New apps and updates must target Android 16 (API 36) |
Frequently asked questions
Do I need 12 testers for every app?
The requirement applies per app for personal developer accounts created after 13 November 2023, until that account has production access. Organization accounts and older personal accounts are not subject to it.
Can the same 12 testers test multiple apps?
Yes. Nothing prevents the same people from testing more than one of your apps, as long as they genuinely use each one.
Do testers need to be in specific countries?
No. There is no country requirement. Spreading testers across regions and devices does produce a broader testing record, which helps.
Can I use emulators or my own devices as testers?
No. Testers must be separate Google accounts, and the engagement checks are designed to identify artificial testing.
Do friends and family count as testers?
Yes, provided they genuinely use the app across the full period. Google does not object to who your testers are, only to testers who install once and never return.
What if I drop below 12 testers?
The 14-day timer does not reset. Add replacements as soon as you can, because the engagement record still matters at review.
Does internal testing count toward the 14 days?
No. The requirement is specifically for the closed testing track.
How long does the whole process take?
Plan for roughly three weeks: a day or two of setup, 14 days of testing, about 48 hours for the production access decision, and up to 7 days for production review.
What happens if my application is denied?
You can reapply. Extend the test, improve engagement, fix whatever the rejection referenced, and give specific answers on the resubmission form. Our guide to why apps fail production access covers the common causes.
Meeting the requirement without the hassle
Every requirement on this page comes down to one thing: real people using your app for 14 continuous days. If you do not have 12 engaged testers available, Testers Community assigns verified testers within 6 hours, replaces anyone who goes inactive, and sends you a feedback report plus pre-filled answers for the production access form. More than 10,000 apps have reached production this way, from a community of over 50,000 developers. Submit your app to start.
