Closed vs internal vs open testing: which Google Play track to use

Google Play gives you three testing tracks. Here is what each one is for — and which actually satisfies the production-access requirement.

Google Play offers internal, closed, and open testing tracks. They look similar in Play Console, but they serve different purposes — and only one of them clears the new production-access requirement. Here is the plain-English breakdown.

Internal testing

Up to 100 testers, added by email.
Instant — no review delay; builds go live to testers in minutes.
Best for: your own team, quick smoke tests, sharing a build fast.
Does not satisfy the 14-day closed-testing requirement.

Closed testing

Testers join via an email list or a Google Group.
This is the track tied to the 12 testers / 14 days rule for new accounts.
Best for: the official pre-production cycle, gathering structured feedback.
Yes — this is the one that unlocks production access.

Open testing

Anyone with the link can join; your app can also appear publicly as "early access".
Larger audience, less control, public-facing.
Best for: a broad beta once you are more confident.

Side-by-side

Track	Who can join	Review delay	Clears production requirement
Internal	Up to 100, by email	None	No
Closed	Email list / Google Group	Short	Yes
Open	Anyone with the link	Short	No

If your goal is to publish a new app, closed testing is the track that matters. Use internal testing alongside it for fast iteration, but the 14-day clock only runs on closed.

A practical workflow

Use internal testing to validate each build instantly.
Run closed testing in parallel to satisfy the requirement with your 12 testers.
Optionally graduate to open testing for a wider beta before launch.

Get the track right and you avoid the most common new-developer mistake: spending two weeks on internal testing that never counted.