Google Play Closed Testing vs Open Testing
Who can join, how many testers you can add and which track counts toward the 12-tester, 14-day requirement.
Read the guide →Google Play Internal Testing vs Closed Testing
Quick answer In internal testing vs closed testing, internal is a quick check for up to 100 testers and does not unlock production, while closed testing with 12 testers for 14 days does.
Internal testing and closed testing both let you share your app with a small group before it goes live, but they have different limits and different purposes. If you have a new personal account, mixing them up can cost you time. This guide shows the difference and when to use each one.
What is each testing track for?
Internal testing is for your own team. It is the quickest way to get a build onto real devices so that you and your colleagues can check it. Closed testing is for a wider invited group, such as beta users. It is also the track that counts for the production access requirement on new personal accounts.
Internal vs closed testing compared
These facts come from Google's Play Console Help page on testing tracks.
- Tester limit: internal testing allows up to 100 testers per app. Closed testing allows up to 200 email lists of up to 2,000 users each, with up to 50 lists per track.
- Who joins: internal testers are added by email address. Closed testers come from email lists, Google Groups or organizations.
- Visibility: neither track is searchable on Google Play. You share the opt-in link or Play Store URL.
- Setup: internal testing is under Testing > Internal testing > Testers. Closed testing is under Testing > Closed testing > Manage track > Testers. You can start internal testing before app setup is complete.
- Review: Google notes that internal test releases may not be subject to standard Play policy or security reviews.
Using both in the right order
- Start with internal testingCheck that the app installs and the main flows work, with a few trusted people.
- Fix obvious problemsCrashes, login issues and layout problems are easier to fix before many people see them.
- Move to closed testingSet up your closed track, add your testers and share the link. See our guide to adding testers.
- Run the 14 daysKeep at least 12 testers opted in for 14 days in a row.
Careful: Google says a user who is opted in to internal testing cannot receive open or closed test versions until they opt out. Do not put your closed testers on the internal list.
Which track unlocks production access?
For personal accounts created after November 13, 2023, the requirement is a closed test with at least 12 testers opted in for 14 days. Internal testing is useful, but it does not replace it. Read the closed testing requirements checklist or compare closed testing with open testing.
Common mistakes
- Using internal testing as the production requirement. It is not the closed test Google asks new personal accounts to complete.
- Adding the same people to both tracks. A user opted in to internal testing cannot receive closed test versions until they opt out.
- Forgetting the opt-in link. Testers must open the link, then install from Google Play.
- Assuming internal testing is fully reviewed. Google says internal releases may not be subject to the standard policy and security reviews, so you should not treat it as a final check.
A simple example
You build a new app. Your team of three tests it through internal testing for a few days. After you fix the crashes, you create a closed test, add 15 testers, and keep them opted in for 14 days. During that time, they send feedback and you release one update. When the 14 days are done, you apply for production. If you want to understand the production step, read how to apply for production access.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
A testing flow that saves time
| Stage | Track | Goal | Time |
|---|---|---|---|
| 1. Does it install and run? | Internal | Catch crashes and obvious bugs | Minutes to days |
| 2. Does it work for real people? | Closed | 12+ testers, 14 days, feedback | 14+ days |
| 3. Is it ready for everyone? | Production | Release to all users | After approval |
The conflict to avoid
Google says a user opted in to internal testing cannot receive open or closed test versions until they opt out of the internal test. If your closed testers are also on the internal list, remove them from the internal list before you start. Otherwise they may see an older build. If that happens, follow the link troubleshooting guide.
Who belongs in internal testing
- You and your developers.
- A few trusted colleagues who can report bugs precisely.
- People who need quick builds, not people you rely on for the 12-tester count.
Keep your closed testers separate, and keep them to the plan in how to share the closed testing link.
Frequently asked questions
Does internal testing count toward the 12-tester requirement?
No. The requirement is for a closed test with at least 12 testers opted in for 14 days. Internal testing is a separate track.
How many testers can an internal test have?
Google allows up to 100 testers per app for internal testing.
Can I start internal testing before my app setup is finished?
Yes. Google says you can start an internal test before app setup is complete.
What happens if a tester is opted in to internal testing and a closed test?
Google notes that a user who is opted in to internal testing cannot receive open or closed test versions until they opt out of internal testing.
