Google Play 12 testers for 14 days: how the rule works

If your personal Google Play developer account was created after November 13, 2023, you have to run a closed test with at least 12 testers who have been opted in continuously for the last 14 days before you can apply for production. Testers who leave early don't count. Then you apply from the Dashboard with a short form, and Google says review usually takes seven days or less.

As of October 23, 2026, that's what Google's Play Console Help page App testing requirements for new personal developer accounts says. The setup steps come from its companion page on setting up an open, closed, or internal test.

Does the 12 testers rule apply to me?

The requirement page is written for developers with personal Play Console accounts created after November 13, 2023. It doesn't cover organization accounts, so if you registered as an organization, this page isn't your rulebook. If your personal account is older than that date, the requirement page doesn't apply to you either.

What counts toward 12 testers and 14 days?

The test that counts is a closed test. Google's wording is that at least 12 testers must be opted in when you apply for production access, "and they must have been opted in continuously for the preceding 14 days."

Situation	Counts?	Where it comes from
Tester opted in to your closed test for the whole 14 days before you apply	Yes	Requirement page
Tester who opted in, stayed less than 14 days, then opted out	No	Requirement page FAQ
Tester who opted out and back in	Only if their 14 days are consecutive	Requirement page FAQ
Fewer than 12 opted in on the day you apply	No, Google may ask you to keep testing	Requirement page
Open testing	Not available yet. It opens after you get production access.	Requirement page

Numbers aren't the only thing Google looks at. The page says continued testing can be required for having fewer than 12 opted-in testers or for insufficient tester engagement during the testing period. So 12 people who opted in and never opened the app is a weak position to apply from.

The internal testing catch

The requirement page calls internal testing optional but recommended as a starting point. The setup page adds a detail that matters here: users who opt into internal testing aren't eligible for open and closed testing, even if they're included as testers on those tracks.

So if you put your 12 friends on an internal test first and then add the same people to your closed test, the setup page says they can't join it. I'd keep the people you're counting on for the 14 days on the closed test only, and use internal testing for yourself, if at all.

How do I set up the closed test?

1. In Play Console, go to Test and release, then Testing, then Closed testing.
2. Click Manage track and open the Testers tab.
3. Click Create email list and add addresses separated by commas, or upload a CSV file. Uploading a CSV overwrites the addresses you added before, and Play Console doesn't accept CSV files saved as UTF-8 with BOM.
4. Or choose Google Groups and enter the group's address. Testers then have to join the group before they can opt in.
5. Publish the test release, then share the link with testers. Each tester opts in with it.

Some details from the same page that trip people up:

• Testers need a Google Account or a Google Workspace account.
• The opt-in link only shows when the app status is Published. Apps in Draft or Pending publication don't show one.
• After the first publish, the test link can take several hours to become available.
• If you haven't released to open testing or production yet, testers can't find your app by searching Google Play. Send them the link.

What does the production access form ask?

When you're ready, open the Dashboard in Play Console and click Apply for production. The form has three parts:

Part	What it asks
About your closed test	How easy it was to recruit testers, how engaged they were (did they use all the features, did usage match what you expect in production), and a summary of their feedback and how you collected it.
About your app or game	Your target audience, how the app provides value to users (for games, what makes the game unique), and an estimated install range for the first year.
About your production readiness	What you changed based on the closed test, and how you decided the app was ready for production.

Google says review usually takes seven days or less but can occasionally take longer. If your app needs login, the page also asks you to give working test credentials in Play Console.

What I'd do

Before day one, write down what you want testers to try and how they'll send feedback, because the form asks for both. Put your testers on the closed test only, check on day 3 or 4 that at least 12 are still opted in, and keep a short list of what you changed because of their feedback. That list is most of the answer to the last part of the form.