How to Apply for Production Access on Google Play
Where to click, what the three questionnaire parts ask and how to write answers that show a real closed test.
Read the guide →Google Play Closed Testing Requirements 2026
Quick answer The 2026 closed testing requirements for new personal accounts are simple: at least 12 testers opted in for 14 continuous days, then an application for production access.
If you have a new personal Google Play developer account, you cannot publish to production until your closed test meets Google's requirements. The rules are simple but easy to get wrong. This checklist puts every requirement in one place so you can check each one before you apply.
Who needs a closed test in 2026?
Google requires personal developer accounts created after November 13, 2023 to test their app with a closed test before applying for production access. Until the requirements are met, the Production and Pre-registration options stay disabled. The official wording is on Google's Play Console Help page.
What are the closed testing requirements?
- A closed testing track with a releaseCreate the closed test and roll out a release so testers can install. See how to add testers.
- At least 12 testers opted inPeople must open your opt-in link and join. Being on the list is not enough. See how to get 12 testers.
- 14 continuous daysTesters must stay opted in for 14 days in a row. Those who leave early do not count, and rejoining must keep the days consecutive.
- Real use of the appThe questionnaire asks whether testers used all features and whether their usage looked like production use.
- Apply for productionClick Apply for production on the Dashboard and complete the three-part questionnaire. See the step-by-step guide.
- Wait for reviewGoogle says review usually takes seven days or less.
Where developers go wrong
- Counting list members as testers, when only opted-in testers count. See why testers do not count.
- Starting with exactly 12, then losing one tester and breaking the count.
- Skipping real use and feedback, which makes the questionnaire hard to answer honestly.
- Applying before 14 full days have passed.
What should you do after the 14 days?
Apply for production access from your Dashboard. If the application is not approved, do not panic: read what to do when production access is rejected. Not sure which track you need? Compare internal and closed testing and closed and open testing.
A simple 21-day plan
Use this plan to stay on track. It follows the closed testing steps in the order they happen, and the extra week gives you a safety buffer.
- Before day 1: create the closed track, upload your build, choose countries, add your tester list and save. Wait until the release is available, because the opt-in link can take several hours to work after the first publication.
- Day 1 to 2: send the opt-in link and confirm that each tester has joined and installed the app.
- Day 3 to 13: ask testers to open the app regularly, try different features and report anything confusing. Collect their feedback in one document.
- Day 7: check your opted-in count. Replace anyone who has left.
- Day 14: confirm that at least 12 testers have been opted in for 14 days in a row.
- Day 15 onward: apply for production access. Keep the test running until you get a decision.
What the questionnaire will ask
When you apply, Google asks about the closed test, your app and your production readiness. Keep notes during the test, so the answers are easy to write. You will be asked how easy it was to recruit testers, whether testers used all features, what feedback you got and what you changed. Our step-by-step application guide covers every question.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Plan your test around the rules
| Requirement | What to plan |
|---|---|
| At least 12 testers | Recruit 15 to 20. See the 12 vs 20 testers guide |
| 14 continuous days | Send reminders on days 3, 7, 10 and 13. See what to do if testers leave |
| Testers opted in | Collect confirmations. See how to share the link |
| Production access questionnaire | Keep notes during the test. See how to apply |
| Review time | Plan for about a week. See how long it takes |
Pitfalls that reset your progress
- Letting the closed track be paused or the release be removed.
- Replacing the tester list with a partial CSV. See email list vs Google Group.
- Testers using the wrong account. See why testers are not counting.
- Applying before the count is truly 12 for 14 days.
Frequently asked questions
Which accounts need the closed test?
Personal Google Play developer accounts created after November 13, 2023.
How many testers do I need?
At least 12 testers who stay opted in continuously for 14 days.
What stays locked until I meet the requirement?
Google says the Production and Pre-registration options stay disabled until the closed testing requirements are met.
How long does Google take to review my application?
Google says the review usually takes seven days or less, but it can occasionally take longer.
