Google Play changed 20 testers to 12: what it means for you

Updated

If you have read that Google Play needs 20 testers, you have read something out of date. Since December 2024 the number is 12. Everything else about the rule stayed the same.

The short history

  • November 2023. Google introduced a testing requirement for new personal developer accounts. Accounts created after 13 November 2023 had to run a closed test with 20 testers opted in for 14 continuous days before they could apply for production access.
  • December 2024. Google reduced the number of testers from 20 to 12. Play Console began asking for a closed test with at least 12 testers for at least 14 days continuously.

Google's help page today states the rule as a minimum of 12 testers who have been opted in continuously for at least 14 days.

What did not change

Only the number moved. These are exactly as they were:

  • Who it applies to. Personal accounts created after 13 November 2023. Organization accounts, and personal accounts created before that date, are not subject to it.
  • Fourteen continuous days. Not fourteen days in total, and not fourteen separate days.
  • Opted in, not invited. A tester counts when they accept through your opt-in link, not when you add their email.
  • The production access application. You still apply after the test and answer questions about it, and review still follows.

The full rule, word by word, is in the 12 testers requirement explained.

Why you still see 20 everywhere

The rule spent a year at 20, and a lot was written in that year: forum answers, videos, blog posts and templates. Much of it has never been updated, and search engines and AI assistants still surface it. If a source says 20, check its date. Anything written before December 2024 describes the old number.

Play Console itself is the source that matters. It shows the requirement that applies to your account on the app's Dashboard.

Does 12 make it easy?

It makes it easier, not easy. Eight fewer people is a real saving, but the hard part was never the count on day one. It is keeping the count for fourteen days. One uninstall on day nine puts twelve testers below the line just as it did twenty, and the smaller the cohort, the bigger each drop-out is.

That is why the practical advice is the same as it always was:

  1. Recruit around fifteen. A margin of three covers the usual losses: a phone replaced, an app uninstalled to free space, a tester who wanders off.
  2. Verify each opt-in in Play Console instead of trusting replies.
  3. Check the count every few days, and replace drop-outs the same day. What to do when someone opts out.
  4. Keep everyone until access is granted. The review comes after the test.

If you are starting from zero, here is every free way to get 12 testers, ranked by how well each one keeps people opted in.

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Applying for production soon? Check your APK against the Google Play launch checklist - target API, permissions that need a declaration, your Data Safety form and leaked keys. The first check is free.

Common questions

Does Google Play still require 20 testers?
No. Google reduced the requirement from 20 to 12 testers in December 2024. Personal developer accounts created after 13 November 2023 now need at least 12 testers opted in to a closed test for 14 continuous days.
Did the 14-day period change when testers went from 20 to 12?
No. Only the number of testers changed. The 14 continuous days, the need for testers to opt in, and the production access application all stayed the same.
Should I still recruit 20 testers to be safe?
You do not need 20, but aim for more than 12. Fifteen gives you a margin for a drop-out or two without falling below the line, which matters more than hitting any round number.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

FitLifeApp is a daily habit and goal-tracking app that helps users monitor water intake, step goals, and mood entries. Please test the following: - Set a daily water goal, add water intake, and check whether the totals and remaining amount update correctly. - Set a step goal and check the progress display. - Add mood entries and review previous records. - Close and reopen the app to check whether your saved data is still available. - Use the app on different days to check daily tracking and history. - Check for confusing navigation, overlapping text, or buttons that do not work correctly. Please join the Google Group and the Google Play closed test using the same Google account. Install the app through Google Play and stay enrolled for at least 14 consecutive days, using its features during the testing period. When reporting a problem, include what happened, the steps to reproduce it, your device model, and Android version. Screenshots are welcome. Thank you for helping improve FitLifeApp!

Health & FitnessProductivityLifestyle

Open to testers · 14-day test

Closed testing

Testers must join the Google Group using the same Google account they use on their Android device's Google Play Store. Testers must open the opt-in link, tap Become a tester, and then download the build via the Play Store link provided.

News & Books

Open to testers · 14-day test

Closed testing

Hi! I’m looking for testers for Crew Bites, a Flutter app that helps groups organize food orders, track who ordered what, and calculate the final bill fairly. Please test the main flow: add people, add food orders, select a restaurant/bundle, add tax/service/tip/delivery, review the total, and save or share the result. I’d especially appreciate feedback about usability, layout, performance, and any bugs on your Android device. Thank you!

Food & Drink

Open to testers · 14-day test

Related guides

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·