How do you pass Google Play's 12-tester, 14-day rule?
Invite at least 12 testers to a closed test and make sure each one installs the app and keeps it for 14 continuous days; the clock starts only when the release is approved and twelve have opted in. The rule applies to personal Play accounts created after 13 November 2023. Enrolling as an organisation normally avoids it altogether.
The rule is Google's, it's enforced, and on a personal account it adds two weeks before you can go live. Understand how the clock works and you only have to run it once.
Who does the rule apply to?
It applies to personal Google Play developer accounts created after 13 November 2023. Until such an account has run a closed test with at least 12 testers for 14 continuous days, it cannot publish its first app.
If you've read older guidance saying 20 testers, that's out of date. Google reduced the number to 12 in December 2024.
Accounts registered as an organisation normally avoid it. Google's own documentation only states the rule for personal accounts and doesn't spell out the exemption in writing, so check your Play Console dashboard once you're in. It tells you plainly whether the requirement applies to your account.
Personal or organisation account: which should you choose?
Decide before you sign up at play.google.com/console/signup. The account type is difficult to change later, and it decides whether the rule applies to you.
| Personal account | Organisation account | |
|---|---|---|
| Closed test before the first app | Yes, 12 testers for 14 days, if created after 13 November 2023 | Normally not; your dashboard confirms |
| Needs a D-U-N-S number | No | Yes, the same one Apple asks for |
| Registration fee | $25 once | $25 once |
| Time the rule adds before launch | Two weeks at least | Normally none |
For a business, organisation is the better route. The one extra requirement is a D-U-N-S number, which Apple also asks for when you enrol as an Organization. If you've started your Apple enrolment, you have it; if not, allow up to 5 business days to receive one.
How do you run a closed test that counts?
If the rule does apply to you, it's survivable, just slow. Twelve people must install and keep the app for fourteen unbroken days. Three details decide whether those days count.
Testers must actually install the app
Accepting the invitation isn't enough on its own. Each tester must accept and install. Someone who was invited but never installed doesn't count towards the twelve.
The clock starts later than you think
The fourteen days only start once your release is approved and twelve testers have opted in. Uploading a build and sending invitations doesn't start the count; it begins when both of those are true.
Opting out resets the clock
If a tester opts out partway through, their clock resets, even if they rejoin later. If you started with exactly twelve, one person leaving in the second week pushes your launch back. Count on a couple of spares beyond the twelve.
Who can be a tester?
Staff, colleagues and friends all count. Each one needs a Google account and an Android phone they'll keep the app on for the full fourteen days. Collect twelve Gmail addresses early, plus your spares, so the test can start the day the release is approved.
Is this the same as internal testing?
No, and mixing them up costs time. Google Play also has an internal testing track, and it's unrelated to the 12-tester rule:
- Internal testing is instant, with no time requirement.
- It's for you and your team to use the real app before anyone else sees it.
- Google only lets in accounts listed in advance, so each tester sends their Gmail address first.
The step that trips people up with an internal-testing link: open it on the phone, signed in with the same Google account that's signed into the Play Store. A link opened in a browser signed into a personal account, on a phone signed into a work account, gives "item not found".
How much time does the rule add?
On a personal account, at least two weeks on top of everything else. The Android side of a launch then looks like this:
- Google approves the Play account, usually within a day or two.
- The closed-test release is approved and twelve testers opt in.
- Fourteen continuous days of testing.
- Google reviews the first public release. A brand-new account's first review can take several days while Google checks the account itself, so allow up to a week.
With an organisation account, steps 2 and 3 normally disappear. Even if you first need a D-U-N-S number, up to 5 business days is shorter than a fourteen-day test that can't start until a release is approved.
How our team handles it
We'll ask you to check your Play Console dashboard and tell us whether the 12-tester requirement applies. If it does, you collect the Gmail addresses; we set up the test track, send you the invite link and run it alongside internal testing. Releases are uploaded as drafts, and rolling them out stays your decision.
Key facts
- The rule applies to personal Google Play developer accounts created after 13 November 2023.
- Such an account needs a closed test with at least 12 testers for 14 continuous days before it can publish its first app.
- Google reduced the requirement from 20 testers to 12 in December 2024.
- The 14 days start only once the release is approved and 12 testers have opted in.
- A tester who opts out partway has their clock reset, even if they rejoin later.
- Organisation accounts normally avoid the rule but need a D-U-N-S number; the Play Console dashboard confirms whether it applies.
- A Google Play developer account costs $25 once, with no annual fee, and is usually approved within a day or two.
Our Google Play setup guide walks through signup, access and the service account step by step, and testing your app covers the internal track and what to check. We set up the test tracks and take your app through Google Play review as part of every order: $1,499 for iPhone + Android or $999 for one platform, paid once, with the first year of updates included. See pricing.