Play Console closed testing calculator
Google Play asks new personal developer accounts for a closed test with at least 12 testers opted in for at least 14 days continuously before production access. This calculator finds the earliest day to apply from your start date and daily tester counts, and lists what the application asks.
Updated
Earliest day to apply for production
17 Nov 2026
5 more days to hold at 12 or more testers. Streak began 3 Nov 2026.
- Pass · 12 or more testers opted in today12 opted in
- Fail · 14 continuous days at that level9 of 14 days
Production-access application checklist
PRODUCTION ACCESS CHECKLIST (Google Play, new personal developer accounts) Before you apply [ ] Closed test live with at least 12 testers opted in [ ] 14 continuous days passed (earliest: 17 Nov 2026) [ ] Testers actually used the app, not just installed it [ ] Feedback collected from testers (form, chat, email) and kept Application part 1: about your closed test [ ] How easy it was to recruit testers [ ] Whether testers used all available features [ ] Whether tester usage matched expected production behaviour, and differences you saw [ ] Summary of tester feedback and how you collected it Application part 2: about your app [ ] Target audience, as specific as you can be [ ] How the app gives users value [ ] Estimated install range for the first year Application part 3: production readiness [ ] Changes you made from what the closed test taught you [ ] How you decided the app is ready for production Source: Google Play Console Help, checked 2026-11-11
- Test started
- 1 Nov 2026
- Days since start (today counted)
- 11
- Testers opted in today
- 12
- Current continuous streak
- 9 days from 3 Nov 2026
- Buffer suggested
- 19 Nov 2026Two days later than the earliest day, in case a tester left late or the Dashboard count lags. Our margin, not Google's.
- Google says the 12 testers must stay opted in for the 14 days. A tester who opts out and back in restarts that tester's count, so recruit a few more than 12.
- Day counting is our convention: day 1 is the first day with 12 or more testers, and the first day you can apply is 14 days after it. Google does not say how it counts the first day; the Dashboard shows when the Apply for production button turns on, and that is the authority.
- Some days sit exactly at 12. One tester leaving drops you below the bar and restarts the clock. Add three or four spare testers.
Code Audit: from ₹90,000 / $950
Stuck on testers or a rejected application? A code audit before launch covers crashes, permissions and policy checks.
How is the earliest production date worked out?
Google Play Console Help says a new personal developer account must run a closed test with at least 12 testers opted in for at least 14 days continuously before it can apply for production access. Google's page applies this to personal accounts created after 13 November 2023; this calculator treats other accounts as not covered and says so.
You enter the test start date and how many testers were opted in on each day. The calculator finds the run of days that ends today where the count never dropped below 12. Day 1 of that run plus 14 days is the first day you can apply. If the count dropped below 12 at any point, the run restarts at the first day you were back at 12.
The tester count is read from your own entries, so the result is only as good as the numbers you copy from Play Console. Google decides eligibility itself, and the Apply for production button in the Dashboard is the final signal.
streak day 1 = first day with >= 12 testers, unbroken to today earliest apply date = streak day 1 + 14 days any day below 12 testers restarts the streak
What does Google ask when you apply for production?
| Part | What Google asks | What to have ready |
|---|---|---|
| 1. About your closed test | How easy testers were to recruit; whether they used all features; whether usage matched real production use; summary of feedback and how you collected it | A feedback log with dates, and notes on what testers did not touch |
| 2. About your app | Target audience; how the app gives users value; estimated installs in the first year | A one-paragraph audience description and an honest install range |
| 3. Production readiness | Changes you made from closed-test learnings; how you decided the app is ready | A list of fixes shipped during the test and your release checks |
How to work out your Play production access date
- 1Pick the account typeChoose personal and created after 13 November 2023 if that is you. Other account types show as not covered by this rule.
- 2Enter the start dateUse the day your closed test was live and testers could opt in, as YYYY-MM-DD.
- 3List the daily tester countsRead the opted-in tester count in Play Console each day and type the numbers in order from the start date, separated by commas.
- 4Read the date and the checklistThe headline shows the first day to apply. Copy the checklist and draft your answers to the three application sections while you wait.
Frequently asked questions
How many testers and days does Google Play require for a closed test?
Which Google Play developer accounts need the closed test before production?
What happens if a tester leaves the closed test partway through?
Where do I apply for production access in Play Console?
Can testers just install the app, or must they use it?
Sources
- Google Play Console Help, closed testing requirement and Apply for production (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter