Closed testing basics

20 testers or 12? How the Google Play rule changed

November 14, 2026 · 6 min read

Wooden letters arranged to spell 'UPDATE' on a textured burlap surface.
Photo by Ann Hannes on Pexels

Google Play now asks for 12 testers, not 20. The original announcement in November 2023 required "at least 20 people for a minimum of two weeks", and in December 2024 Google lowered the number to 12 for personal developer accounts. The 14 days did not change. If a tutorial, video or forum post still tells you to find 20 testers, it was most likely written before that update.

The short version

Original announcement (Nov 2023) Current rule (since Dec 2024)
Testers At least 20 At least 12
Duration A minimum of two weeks Opted in continuously for at least 14 days
Where it's written Android Developers Blog Play Console Help, plus an update note on the same blog post

Everything else about the requirement stayed the same: it's a closed test, the testers must stay opted in without a break, and Google makes the final decision when you apply for production access.

What Google announced in November 2023

The requirement was introduced in an Android Developers Blog post, Ensuring high-quality apps on Google Play, published on November 9, 2023. It introduced the testing requirement and set it at "at least 20 people for a minimum of two weeks".

That number spread quickly. Many guides, YouTube tutorials, forum answers and tester-exchange groups written in 2024 were built around 20. Many of them are still online and still rank in search results, which is why the old number keeps coming up.

What changed in December 2024

Google added an update to the same blog post saying it is "requiring 12 instead of 20 testers for personal developer accounts". The change took effect in December 2024.

The current wording lives in Google's help page, App testing requirements for new personal developer accounts. It says you "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."

Only the tester count went down. If you were planning around 20, you now need fewer people, but you don't need fewer days.

What did not change

  • The 14 days. The original "two weeks" is now written as "at least 14 days", and the duration was not shortened when the count dropped.
  • Continuous opt-in. "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 opts back in later, the 14 days must be consecutive to count."
  • When the count is checked. "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days." Having 12 at the start isn't enough; you need 12 on the day you apply.
  • Closed testing only. Internal testing doesn't satisfy the requirement. Only a closed test counts.
  • Google still decides. Even with 12 testers and 14 days, Google may ask you to keep testing. Its listed reasons include "fewer than 12 opted-in testers or insufficient tester engagement during the testing period."

If you're unsure what "opted in" means in practice, what counts as an opted-in tester walks through it with examples.

Who the 12-tester rule applies to

The requirement applies to personal accounts created after Nov 13, 2023. In Google's own words: "Google Play requires personal developer accounts created after November 13, 2023, to test their apps before those apps are eligible for distribution on Google Play."

Google's official page covers personal accounts only and doesn't mention organization accounts. A community guide written by Product Experts describes organization accounts, and personal accounts created on or before that date, as unaffected. That guide is helpful, but it isn't official Google documentation. If you're not sure which type of account you have or what it means for you, see personal vs organization developer accounts.

When an old guide still says 20

You don't need to throw away an older tutorial. Most of its steps (creating the closed track, adding testers, sharing the opt-in link) may still be useful. Just read it with a few checks in mind:

  1. Look at the date. Anything written before December 2024 will have the old tester count. Treat the number as outdated, then check whether the other steps still match what you see in Play Console.
  2. Take the number from Google, not from the guide. Google's help page is the source of truth, and Google changes its pages without notice. A guide written today could be out of date next year too.
  3. Don't panic if you already recruited 20. Twelve is a minimum, not a limit. Extra testers are allowed, and a few above 12 give you a buffer if someone drops out before day 14. You just don't need to keep hunting for 20.
  4. Be wary of claims that changed along with it. If a guide says the 14 days can be shortened, that internal testing counts, or that approval is guaranteed after the test, none of that matches Google's current help page.

How to check what applies to you in Play Console

Articles, including this one, can be out of date. Your own Play Console is the most reliable check.

  1. Open your app's Dashboard. Google's help page says: "Certain features in Play Console, such as Production … and Pre-registration …, remain disabled until developers meet these testing requirements." If Production is locked for your app, the requirement most likely applies to your account (unfinished account verification can also block it), whatever any guide says.
  2. Read the current requirement on Google's help page. The number there is the one to plan around. As of this writing it's 12 testers for 14 continuous days.
  3. Check how many testers are opted in right now. How to check how many testers have opted in shows where to look.
  4. Work out your earliest application date. Find when your 12th qualifying tester opted in and count 14 full days from there. The closed testing timeline lays out each stage, including Google's review afterwards.
  5. Apply from the Dashboard when you qualify. Google's instructions are short: "Open the Dashboard in Play Console. Click Apply for production." Review "usually takes seven days or less, but can occasionally take longer."

If you want the background on why Google asks for this at all, why Google requires closed testing covers the reasoning behind the rule.

Key takeaways

  • The original November 2023 announcement asked for 20 testers; since December 2024 it's 12 for personal developer accounts.
  • The 14 continuous days did not change, and testers who opt out before day 14 don't count.
  • The requirement applies to personal accounts created after Nov 13, 2023.
  • If a guide says 20, it predates the change. Use Google's help page and your own Play Console as the source of truth.
  • More than 12 testers is fine and gives you a buffer.

When your 14 days are done, our production access guide walks through the questions Google asks. If finding 12 people who stay opted in for the full 14 days is the hard part, GoPlayTester runs the closed test with real people on real Android devices; Google still makes the final decision on production access. Details are on the order page.

All articles