Skip to content

Requirements

Google Play 12 Testers, 14 Days Requirement: Full Guide

What Google's 12 testers for 14 days rule requires, who it applies to, what counts as a tester, and how to plan the test and apply for production access.

Sundar•Published November 21, 2026•Updated November 21, 2026
6 minestimated read
7guide sections
1references
Illustration of an Android QA workflow with a checklist, a bug under a magnifying glass, and launch steps
On this page · 9 sections
  1. 01Who the rule applies to
  2. 02What counts toward the 12 testers
  3. 03How to plan the dates
  4. 04Applying for production access
  5. 05Why Google asks for more testing
  6. 06Ways to find 12 testers
  7. 07Checklist before you press Apply
  8. 08Frequently asked questions
  9. 09Official sources
Open the free toolsCheck your closed test setup with the free tools before you change anything.

If your Google Play developer account is a personal account created after 13 November 2023, you can't publish an app to production straight away. You first need a closed test with at least 12 testers who have each been opted in continuously for the 14 days before you apply. Once that is true, the Apply for production button in the Play Console dashboard becomes available. You answer a short set of questions about the test, and Google reviews the application. Google says review usually takes seven days or less (Play Console Help 14151465).

The rest of this guide explains each part of that sentence: who the rule covers, what counts as a tester, how to plan the dates, and what the application asks.

Who the rule applies to

Google's help page covers personal developer accounts created after 13 November 2023 (Play Console Help 14151465). If your account was created before that date, or it is an organization account, the page doesn't describe a testing requirement for you.

Check this before you plan anything. Open the Play Console dashboard for your app: if the requirement applies to your account, it is listed there as a step before production.

What counts toward the 12 testers

Three conditions have to be true for a tester to count:

  • They are in your closed test. Internal testing is a separate track; Google recommends it as an optional first step, but the requirement is about your closed test.
  • They have opted in. Being on your email list or in your Google Group is not enough; the tester has to accept the invitation through the opt-in link.
  • They have stayed opted in for the last 14 days without a break. Google says testers who opt in, test for fewer than 14 days and then opt out don't count, and a tester who opts out and back in needs 14 consecutive days.
Illustration of a completed app launch checklist next to an Android phone and a finish-line flag
Turn testing findings into a short, prioritized launch checklist.

How to plan the dates

  1. Upload a build to the closed testing track and get the release reviewed and available. Testers can't install anything until it is.
  2. Add testers by email list or Google Group, and share the opt-in link with them.
  3. Write down the date each tester opts in. Your own record is the easiest way to see whose 14 days end when.
  4. Find the date your twelfth tester opted in and add 14 days. That is the earliest day you can apply.
  5. Keep everyone opted in until you have applied. A tester who leaves early can push the date back.
  6. If you need to ship fixes during the test, publish them to the same closed track so your testers get them.

A quick illustration with made-up dates: 14 testers opt in between 3 and 5 March, and the twelfth of them opts in on 5 March, so the earliest application date is 19 March. If two testers leave on 10 March, you still have 12 with unbroken streaks and the date holds. If a third leaves, you need a replacement, and the date moves to 14 days after that person opts in.

The free tester start-date calendar does this calculation for you from the opt-in dates you enter.

Applying for production access

When the requirement is met, open the dashboard and choose Apply for production. Google's form has three parts (Play Console Help 14151465):

  • About your closed test: how easy it was to recruit testers, how testers engaged with the app, and a summary of their feedback and how you collected it.
  • About your app or game: your target audience, what the app offers them, and an estimate of installs in the first year.
  • About your production readiness: what you changed because of the test, and how you decided the app is ready.

These answers are why the test is more than a waiting period. Keep tester feedback, the issues you found and the changes you shipped as you go, so you can describe the real test rather than writing from memory. The guide on writing production access answers goes through each question.

Why Google asks for more testing

Google names two reasons it may ask you to keep testing: fewer than 12 opted-in testers, or insufficient tester engagement during the testing period. Twelve names on a list who never open the app can meet the count and still fail the engagement part of the review.

If that happens, read the notice carefully, fix what it points to, and run the test again with testers who actually use the app. The guide on production access being denied covers what to change.

Ways to find 12 testers

Google suggests recruiting from your personal and professional networks and choosing people who match your target audience. In practice developers use one of three routes:

  • People you know: friends, colleagues, existing users or a community you belong to. Free, but keeping 12 people opted in for two weeks takes reminders.
  • A Google Group: create one, add it to the closed test, and share one join link. It makes adding and replacing testers easier. See [adding testers with a Google Group](/blog/google-group-testers-play-console-setup).
  • A managed service: someone else supplies and coordinates the testers. Our managed plans run 14 testers for 16 days per app, which leaves two spare testers and two spare days above Google's minimum. Google still decides production access; see the [guarantee](/guarantee) for what happens if it is denied.

Checklist before you press Apply

  • At least 12 testers are opted in to the closed test today.
  • The twelfth of them opted in at least 14 days ago, and none has opted out since.
  • The dashboard shows the testing step as complete.
  • You have notes on tester feedback, the issues found and the changes made.
  • Any login the reviewer needs is working, with test credentials provided in Play Console.

FAQ

Questions about this topic

Is it 12 testers or 20 testers?

Google's current help page (Play Console Help 14151465) says a minimum of 12 testers opted in continuously for at least 14 days. Go by that page if you find older advice with a different number.

Do internal testers count toward the 12?

No. The requirement is about testers opted in to your closed test. Internal testing is a useful first step for your own team, but it is a separate track.

Can I apply on day 14?

You can apply once at least 12 testers have each been opted in for the preceding 14 days. Count from the day your twelfth tester opted in, and check the dashboard before you apply.

Do testers have to open the app every day?

The rule counts opted-in testers, not daily opens. But Google reviews how testers engaged with the app, so real use during the test matters for the application.

Does meeting the requirement publish my app?

No. It lets you apply for production access. Google reviews the application, and after approval you still publish a production release, which goes through its own review.

Sources

Official references used

Continue

Choose the next step

Related

Next pages to read

Rather not recruit testers yourself?

Our managed closed test runs 14 testers for 16 days. Google requires 12 testers for 14 days (for personal Play developer accounts created after 13 November 2023; organization accounts are exempt); the extra 2 testers and 2 days are our buffer.