Google Play's 14-Day Closed Testing Rule, Explained

This page is about how the rule works. If what you actually want is to put 12+ real testers on your closed test, our 12 testers page covers the plans and pricing — everything below is the requirement itself, independent of who supplies the testers.

Google Play's closed testing requirement, for personal developer accounts created after November 13, 2023, is precise: at least 12 testers opted in, continuously, for 14 days. "Continuous" is the operative word, and it attaches to each tester rather than to your order as a whole: when you apply, you need at least 12 testers who have each been opted in continuously for the preceding 14 days. A tester who opts out and rejoins starts their 14 days over — their earlier stretch no longer counts — and a replacement begins their own period rather than inheriting anyone else's. Google does not publish what happens if your count dips below 12 mid-test and recovers before you apply, which is the honest answer and exactly why every plan ships a buffer above the minimum.

That single rule is why the count matters as much as the duration. 20 testers, 25 testers, or any number above 12 exists purely as a buffer against dropout, not because Google requires more than 12 — see our 12 testers page for how tester count and plan size relate.

Who this applies to: Google Play accounts registered as an individual (personal) developer, created on or after November 13, 2023. Organization accounts and personal accounts created before that date are not subject to this specific closed-testing gate — though Google can still apply its general testing requirements to any account. If you're not sure which category your account falls under, Play Console shows your account type under Setup → Developer account details.

"Opted in" has a specific meaning here: a tester has opened your closed test's shareable opt-in link and joined the test with an eligible Google account, not simply been added to the tester list. Google Play doesn't email testers an invitation on your behalf — you copy the opt-in link from Play Console and share it with your testers yourself (email, Slack, wherever they'll actually see it), and each person has to actively open it and join before they count toward the requirement. This is the single most common point of confusion, and the reason a fresh test can sit at "0 opted in" even with a full list saved.

Google reduced this bar from 20 testers to 12 in December 2024 — a real, permanent change, not a temporary promotion. If you're reading older forum posts or guides that reference 20 testers, they predate that change and describe a stricter requirement than currently applies.

This requirement is distinct from internal testing (which never counts toward it, regardless of tester count or duration) and from the engagement/feedback Google's production-access questionnaire asks about afterward. Clearing 12 opted-in testers for 14 continuous days is a hard, automatically-checked gate; what you did with that time — real usage, real feedback, real fixes — is a separate, human-reviewed judgment call once you apply.

Testers14 runs a 20-day cycle for every order: the 14 days Google actually checks, plus 6 bonus days at no extra charge. Google says production-access review typically takes a week or less, though it can occasionally take longer — the 6 bonus days provide extra coverage during that typical review window, on top of what Google requires.

Your day counter on your Testers14 dashboard reflects real calendar time from when your app was confirmed installed on testers' devices — not from checkout, and not from how many days we've logged activity for. If your count looks different from what Play Console shows, see our page on that specific mismatch.