Guide · Play Console

Google Play closed testing: 12 testers for 14 days, explained

If you created a Google Play developer account recently, you can't just push your first app to production. Google makes you run a closed test first — and the number that trips everyone up is 12 testers for 14 days. Here's exactly what that means, who it applies to, and the part most guides skip: why plenty of apps still get rejected after the two weeks are up.

The rule: before you can apply for production access, run a closed test with at least 12 testers who have been opted in for the last 14 days continuously.

Who it applies to: personal developer accounts created after 13 November 2023. Organization accounts and older personal accounts are exempt.

Who actually has to do this

This is a per-account rule, not a per-app policy for everyone. It only applies to personal developer accounts opened after 13 November 2023. If your account is registered as an organization (a legal business entity), or it's a personal account created before that date, you can publish straight to production without the closed-test gate. The requirement is a one-time unlock: once an account has earned production access through any qualifying app, you don't repeat the 14-day test for future updates to that same app — though each brand-new app on a gated account still needs its own qualifying closed test.

Where the numbers come from

When Google introduced the policy in late 2023 the threshold was 20 testers. On 11 December 2024 it was lowered to 12, after developers pushed back that 20 committed testers was hard for solo devs to find. The 14-day duration never changed. That's why you'll still see older tutorials and videos saying "20 testers" — the count is out of date, but everything else about how those guides describe the process still holds.

What "opted in for 14 days continuously" means

Three details matter here, and getting any of them wrong resets your clock:

Opted in, not just invited. A tester counts only after they open your opt-in link and accept. Sending twelve invitations does nothing until twelve people actually join.
Twelve unique Google accounts on real devices. Emulators, duplicate accounts and bot farms don't count and can flag your account for policy violations. Use real phones.
The window is continuous. The count Google checks is how many testers have been opted in for the last 14 days without a gap. Opting out drops someone from the count; a tester who leaves and rejoins doesn't carry their earlier days forward.

Uninstalling the app is not the same as opting out — a tester opts out only through the testing web link. So an uninstall doesn't formally break your count, but see the engagement section below for why silent uninstalls still hurt you.

How to set it up

Build and upload a signed App Bundle (.aab) to a closed testing track: Test and release → Testing → Closed testing in the Play Console.
Create a tester list — email addresses directly, or a Google Group you control — and add your 12+ people.
Finish the store listing and required policy sections so the release can be reviewed.
Submit the release. After Google approves it, share the opt-in link with your testers and have each one accept it.
Let the 14 days run with testers actively using the app, then apply for production from the dashboard.

Recruit a buffer above 12 — aim for 15 or more. If one or two people drift away or opt out mid-window, you don't want to slip under the line on day 13.

Why apps still get rejected after 14 days

This is the part that surprises people. Hitting "12 testers, 14 days" on paper doesn't guarantee approval, because Google also looks at engagement, not just installs. If twelve people install on day one and never open the app again, reviewers read that as testing that didn't really happen, and you get the dreaded "more testing required" reply. To avoid it:

Ask testers to actually open and use the app across the two weeks, not just install it once.
Ship two or three small updates during the window — fix a minor bug, tweak a screen. It signals you're using the test for its purpose.
When you apply, the production access questionnaire asks what feedback you got and what you changed. Give specific answers; "the app is fine, no issues" is a common trigger for rejection.

After you apply, Google reviews the submission and emails the account owner — usually within about 7 days, sometimes longer. If it comes back as insufficient, you keep testing and reapply.

The short version

12+ real testers, opted in and engaged, for 14 continuous days, then apply — with honest questionnaire answers and a couple of real updates along the way. Recruit extra, use real devices, and don't go silent for two weeks.

Policy details and the current tester count can change; before a launch, confirm the specifics on Google's official Play Console Help page for testing requirements.