12 or 20 testers: how many does Google actually need?

Search for this and you will find both numbers stated as fact. Both were true, at different times. Here is the actual history and what it means for a run you are starting today.

The short answer

Twelve. Google requires at least 12 testers 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.

The reason 20 keeps appearing is that 20 was the original number. When the policy arrived in November 2023 it applied to personal developer accounts created after 13 November 2023, and it demanded 20 testers. Google reduced it to 12 in December 2024 after a year of developers saying that finding 20 reliable people was the hardest part of shipping an app. Anything written before that date, and a fair amount written since, still says 20.

Twelve is a floor, not a target

This is the part that costs people two weeks. Google does not check whether you started with 12. It checks whether 12 were opted in continuously for the 14 days before you applied. Continuously is doing the work in that sentence.

If your count is exactly 12 and one person changes phone, factory resets, or taps "leave the programme" without telling you, you are at 11. The requirement is no longer being met. The days you have already banked stop counting toward the run, and you find out when you open Play Console expecting the production access form and it is not there.

Google's own FAQ is blunt about it: testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement.

So how many should you run?

Enough that one or two silent departures do not matter. In practice:

• 12 testers. Meets the rule on paper. One drop-out breaks it. Only sensible if every tester is someone you can phone.
• 14 to 16 testers. The sweet spot. Two or four spare people absorb the normal rate of attrition over a fortnight without you doing anything.
• 20 or more testers. Genuinely safe, and what most paid services upsell. Worth it if your app is large, crashes on some devices, or asks for permissions people dislike, because those are the apps testers actually uninstall.

Appline supplies 14 and holds them for 16 days for exactly this reason. Two spare people, two spare days.

Does a bigger number improve your odds of approval?

Not directly. Google is checking a floor, not scoring you against a curve. Twenty testers who install and never open the app again are worth less than twelve who use it, because the production access form asks what feedback you received and what you changed as a result. A vague answer there is one of the most common causes of refusal even when the tester count is fine.

So the honest framing is: extra testers buy you insurance against the count dropping, not credit with the reviewer. Buy the insurance, then earn the credit separately by writing a specific application.

What about organisation accounts?

The requirement targets personal developer accounts created after 13 November 2023. If you registered as an organisation, or your personal account predates that cut-off, the closed testing requirement does not apply to you in the same way. Check the requirements card on your Play Console dashboard rather than guessing: it tells you directly whether the testing requirement is live on your account.

If you have already seen 20 somewhere

Check the date on the page. Anything from 2024 or earlier is describing the old rule, and a surprising amount of tester-service marketing has never been updated. The number to satisfy today is 12. The number to actually run is more than 12.