Closed vs Internal vs Open Testing on Google Play: What's the Difference?

The three tracks at a glance

Internal testing

Internal testing is built for speed. You add up to 100 testers by email, upload a build, and it's usually available to them within minutes. It's perfect for checking a build on your own devices or sharing it with your team.

But it doesn't count towards the closed testing requirement for new personal accounts. Many developers lose days by running their 12 testers on the internal track by mistake.

Closed testing

Closed testing is invite-only. You add testers as an email list or a Google Group, Google reviews your release, and then testers join through an opt-in link. You can run several closed tracks. The default is usually called Alpha.

This is the track that matters for the requirement: 12 or more testers opted in for 14 days in a row before you can apply for production access. Here's how to set one up step by step and how to get your opt-in link.

Open testing

Open testing is a public beta: anyone can find your app's testing program on Google Play and join, and you can cap how many people get in. It's great for gathering feedback at scale once you have an audience.

For new personal developer accounts, open testing (like production) only becomes available after you've met the closed testing requirement and been granted production access.

Which one should you use?

1. 1Step 1

   Internal

   Check each build on your own devices and with your team.

2. 2Step 2

   Closed

   Run your 12+ testers for 14 days to unlock production.

3. Step 3

   Production (and open testing)

   Once Google grants access, launch, or run a public beta first.

Most developers use both internal and closed: internal for quick checks, closed for the real test. Just make sure the 12 testers are on the closed track.

FAQ