Internal vs closed vs open testing on Google Play: the differences
What each Google Play testing track is for, who can join it, how fast releases arrive and which one counts for the 12 testers requirement.
Updated 20 Nov 2026
Internal testing
Internal testing is for quick checks with your team. You can add up to 100 testers by email, and new releases usually reach them within minutes.
It does not count for the 12 testers for 14 days requirement. Use it to make sure a build installs and starts before you send it to the closed track.
Closed testing
Closed testing is for a wider group you choose, added with email lists or Google Groups. Testers opt in with a link and install the app from Google Play.
This is the track that counts for new personal developer accounts: at least 12 testers opted in continuously for 14 days before you can apply for production access. Releases go through Google’s review before testers get them.
Open testing
Open testing lets anyone join from your Play Store listing, without an invitation. For new personal accounts it becomes available only after you get production access, so it cannot replace the closed test.
Side by side
- Internal: up to 100 testers you invite by email, fastest releases, does not count for the requirement.
- Closed: testers from email lists or Google Groups, releases reviewed by Google, the only track that counts for the 12 testers for 14 days.
- Open: anyone can join from the Play Store, available to new personal accounts only after production access.
A practical order
Upload the first build to internal testing and check that it installs and starts on a couple of devices. Then promote it to closed testing and invite your testers there. After 14 days with 12 testers, apply for production access, and only then consider an open test for a wider beta.
Frequently asked questions
Can I move testers from internal to closed testing?
They have to opt in to the closed track. Add them to the closed track’s email list or Google Group and send them its opt-in link.
Does an open test count for production access?
No. New personal accounts need a closed test, and open testing is only available to them after production access.