Closed vs Internal Testing on Google Play
Last updated: 5 November 2026
Quick answer
Internal testing is for quick builds shared with up to 100 people on your team. Closed testing is for a wider group of invited testers and is the only track that counts towards Google's 12 testers / 14-day requirement for new personal accounts.
Google Play's testing tracks at a glance
| Internal testing | Closed testing | Open testing | |
|---|---|---|---|
| Who can join | Up to 100 testers you add by email | Invited testers (email lists or Google Groups) | Anyone who finds it on Google Play |
| Review | Usually available within minutes | Reviewed like a normal release | Reviewed like a normal release |
| Counts for 12 testers / 14 days | No | Yes | No (needs production access first) |
| Best for | Quick team QA and debugging | Pre-launch testing and the production requirement | Public betas at scale |
What is internal testing?
Internal testing is the fastest way to get a build onto real phones. You add up to 100 testers by email, upload a build, and it is usually available within minutes. It is ideal for your own team, but because it is meant for internal use, it does not count towards the production access requirement.
What is closed testing?
Closed testing lets you share pre-release builds with a larger, invited group. You add testers using email lists or Google Groups, they opt in using a link, and they install the app from Google Play as normal. Closed testing releases go through Google's review. For personal accounts created after 13 November 2023, a closed test with at least 12 testers for 14 continuous days is required before you can publish to production. Read the full 14-day rule guide.
What is open testing?
Open testing makes your test version visible on Google Play so anyone can join. New personal accounts can only use it after they have been granted production access.
Which one should you use?
- Just checking your build works? Use internal testing.
- New personal account that needs production access? Use closed testing with at least 12 testers for 14 days, ideally a few more to cover drop-offs.
- Already in production and want a public beta? Use open testing.
Moving from internal to closed testing
- In Play Console, open Testing → Closed testing.
- Create a release. You can promote the build you already tested internally.
- Add your tester email list or Google Group.
- Send the release for review, then share the opt-in link.
Need testers for the closed track? See how Closed Test Hub works.
Frequently asked questions
Does internal testing count for the 14-day requirement?
No. Only closed testing counts towards the 12 testers / 14-day requirement for new personal developer accounts.
Can I use internal and closed testing at the same time?
Yes. Many developers use internal testing for quick team builds and closed testing for the 14-day requirement. They are separate tracks with separate tester lists.
How many testers can a closed test have?
Closed tests can use email lists of up to 2,000 testers each, or Google Groups for larger audiences. You need at least 12 for the production access requirement.
Can I use open testing instead of closed testing?
No. For new personal accounts, open testing only becomes available after you have been granted production access, so the closed track is the one you must use.
Need 12+ testers for your closed test?
Closed Test Hub gives you real testers on physical Android phones, a tester-by-day dashboard for all 14 days, and a feedback report you can use in your production application. Plans start at ₹699.
More guides
- 12 testers & 14-day rule explained
- How to apply for production access
- Free tool: closed testing tracker
Closed Test Hub is an independent service and is not affiliated with Google or Google Play. Google can change its policies at any time, so always confirm the current requirements in your Play Console.