Closed Testing vs Internal App Sharing on Google Play
Internal app sharing gives instant download links for any build; closed testing is the reviewed track that counts for production access. When to use each.
Short answer
Internal app sharing is for quick developer handoffs: upload any build, get a link, no version-code rules, up to 100 downloads per link, links expire after 60 days. Closed testing is a real release track with opt-in testers, and it’s the only one that counts for the 12-tester, 14-day requirement.
Side by side
| Internal app sharing | Closed testing | |
|---|---|---|
| Purpose | Share a build fast with teammates or QA | Pre-launch test with real users |
| Version code | Doesn’t need to be new or unique | Must be unique and increasing |
| Signing | Any key (re-signed by Google for sharing) | Your upload key, Play App Signing |
| Review | No review step mentioned by Google | Can go through review |
| Who can install | Anyone with the link who enabled internal app sharing in Play | Opted-in testers on your lists |
| Limits | 100 users per link, link expires after 60 days | Email lists up to 2,000 each, or Google Groups |
| Counts for production access | No | Yes |
| Builds can move to other tracks | No | Yes, promote to production |
Facts are from Google’s help pages on internal app sharing and testing tracks.
When to use internal app sharing
- Sending a debug or experimental build to a designer or QA teammate.
- Reproducing a bug with a specific build quickly.
- Checking a build on a device that isn’t yours.
Testers must turn on internal app sharing in the Play Store app’s settings before they can download.
When to use closed testing
- Your official pre-launch test with 12+ testers for 14 days.
- Beta testing updates after launch.
And internal testing?
There’s also the internal testing track (up to 100 testers, builds available within minutes). It’s a real track, unlike internal app sharing, but it doesn’t count for the requirement either. See do internal testers count and internal vs closed vs open.
Frequently asked questions
Do internal app sharing links work for anyone?
Only for people who have enabled internal app sharing in the Play Store app settings, and each link allows up to 100 users.
Can I promote an internally shared build to production?
No. Google says shared builds can’t be included in testing or production track releases. Upload a proper release instead.
Which should I use for my designer?
Internal app sharing. It’s the fastest way to hand someone a specific build.
Sources and how we keep this accurate
- Play Console Help: Share app bundles and APKs internally
- Play Console Help: Set up an open, closed, or internal test
- Play Console Help: App testing requirements for new personal developer accounts
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. 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 freeKeep reading
Do Internal Testers Count Toward the 12 Closed Testers?
Internal vs Closed vs Open Testing on Google Play
Firebase App Distribution vs Google Play Testing Tracks
Google Play Closed Testing vs Apple TestFlight
Reddit Tester Swaps vs a Tester Exchange: Pros and Cons
AAB vs APK: What Google Play Needs and Why
Browse all compare, or see the quick answers, guides and comparisons.