Internal vs Closed vs Open Testing on Google Play
How Google Play internal, closed and open testing differ: tester limits, review, visibility, paid apps, and which track counts for the 14-day rule.
Google Play Console offers three pre-release testing tracks. They look similar in the console but serve different purposes, and only one of them satisfies the 12 testers for 14 days requirement for new personal accounts. Facts below come from Google's help page on open, closed and internal tests.
Side-by-side comparison
| Internal | Closed | Open | |
|---|---|---|---|
| Who can join | Up to 100 testers you choose | People on your email lists or Google Groups | Anyone |
| Size limits | 100 testers per app | Up to 200 email lists, 2,000 users each | Large, public audience |
| Speed | Available within minutes | After the release is available on the track | After the release is available on the track |
| Visible on Google Play? | No | No (opt-in link only) | Yes, users can find it |
| Paid apps | Testers install for free | Testers must purchase | Testers must purchase |
| Counts for the 14-day rule? | No | Yes | No (the rule names closed testing) |
In all test tracks, Google notes that testers can't leave public reviews for test versions, but they can send you private feedback through Google Play.
Internal testing: fast checks with your team
Internal testing is for quick distribution to up to 100 people, typically your own team. Google says builds become available within minutes and might not be subject to standard Play policy or security reviews. That makes it great for smoke-testing a build before wider release, but it does not count toward the production access requirement.
Closed testing: the one that counts
Closed testing lets you invite a specific group by email list or Google Group. Testers join through an opt-in link and install from the Play Store. This is the track Google's requirement refers to: at least 12 testers opted in continuously for 14 days. Our step-by-step closed testing setup guide walks through creating it.
Because you control who joins, closed testing pairs naturally with a tester-exchange community like TestersZone: you paste testers' emails into your list, and they check in daily with feedback.
Open testing: public beta
Open testing makes your test version discoverable on Google Play, and anyone can join. Google asks you to make sure your app and store listing are ready for visibility on Google Play first. It's best for a larger public beta once your app is stable, usually after you already have production access.
Which one should you use?
- Internal to sanity-check each build with yourself or your team.
- Closed to run your 14-day test with 12+ real testers and collect feedback for your production access application.
- Open later, for a public beta with a wider audience.
You can run tracks in parallel. Many developers keep an internal track for their team while the closed test runs.
How we keep this accurate
Policy facts in this guide are checked against Google's Play Console Help pages, linked inline, on the date shown above. Google can change its requirements at any time, so always confirm in your own Play Console. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start free