Google Play closed testing: the complete guide
Closed testing is how you put a pre-release version of your app in front of people you choose. For a personal developer account created after 13 November 2023, it is also the gate to production: at least 12 testers, opted in for 14 continuous days, before you can apply. This page covers the whole path and links to the detail.
What is closed testing?
One of Google Play's three testing tracks. You invite testers by email list or Google Group, share the test's opt-in link, and each tester accepts and then installs the app from its Play Store page. Testers need a Google account, and they get your testing build instead of the production one.
A closed release is reviewed by Google before testers can install it, so the first build can take a while to reach them. After that, you can keep shipping updates to the same testers during the test.
How is it different from internal and open testing?
| Track | Who can join | Review | Counts for the requirement |
|---|---|---|---|
| Internal testing | Up to 100 testers you add by email address | Skipped or minimal, so builds reach testers fast | No |
| Closed testing | People you invite by email list or Google Group, who join through an opt-in link | Reviewed before testers can install | Yes: 12+ testers for 14 days |
| Open testing | Anyone who finds the test on your Play Store listing | Reviewed before testers can install | No |
Two weeks of internal testing does not transfer. More on the difference: closed testing vs internal testing.
Who has to run a closed test, and for how long?
Personal developer accounts created after 13 November 2023. Google's wording: 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.” Organisation accounts are not subject to it. The number was 20 until Google lowered it to 12 in December 2024.
- The rule and its edge cases: Google Play's 12 testers, 14 days requirement.
- It applies to each app: do you need new testers for every app?
- When you will be eligible: the production access date calculator.
How do I set up a closed test?
- Finish the setup tasks Play Console marks as required, including a store listing and the Data safety form.
- Open Test and release, Testing, Closed testing, and manage the closed track.
- Choose countries and regions: a tester outside them cannot install the app.
- Add testers by email list or Google Group, and set a feedback email or URL.
- Create a release with your signed App Bundle and roll it out for review.
- Once it is published, share the opt-in link, then check the tester count in Play Console.
Step by step, with the mistakes that cost days: how to set up a closed test in Play Console.
What goes wrong during a closed test?
- The opt-in link does not work. Opt-in link not working: what to check.
- Testers say they joined, but the count is short. Six causes, and how to tell which.
- A tester abroad cannot install. Can testers be in different countries?
- Someone drops out on day nine. What happens if a tester opts out.
- You need to ship a fix mid-test. A new build does not reset the clock: why not.
Where do I find 12 testers?
Friends, communities, exchanges and paid services all work, with different costs. TestersWiz is a free test-for-test exchange: you test another developer's app, they test yours, and each opt-in is verified in Play Console. Every route compared: how to get 12 Google Play testers for free.
What happens after the 14 days?
The Apply for production button appears. The application asks about your test, your app and how you decided it was ready, and Google says review usually takes seven days or less. How to answer the production access questions, and how long the review takes.
Before you apply, check the build itself: target API level, permissions that need a declaration, the Data safety form and anything secret left in the APK. The Google Play pre-launch checklist covers each one.
Common questions
- What is closed testing on Google Play?
- A testing track that distributes a pre-release version of your app to people you invite, by email list or Google Group. Testers join through an opt-in link and install from the Play Store.
- How long does Google Play closed testing take?
- For new personal accounts, at least 14 days with 12 or more testers opted in the whole time, then a production access review that Google says usually takes seven days or less. Allow for the closed release's own review before testers can join, too.
- Does internal testing count for the 12 testers requirement?
- No. Only a closed test counts toward the requirement for new personal developer accounts.
- Can I update my app during closed testing?
- Yes. Uploading a new build does not reset the 14 days, which count testers who are opted in, not builds.