In Google Play Console, what are the internal, closed, open and production tracks, and who can install a build from each?
answer
- four audiences, narrow to wide
- internal: 100 testers, minutes
- closed: lists, groups, organizations
- open: visible, anyone joins
- testers must opt in
basics
~20 sPlay Console has four tracks: internal testing (up to 100 listed testers), closed testing (testers invited by email list, Google Group or organization), open testing (any Google Play user can join) and production (all Google Play users in your chosen countries).
solid answer
~40 sA track is a release channel with its own audience. **Internal testing** reaches up to 100 testers listed by email, and a new bundle is available to them within minutes, even before app setup is finished. **Closed testing** reaches testers you choose by email list, Google Group or organization, and you can add extra named closed tracks for separate teams. **Open testing** makes the test version visible on Google Play so anyone can opt in, optionally capped at 1,000 or more testers. **Production** reaches every Google Play user in the countries you select. Testers must opt in through the track's link, and an internal tester is not eligible for closed or open builds. Personal accounts created after November 13, 2023 must run a closed test with 12 testers for 14 days before production unlocks.
go deeper
Name the four tracks in order and say who each one reaches, with the 100-tester limit on internal testing and the opt-in link every tester uses.
Explain eligibility: list membership plus opt-in, why an internal tester stops getting closed builds, and why open testing is public on Google Play.
Show you have run tracks in production: extra closed tracks per team, pausing a track, the hours-long first link delay and the new-account closed-test gate.
Treat the tracks as an exposure ladder the team owns: which audience sits on each rung and what evidence lets a build climb to the next one.
## What a track is In **Play Console**, a **track** is a release channel with its own audience. Every Android App Bundle you upload sits in a **release**, and that release is rolled out on one track. Play Console has four kinds of track, and moving a build from the narrowest audience to the widest is how most teams ship. ## The four tracks | Track | Who can install | How they get in | Limits worth knowing | |---|---|---|---| | **Internal testing** | Testers you list by email | Opt-in link | Up to **100** testers per app; a new bundle is available within minutes | | **Closed testing** | Testers you choose | Email lists, **Google Groups** or an organization | Up to 200 email lists of up to 2,000 users each; you can create extra named closed tracks | | **Open testing** | Any Google Play user who joins | Opt-in from the store listing or a link | Optional cap, which must be at least 1,000 testers | | **Production** | Every Google Play user in the countries you select | Nothing to join | The release everyone is eligible for | Some details that make each one useful: - **Internal testing** can start before app setup is complete. A first upload is available to internal testers at once, under a temporary name for up to 48 hours. Device exclusion rules do not apply to internal testers, and testers of a paid app install it free. - **Closed testing** is for a wider, still controlled group. Its first track is created for you; additional closed tracks let separate teams test separate builds at the same time. - **Open testing** makes the test version visible on Google Play. Before an app has a production release, users can find the open test through search; once it has one, they opt in from the store listing. - **Production** reaches everyone in the selected countries and regions. Pricing changes apply to every track, and so do country changes, except that internal testers can be anywhere. ## Opting in and finding the build Being on a list is not enough. A tester must: 1. Be included in the track's tester configuration (email list, group or organization). 2. Open the track's **opt-in link** and accept, which is shown only once the app's status is published. 3. Install or update from Google Play; after opting in, the installed app moves to the test version within a few minutes. Before an app has an open test or a production release, internal and closed testers cannot find it by searching Google Play, so you share the link. The first time a test is published, the link can take several hours to work. ## Rules that trip people up - **An internal tester is not eligible for closed or open builds**, even when listed on those tracks; they must opt out of the internal test first. - You can run **several closed tests and one open test** at the same time. - Testers cannot leave public reviews on test versions, and their feedback does **not** affect the public rating; give them a feedback email or URL. - Paid apps: open and closed testers must buy the app; internal testers do not. - **Pause track** ends a test: testers stop receiving updates, but the app stays installed. - Before its first review, an app tested only internally shows a **temporary name** on Google Play, and once you upload an artifact the **package name is fixed**. - Internal tests might not get the standard policy and security reviews, and an app active only on the internal track is exempt from the Data safety section. ## New personal developer accounts Personal Play Console accounts created after **November 13, 2023** have an extra gate. Production and pre-registration stay disabled until the developer runs a closed test with **at least 12 testers opted in continuously for 14 days**, then applies for production access from the Dashboard; open testing also unlocks only after production access is granted. ## Worked example A fintech team ships version 4.2. Every merged build goes to the **internal** track for the team's QA engineers within minutes. A candidate goes to a **closed** track for a few hundred existing customers on a Google Group. When it holds up there, the same bundle is released to **production** as a staged rollout. The team skips open testing, because a public beta of a banking app would be visible to anyone on Google Play. When a candidate fails in closed testing, the team rolls a newer build out on the same closed track rather than starting a new test.
- What must a new personal developer account do before Play Console lets it publish to production?Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in continuously for 14 days, then apply for production access from the Dashboard and answer questions about the test, the app and its readiness. Production and pre-registration stay disabled until then, and open testing unlocks only after production access is granted.
- How does internal app sharing differ from the internal testing track?Internal app sharing gives each uploaded bundle or APK its own link, usable by up to 100 people and expiring 60 days after upload. Builds may be debuggable, signed with any key (Play re-signs them with an internal app sharing key) and may reuse version codes, but they never enter a track release. Testers must first switch on internal app sharing in the Play Store app's settings.
- Internal testing is a private production release with no tester limit.
- Adding someone to a tester list installs the build without them opting in.
- An internal tester also receives closed and open builds when listed there.
- Closed testers can find a never-released app by searching Google Play.
- Feedback from testers lowers the app's public star rating.
Assumes Play Console as of 2026-10-10; the closed-test gate applies to personal developer accounts created after November 13, 2023.