Google Play 12 Testers Rule: A Guide for Mobile Game Devs

The Google Play 12 testers rule says that if your personal Play Console developer account was created after November 13, 2023, you have to run a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply to publish. For a mobile game, that is two weeks you can either spend chasing installs or spend getting real feedback. This guide covers what the rule actually requires, how to set up the closed test, how to find testers who will play, and how to answer the production access questions so you are not sent back for more testing.

Everything about the rule below comes from Google's Play Console help pages as of October 2026. Google changes these details from time to time (the minimum used to be 20 testers), so check the official page before you plan your launch date around it.

What the 12 testers, 14 days rule requires

Google's help page on app testing requirements for new personal developer accounts sets out the rule:

• It applies to personal developer accounts created after November 13, 2023. The Play Developer Community guide confirms there is no impact on older personal accounts or organization accounts.
• You must run a closed test, not just an internal test.
• At least 12 testers must be opted in to the closed test when you apply for production access.
• Those testers must have been opted in continuously for the preceding 14 days.
• Until you meet this, the Production page and Pre-registration stay disabled in Play Console.

The help page spells out what "continuous" means. A tester who opts in, tests for fewer than 14 days and then opts out does not count. If someone opts out and back in later, the clock restarts, because the 14 days must be consecutive.

Android Authority reported when Google lowered the number from 20 to 12. The 14 day period stayed the same.

Meeting the numbers is not the same as getting approved

This is the part most guides skip. Hitting 12 testers for 14 days only unlocks the application. Google then reviews it, which the help page says usually takes seven days or less. If Google decides your app needs more testing, you keep running the closed test. The two reasons Google gives are having fewer than 12 opted-in testers, or insufficient tester engagement during the testing period.

So the goal is not 12 names on a list. It is 12 or more people who actually play your game during those two weeks, and evidence that you listened to them.

Set up the closed test

Here is the order that avoids most of the common snags. Menu names are from Google's "Set up an open, closed, or internal test" help page.

1. Finish your app setup first. Google's summary of the tracks says closed testing needs app setup complete. Internal testing does not, so you can use it for quick checks earlier.
2. Optionally run an internal test. Internal testing goes to up to 100 testers by email and builds usually reach them within minutes. It is good for checking your build installs. It does not count toward the 12 testers.
3. Create the closed test. In Play Console go to Test and release, then Testing, then Closed testing, and open Manage track.
4. Choose how testers get access. On the Testers tab you can use email lists (you type or upload the addresses) or Google Groups (anyone who is a member of the group can join). A Google Group is far easier when you are recruiting strangers, because you do not need to collect and paste every email address.
5. Add a feedback channel. Play Console asks for a feedback URL or email address, which appears on the tester opt-in page. Use a short form or a Discord channel so feedback lands somewhere you can read and count.
6. Roll out a release and wait for it to publish. Google notes that the opt-in link only appears when the app's status is Published, and a new test link can take several hours to become available.
7. Copy the opt-in link. Testers in a closed test cannot find your app by searching Google Play, so they need the link. If you used a Google Group, testers must join the group before they can opt in.

One trap that removes testers

Google's help page warns that a user who opts in to your internal test is no longer eligible for your open or closed test until they opt out of the internal test. If a friend helped with your internal test, ask them to leave it before they join the closed test, or they will not count.

Give testers exact instructions

Testers who have never joined a Play closed test get lost. Send them a short, numbered message. For example:

1. Join the Google Group: [link]
2. Open the opt-in link on your Android phone and tap to become a tester: [link]
3. Install the game from the Play Store page that link opens.
4. Stay opted in and keep the game installed for at least 14 days.
5. Play at least three sessions during the two weeks, and send feedback here: [form or Discord link]

Google's own best practices say to tell testers they need to stay opted in for at least 14 days. Put it in bold. It is the single most common reason a tester stops counting.

Recruit more than 12, and recruit players

Google's help page suggests starting with personal and professional networks (friends, family, colleagues, classmates) and then communities where your future users already are. It also says to recruit testers who represent your intended audience, because the closer they are to your real players, the more useful the feedback.

Two lessons come up again and again from developers who have been through it:

• Aim higher than 12. In a reply on r/GooglePlayDeveloper, a developer who got production access for their game said they recruited 20 testers and by the end of the period only 16 still had the game installed. People drop out. Plan for 15 to 20 so you still have 12 on day 14.
• Engagement matters more than the headcount. Replies on r/googleplayconsole make the same point: testers who install once and never open the game again do not help your application.

Where to find testers for a mobile game:

• Friends and family who own Android phones. Good for the headcount, weak for feedback.
• Mobile game communities for your genre: subreddits, Discord servers and forums where people already play games like yours. Read each community's rules before posting. Our guide on where to post your game for feedback covers subreddit and Discord norms.
• Tester swap communities such as r/AndroidClosedTesting and r/TestMyApp, where developers test each other's apps. These help with numbers, but swap testers are often not your target audience, so do not rely on them alone for feedback. Our guide to running a playtest swap covers how to set terms so both sides actually deliver.
• Paid testing services. The "Everything about the 12 testers requirement" guide on the Google Play Developer Community, written by volunteer product experts, says using a third-party company that specializes in testing does not violate the policy. The same guide warns about scams from people selling access to groups who are not recognized testing companies. Faking it with fake accounts or one person running several accounts is a different thing entirely, and it will not survive the engagement check.
• Playtest marketplaces. Platforms where players browse games and choose what to play give you testers who picked your game because they wanted to play it, which is exactly the engagement Google is looking for.

For a wider list of places to look, see our guide on how to find playtesters.

Run the 14 days like a real playtest

Two weeks is long enough to learn a lot about a mobile game. Treat it as a playtest with a schedule, not a waiting room.

Day 1 to 3: first impressions

Ask testers to play their first session and answer three or four questions while it is fresh. Good first-session questions for mobile games:

• Where did you stop playing, and why?
• Was there any moment you did not know what to do?
• Did anything about the controls feel awkward on your phone?
• Would you open the game again tomorrow? Why or why not?

Our list of playtest survey questions has more, sorted by goal, and the game feedback form template shows how to build the form in Google Forms in a few minutes.

Day 4 to 7: give testers a task

Engagement drops after the first session. Give testers something specific to do: reach level 5, try the new mode, beat the first boss, send you a screenshot of their best score. A task gives them a reason to open the game and gives you something concrete to ask about.

Day 7: check in and ship an update

Collect a written check-in from each tester. Then ship at least one update that fixes something testers reported. Developers in the threads above, and the dev.to write-up on the production access form, all point to the same thing: Google wants to see that you acted on feedback. A small fix tied to a real report counts.

Day 8 to 14: test the change

Ask testers to try the update and tell you whether the problem is gone. That gives you a before and after you can describe in your application. Send a reminder around day 12 that they need to stay opted in until you apply.

Keep a running log

Write down, as you go: how many testers are opted in, who sent feedback on which day, the main themes, and every update you shipped with its version number and the feedback it answers. Our playtest report template works well for this, with one short entry per check-in.

Answer the production access questions

When you click Apply for production on the Dashboard, Google's help page says the form has three parts.

About your closed test

You select how easy it was to recruit testers, describe tester engagement (whether testers used all features, and whether their use matched how you expect real players to use the game), and summarize the feedback and how you collected it.

Be specific. Instead of "testers enjoyed the game", write something like "most testers played several sessions, the most common complaint was that the second world's difficulty jump felt unfair, collected through an in-game feedback link and a day 7 form." Use your real numbers from the log.

About your game

You describe your target audience, explain what makes your game unique, and pick an estimated install range for the first year. For games, Google specifically asks what makes the game unique, so give a clear sentence about your hook, not a feature list. The help page says these answers are not shown publicly.

About your production readiness

You describe the changes you made based on the closed test and how you decided the game is ready. This is where the update you shipped on day 7 pays off. List each change, what feedback it answered and which version it shipped in.

The dev.to article from a testing marketplace founder who reads rejection emails makes a useful point: the reason for refusal is rarely too few testers. It is usually not enough engagement, or no sign the developer did anything with what testers said. Both are judged from what you write in this form.

Before you click Apply

Google's help page also lists things to check before applying: that the content and monetization follow Play policies, that the target age group and content rating are accurate, that the game is stable without crashes or missing screens, and that you have provided working test login details if your game needs an account.

Common mistakes with the 12 testers rule

• Recruiting exactly 12. One drop-out and you are back to waiting. Recruit more.
• Using only internal testing. Internal testers do not count, and testers in your internal test cannot join the closed test until they leave it.
• Telling testers to uninstall after a day. Make the 14 day requirement the first thing they read.
• Shipping no updates during the test. It leaves you with nothing to write under changes made.
• Collecting no written feedback. If feedback only happened in voice chat, you cannot summarize it. Use a form or a channel you can scroll back through.
• Starting the clock before the build is ready. A crash on launch burns the first days of your two weeks and the goodwill of your testers.

Using Get Playtests for your closed test

On Get Playtests you can post your game for free, with no credit card, and players pick it from the open playtests because it looks like something they want to play. A posting has the focus questions you want answered and a build link, and Google Play links can go live right away. Reviews come back written, on video or as a livestream, which gives you real material for the engagement and feedback questions on the production access form.

Since a closed test needs testers on your email list or Google Group, put the Google Group link, the opt-in link and the "stay opted in for 14 days" instruction clearly in your posting. Post your playtest free.

Common questions

Does the 12 testers rule apply to organization accounts?

No. Google's help page applies the requirement to personal developer accounts created after November 13, 2023, and the Play Developer Community guide confirms organization accounts and older personal accounts are not affected.

Do I need new testers for every app?

Google's help page describes the closed test as something you run for each app before it can reach production, so plan a 14 day closed test for every new game. Testers who helped with your last game can join again, as long as they opt in to the new test and stay for 14 days.

Do the 12 testers need to play every day?

Google's help page does not publish a daily usage number. It names insufficient engagement as a reason for more testing. The community guide goes further and lists testers who did not have the app installed, did not actively test it daily, or left the program during the 14 days as reasons developers get the "more testing required" email. Give testers reasons to come back across the two weeks and record that they did.

Can I pay for testers?

The Google Play Developer Community guide says third-party testing companies do not violate the policy, and warns that people selling access to tester groups are not recognized testing companies. Whatever route you take, describe it honestly in the application.

Is a closed test the same as a beta?

It is Google Play's tool for distributing a test build to a group you control. Whether you treat it as a playtest or a beta depends on how finished the game is. See playtest vs beta test for the difference, and our beta testing checklist for running the round itself.

Is there an iOS version of this rule?

No. Apple has no minimum tester count before release, but external TestFlight builds go through TestFlight App Review and expire after 90 days. If you ship on both stores, our TestFlight beta testing guide covers the iOS side.