Google Play

What is Google Play’s 12-tester rule?

Last updated 9 October 2026

Search this and you get a page of companies selling you testers. Here is what Google’s own documentation says, quoted, with the one thing those pages assert that Google has never published.

The rule, in Google’s words

Three conditions, all of which have to hold at once:

• Twelve testers, as a minimum, not a target.
• Fourteen continuous days opted in. Google states that testers who opt in, test for fewer than 14 days and then opt out do not count.
• A personal account created after 13 November 2023. This is the condition most often missed, and it is the one that most often means the rule does not apply to you at all.

It does not apply to organisation accounts

Google’s requirement is scoped, by its own title and wording, to personal accounts. If you are a company publishing under an organisation account, this is not your problem — your equivalent hurdle is a D-U-N-S number, which Google notes is free to obtain and which third parties will nonetheless try to charge you for.

If you are a UK limited company about to create a personal account because it is quicker, that choice is what buys you the 14-day wait. Worth knowing before, rather than after.

It used to be twenty

Both dates come from Google’s own announcement on the Android Developers Blog, the second as a dated update to the first: “starting today, we’re requiring 12 instead of 20 testers for personal developer accounts.” Any page still telling you 20 is two years behind.

After the fourteen days

Completing the test does not publish anything. You then apply for production access in Play Console, answering three sections — about your closed test, about your app, and about your production readiness. Google states that this review “usually takes seven days or less, but can occasionally take longer”.

So the realistic floor between “ready” and “live” on a new personal account is about three weeks, not fourteen days. Plan the launch from that number.

If the application is refused, Google’s stated remedy is to keep testing — it notes that more testing may be required where there were fewer than 12 opted-in testers or where engagement was insufficient.

What Google does not publish

This is the part the vendor pages fill in with confident specifics, and it is worth being careful about:

• No reset rule. You will read that dropping to 11 testers for a single day restarts the 14-day clock. Google’s page does not say this. It says short-stint testers do not count — which is a different claim. Treat the reset as folklore until Google writes it down.
• No last-updated date on the help article itself, in any locale. So “current as of” here means the date it was read, not a date Google asserts.
• No review statistics. Google publishes nothing equivalent to Apple’s percentile review times, no Play rejection rate and no figure for how many production-access applications fail. Any percentage you see for these is invented.

The two fees, side by side

These get muddled constantly, usually in the direction of assuming Google’s is annual too. It is not.

Sources. The requirement, production access and the seven-day review window: Google Play Console Help, app testing requirements for new personal developer accounts, retrieved 9 October 2026; Google publishes no last-updated date on that article. The 20-to-12 change and both dates: Android Developers Blog, 9 November 2023, with its 11 December 2024 update. Registration fee and account types: Google Play Console Help, retrieved 9 October 2026. Apple’s fee: Apple Developer Program enrolment pages, retrieved the same day.