Internal, Closed, Open and Production: Google Play Testing Tracks Explained

Google Play gives you four places a release can live: internal testing, closed testing, open testing, and production. Each one controls the same thing — who can install your app — but at very different scale, and only one of them counts toward the closed testing requirement.

Internal testing: the team sandbox

Internal testing is for small, fast feedback loops — typically your own team, capped at 100 users. It's ideal for shipping a build to your colleagues minutes after uploading it. It does not count toward the 12-tester requirement.

Closed testing: the requirement track

Closed testing is the track Google uses for the production requirement. You control exactly who can join — email lists of up to 2,000 users each, Google Groups without limits, per track. Releases appear in Play for your testers only, and the feedback channel you configure shows on the opt-in page.

Open testing: public beta

Open testing makes your app available to anyone with the link — a public beta that doesn't touch your production listing or ratings. Because it exposes your app broadly, open testing only becomes available after you've gained production access.

Production: live on Google Play

Production releases go through Google's standard review. For personal accounts created after November 13, 2023, production access itself is gated behind the closed testing milestone.