Which track counts toward the 12-testers requirement?

Only closed testing. Internal testing has no minimum and doesn't count toward production access, and open testing doesn't count toward that specific requirement either, even though it's public.

Can I use all three tracks at once?

Yes. They're independent: many teams keep daily builds on internal while a stable build accumulates its 14 days on closed, then use open testing later for broader public feedback.

How many testers do I need for internal testing?

There's no minimum. The official cap is up to 100 testers, but you can use it with a single tester (yourself) to test builds quickly.

What's the most common mistake when picking a track?

Filling the quota on internal testing and assuming it satisfies the production-access requirement. Only closed testing with testers opted in continuously for 14 days counts toward that.

Guide · Play Console tracks

Internal vs Closed vs Open Testing on Google Play

Real differences between Play Console's internal, closed and open testing tracks: tester caps, review, speed, and which one counts toward the production-access requirement. With a comparison table.

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

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.

More resources

Create a quota campaign More resources