Back to guides

Google Play closed testing requirements (2026)

8 min readUpdated 2026-09

Closed testing is the invite-only track new Google Play developer accounts have to pass before they can apply for production access. The requirements themselves are short — the difficulty is in the details. This is the exact checklist we run through with publishers before a single tester opts in.

Who has to run closed testing

  • Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers before applying for production access
  • Those testers have to stay opted in for 14 consecutive days
  • Play Console shows your account's exact number — some accounts are asked for 20 testers instead of 12
  • Organization (business) accounts are generally not subject to the 12-tester requirement, but this is granted per account, so confirm in your own Play Console
  • The requirement applies to your first production release, not to every update afterwards

Before you start

  • Your app is uploaded to Play Console as an app bundle and available on the Closed testing track
  • You have a Google Group (or email list) that testers can join — Google requires one for closed testing
  • Your testing link works in an incognito browser without developer-only permissions
  • The build is in a usable state: testers must be able to install it and open it without crashing

The test itself

  • At least 12 testers opt in and install the app (Play Console shows your exact requirement)
  • They stay opted in and keep the app installed for 14 consecutive days
  • Testers actually open the app — installs without usage look suspicious and can be rejected
  • Collect feedback during the cycle so you can submit a credible production access application

The 14-day window

  • The 14 days must be consecutive — a gap means the window restarts
  • Every single day needs the minimum number of opted-in testers, not just day 1 and day 14
  • One opt-out on day 13 can put you back to day one, so recruit 15 testers for a 12-tester requirement
  • Do not apply for production access early; the application has to come after the window is complete

Common reasons the requirement does not count

  • Testers opt out before 14 days are up
  • The app was installed but never opened, or opened only once
  • Testers use emulators, cloned apps or the same device fingerprint
  • You apply for production access before the 14 days are complete

How long closed testing takes end to end

Plan for roughly three weeks from submission to production release: a day or two for the first release review, 14 continuous days of testing, then the production access review.

Add buffer days to the test itself. A one-day slip at the end of a 14-day window is painful, which is why our campaigns run 16 days — 14 days of required activity plus two days of cover.

After the 14 days

Once the 14 days are complete you can apply for production access from Play Console. Google typically reviews applications within a few days. After approval you create a production release and complete one final review.

Have your testing notes ready before you apply: Google asks what you tested and what you changed as a result. Publishers who ran the test through us attach the activity report we provide.

Does the 12 tester rule still apply in 2026?

Yes. Personal developer accounts created after 13 November 2023 still need at least 12 testers opted in for 14 consecutive days before production access. Check Play Console for your exact number — some accounts are shown 20.

Do organization accounts need 12 testers?

Organization (business) accounts are generally exempt from the 12-tester closed testing requirement, but Google decides this per account. Confirm the message in your own Play Console before you plan a testing cycle.

Can I use the internal testing track instead?

No. Internal testing does not satisfy the requirement — the test has to run on the closed testing track with real testers opted in for 14 consecutive days.

How long does Google Play closed testing take?

At least 14 consecutive days of testing, plus the production access review. In practice most apps need about three weeks from first submission to a live production release.

Do I need my own testers to start closed testing?

You need at least 12 testers who opt in for 14 days. Recruit them yourself, swap with other developers, or hand the whole cycle to a managed service — BetaReward runs it with its own vetted global testers on real devices, with daily activity checks and buffer testers included.

Does closed testing cost anything?

Google does not charge for closed testing. The real cost is getting genuine testers and keeping them active for the whole period, whether you pay that in your own time or pay a service to run it.

What if a tester uses an emulator or a cloned app?

Emulator and cloned-app activity is not real testing and can make your whole test look artificial. Testers should use real Android devices with real Google accounts, which is how our own tester team operates.

Managed closed testing · $10 all-inclusive

15 real testers, 14 days active + 2 buffer days, test report before day 10.

Publish a task
Google Play Closed Testing Requirements 2026: 12 Testers, 14 Days, Production Access