How Long Does Google Play Closed Testing Take?
A Google Play closed test takes at least 14 days, because 12 testers must stay opted in continuously for the 14 days before you apply. Google also says a test release can take a few hours to seven days to process, and production access review usually takes seven days or less. Added up, plan for two to five weeks.
The 14 days get most of the attention, but they are only the middle of the process. Before them, your test release has to be processed and your opt-in link has to start working. After them, Google reviews your production access application, and then your first production release. This guide adds up every stage using only the times Google publishes in its Play Console Help Center, and says clearly where Google gives no number.
The times here come from Google's articles App testing requirements for new personal developer accounts, Set up an open, closed, or internal test, Control when app changes are reviewed and published and Publish your app.
What does the timeline look like day by day?
| When | What happens | Time Google states |
|---|---|---|
| Before day 1 | You complete your app setup, create the closed test and send the release for review. | Processing can take a few hours or up to seven days, or longer in exceptional cases. |
| Before day 1 | The test is published for the first time and the opt-in link becomes available. | The test link can take several hours to become available to testers. |
| Day 1 | The 12th tester you will count opts in with your link. | Each tester opts in using the link; no time is given. |
| Days 1–14 | All 12 stay opted in, use the app and send feedback. Updates reach them on the test track. | Once testers install your app, it updates to the test version within a few minutes. |
| Day 15 | 14 full days have passed since day 1. You can apply for production access from the Dashboard. | At least 12 testers opted in continuously for the preceding 14 days. |
| After you apply | Google reviews the application and emails the account owner. | Usually seven days or less, but can occasionally take longer. |
| After approval | Your first production release is reviewed and published. | For certain developer accounts, up to seven days or longer in exceptional cases. |
Day 1 here is the day the last of your 12 counted testers opted in, not the day you sent out invitations. To find your own day 15, use our closed test date calculator.
What happens before day 1?
Google says you can start a closed test after completing your app setup. Your release then goes through processing, which Google says can take a few hours or up to seven days, or longer in exceptional cases, depending on the review time your app is subject to. Google also recommends planning a buffer of at least a week between submitting your app and going live.
The opt-in link only appears when the app's status is Published, and after the first publication the test link can take several hours to become available to testers. Testers need a Google Account or a Google Workspace account, and for a closed test that uses a Google Group, they must join the group before they can opt in. If the link does not work yet, our guide to an opt-in link that is not working covers each cause, and the closed testing setup guide covers the steps.
When do the 14 days start and end?
Each tester has their own 14 days. Google's rule is that at least 12 testers must be opted in when you apply, and they must have been opted in continuously for the preceding 14 days. So the date that decides your timeline is the day the last of your 12 counted testers opted in.
A tester who leaves resets their own count: Google says that testers who opt in, test for fewer than 14 days and then opt out do not count, and that if a tester opts out and opts back in later, the 14 days must be consecutive. Google does not publish an exact cut-off time or time zone, so counting 14 full days from the opt-in date, as this guide does, is the conservative way. Our guide to 12 testers for 14 days explains the rule in full.
How long does production access review take?
After you submit your application, Google reviews it and sends an email notification to the account owner when the review completes. Google says review usually takes seven days or less, but can occasionally take longer.
If your app needs more testing, Google says you may need to continue running your closed test, and it names two reasons: fewer than 12 opted-in testers, or insufficient tester engagement during the testing period. Google does not say how long the extra testing must last, so that time is not in the table above. Our guide to applying for production access walks through the form.
How long until the app is live after approval?
When the application is approved, you get access to your app's Production page and can distribute your app on Google Play. Your production release still has to be reviewed. Google's Publish your app article says that for certain developer accounts it takes more time to review apps thoroughly, which may result in review times of up to seven days or longer in exceptional cases.
How long does it take in total?
Google does not publish a total, so this is our arithmetic from its figures, not a Google number. At the fast end, a release processed in a few hours, 12 testers opted in the same day and a quick review give you a little over two weeks. At the slow end, seven days of processing, 14 days of testing, seven days of production access review and seven days of production review add up to about five weeks. Exceptional cases can take longer than both.
How can you avoid adding days?
- Send the test release early. Processing can take up to seven days, so start it before you recruit testers.
- Avoid extra changes while in review. Google says review turnaround is counted from the last submitted change, so a new change can push your app to the back of the review queue.
- Tell testers to stay in. Google advises you to inform testers that they need to remain opted in continuously for at least 14 days.
- Count opt-ins, not invitations. Only testers who opted in count, and our closed testing tracker template keeps the dates in one place.
- Write your answers during the test. Google says you must summarize your testing feedback when you apply.
Frequently asked questions
How long does Google Play closed testing take?
The test itself takes at least 14 days, because at least 12 testers must have been opted in continuously for the 14 days before you apply. Release review before the test and production access review after it add time: Google gives a few hours to seven days for processing and usually seven days or less for the production access review.
Can I apply for production access before the 14 days are over?
No. Google says at least 12 testers must be opted in to your closed test when you apply, and they must have been opted in continuously for the preceding 14 days.
How long does Google take to review a production access application?
Google says review usually takes seven days or less, but can occasionally take longer. When the review is complete, Google sends an email notification to the account owner.
Does the 14-day clock restart if a tester leaves?
For that tester, yes. Google says that if a tester opts out and opts back in later, the 14 days must be consecutive to count, so you need 12 testers who each have an unbroken 14 days.