Guide · Google Play requirement 2026

Google Play Testers: How to Get 12 Testers in 14 Days

Updated: 20 September 2026

Google Play testers explained: new developer accounts need 12 testers opted in for 14 straight days. The real ways to cover it, with pros and cons of each.

The exact requirement (and why it exists)

• Applies to personal accounts created after Nov 13, 2023. Organization accounts and older personal accounts can publish directly.
• The minimum dropped from 20 to 12 testers in December 2024 — if you see older sources mentioning 20, they're outdated.
• The 12 testers must keep the opt-in active for 14 straight days — installing on day one and uninstalling on day two doesn't count.
• It's an anti-spam measure: Google wants to prevent ghost apps published with zero real usage behind them.

Does your account actually need this?

Check this before organizing anything — it's the most common starting mistake:

You can check this yourself in Play Console: if creating a new release prompts you about mandatory closed testing, it applies to you. If it doesn't, skip this entirely — no need to organize testers you don't need.

The real options to get there

Can you get 12 testers for free, or is paying worth it?

You can, and for many projects it is the sensible route: your network and testing-swap communities cost no money. The real cost is elsewhere: your time chasing people, the risk of dropouts, and a dropout pushing the counter below 12. Paid services advertise prices from around $15–25 for a pack (figures published by them), and be wary of anyone promising "guaranteed approval": the decision is always Google's.

• Free fits if you have a community of 20 or more reliable people who will keep the opt-in for 14 days and actually use the app.
• Paid fits if your time is worth more than the cost, or if you want a measurable test (real sessions, not just installs) to answer the production form with data.
• Either way, build in a buffer (14–16 testers) and check real activity. How Google counts the 14 days.

2026 update: Google no longer settles for opt-in alone

Since 2026 Google also checks whether those 12 testers genuinely used the app during the test, not just whether they accepted the invite. Applications with testers who installed but barely opened the app can get rejected for insufficient engagement, even if the 12/14-day count is technically met. In practice, this means Google can look at signals like active session frequency and screen transitions across the full 14 days, not just day-one installs. That reinforces the point above: you need evidence of continuous real usage, not just an opt-in list.

How to avoid the most common mistake

The typical failure is getting 12 people to sign up on day one, then having half of them uninstall before day 14 — Google won't recognize the quota as met and you have to restart the count. The key isn't just recruiting 12 people, it's making sure they keep the opt-in active for the full 14 days. That's why whichever option you use should include active tracking of who's still installed, not just an initial email list.

More resources

• How Google counts the 14 days (dropouts and late joiners)
• Production access rejected: causes and fixes
• Production access form: how to answer
• Internal vs closed vs open testing: which one counts for production
• Google Play developer verification 2026 (Sept 30 deadline)
• Full Play Console quota checklist
• Google Play closed testing
• Comparison: marketplace vs DIY/community
• Pricing overview