Guide · Play Console tracks
Internal, Closed or Open Testing: Which Counts for Production
Updated:
Only closed testing counts toward the 12 testers for 14 days requirement. Table of Play Console's internal, closed and open tracks: how many testers each allows and whether Google reviews it.
Play Console offers three testing tracks with different purposes. Mixing them up is the number-one reason a team thinks it has covered the production-access requirement and finds out it hasn't.
Comparison table
| Internal | Closed | Open | |
|---|---|---|---|
| Tester cap | Up to 100, no minimum | Minimum 12 for production | Unlimited (or from 1,000) |
| Counts toward production requirement? | No | Yes — the only track that counts | No |
| How testers join | Email list / group | Email list, link or groups | Public link on the Play listing |
| Availability speed | Minutes after publishing | Standard Google review | Standard Google review |
| Visibility | Invited only | Invited only | Anyone from the Play listing |
| Typical use | Team's daily builds | Stable beta accumulating 14 days | Public beta / broad feedback |
What is internal testing in Google Play?
Internal testing is the fastest Play Console track: you add up to 100 internal testers by email or Google Group, the build is available within minutes and there is no Google review. It is meant for your own team and QA, not for the public. Internal testers are not counted toward the production-access requirement, and an internal test does not need any minimum number of people or days.
What is open testing in Google Play?
Open testing (sometimes called "open beta") is a public track: anyone can find the test on the Play listing and join without an invite, and reviews from open testers are private. Use it when you want scale and broad device coverage before launch. The catch: open testing does not satisfy the 12-testers / 14-days requirement for new personal developer accounts, so run it after, or alongside, a closed test, never instead of it.
Which one to use, by phase
- Internal — for your own team testing daily builds. Available within minutes, no Google review.
- Closed — the only track that counts toward the 12-testers / 14-days requirement. Use it with a stable build, not one you change hourly.
- Open — when you want broad public feedback before production; anyone can join from the Play listing.
The mistake that costs the most
Gathering 12+ people on internal testing and finding out, when requesting production access, that the track doesn't count — only closed testing with continuous opt-in for 14 days does. If your goal is unlocking production, build your tester campaign directly on the closed track.