If your personal Google Play Console account was created after 13 November 2023, you must run a closed test with at least 12 testers who stay opted in continuously for at least 14 days before you can apply for production access. Google says review of that application "usually takes seven days or less". The rule is written for personal accounts. The page does not name organisation accounts. Source: Google's App testing requirements for new personal developer accounts, opened 9 October 2026.
The rule in Google's words
"Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days." Then you "can apply for production access on the Dashboard". Until then, Production and Pre-registration stay disabled in Play Console.
- Personal account created after 13 November 2023: the rule applies.
- Personal account created on or before that date: the page covers accounts created after it.
- Organisation account: the page is titled for "new personal developer accounts" and does not mention organisations. Confirm in your own Play Console.
What counts as opted in
A tester counts only after opening your opt-in link and accepting. Google says: "Each tester needs to opt in using the link." With a Google Group, "users must join the group before opting into your test".
"Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement." If a tester opts out and returns, "the 14 days must be consecutive". Invite more than 12.
Steps
- Finish app setup, including the declarations. See publishing an app on the Play Store.
- Optionally run an internal test first (up to 100 testers). Do not use your 12 here: a user who opts into an internal test "is no longer eligible to receive an open or closed test" until they opt out of it.
- Create the closed track. In Play Console go to Test and release, then Testing, then Closed testing, and create a release with your Android App Bundle.
- Add testers on the Testers tab: an email list (CSV upload allowed; up to 2,000 users per list) or Google Group addresses.
- Share the opt-in link. Add a feedback email or URL so it shows on the opt-in page. After you publish the test, the link can take several hours to start working. Tell testers to stay opted in for 14 continuous days.
- Collect feedback and fix bugs. Testers cannot leave public reviews on test versions, so you need your own channel. Play Console also shows private feedback.
- Apply for production from the Dashboard once the criteria are met.
Keep your own list of who confirmed they joined, and check your Dashboard before you apply.
The application questions
- About your closed test: how easy it was to recruit testers; whether testers used all available features; whether usage matched expected real users; a summary of feedback and how it was collected.
- About your app or game: target audience, value to users, and an estimated install range for the first year. Google says these answers are not shown publicly and do not affect visibility.
- About production readiness: what you changed after the test, and how you decided the app was ready.
Review time and rejections
Google says: "Review usually takes seven days or less, but can occasionally take longer." You get an email when it finishes. If your app needs more testing, you may have to keep the closed test running. Google's reasons: "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period."
Review "is not a troubleshooting step". Check policy compliance, target age group and rating, crashes and missing screens, and supply a working login for reviewers if your app has one.
Finding testers
Google suggests friends, family, colleagues and classmates, communities where your target users already are, and social media followers. It also asks for a mix of devices and people who resemble your future users. For a business, that means your first customers, staff, suppliers or members.
Day-by-day plan
Our planning advice, built around Google's 12 testers and 14 days.
| Day | What to do |
|---|---|
| Before day 0 | Finish setup, privacy policy, Data safety form, and an internal test with your own team |
| Day 0 | Publish the closed test, send the link to about 18 to 20 people |
| Day 1 to 3 | Chase everyone to open the link and accept; keep a list |
| Day 3 | Replace anyone who has not joined; confirm 12 or more |
| Day 4 to 13 | Ask testers to use real features; log feedback; ship fixes |
| Day 14 | Check that the same 12 or more are still opted in |
| Day 14 or later | Apply for production access; answer from your logs |
| After applying | Expect up to seven days or longer; keep testing meanwhile |
A late joiner starts their own 14-day clock, which is why we invite more than the minimum. For how long a whole build runs, see how long does it take to build an app.
Personal or organisation account
Google's account type page says personal accounts suit "student, hobbyist, or amateur" use, and organisation accounts suit anyone "engaged in commercial, industrial, professional, or governmental activities". Finance, health, VPN and government apps must register as organisations.
An organisation account needs a D-U-N-S number, which Google says is free and "can take up to 30 days" to obtain. The organisation details must match your Dun & Bradstreet profile. Choose before you pay, and keep the account in your company's name. Weighing builds? See React Native vs Flutter and app development cost in India.
Want an app built, tested and launched under your own accounts? Tell us about your project.
Frequently asked questions
Who needs 12 testers on Google Play?
Personal Play Console accounts created after 13 November 2023. They need a closed test with at least 12 testers opted in continuously for at least 14 days before applying for production access. Organisation accounts are not named on the page.
Does an organisation account need 12 testers?
Google's testing page is titled for new personal developer accounts and does not name organisation accounts. Organisation accounts have their own requirement: a D-U-N-S number and details matching your Dun & Bradstreet profile. Confirm in your own Play Console.
What happens if a tester opts out during the 14 days?
Testers who opt in, test for fewer than 14 days and then opt out do not count. If someone rejoins, the 14 days must be consecutive. Invite more than 12 people.
How do I apply for production access?
Once the closed test meets the criteria, open the Dashboard in Play Console and choose Apply for production. You answer questions about your closed test, your app and your production readiness.
How long does production access review take?
Google says: "Review usually takes seven days or less, but can occasionally take longer." You get an email when it finishes. If Google wants more testing, you may need to keep your closed test running and apply again.