How Long Does Google Play Production Access Take?
A realistic week-by-week timeline, the review time Google states and what to do while you wait.
Read the guide →
You pressed the button to send your app for review, and now you are refreshing Play Console. This guide explains what Google actually says about review time, the ranges developers report for new apps, updates and production access, what makes a review slower, and what to do while you wait.
Google does not promise a fixed time for app review. Its Play Console Help says updates are processed and published as soon as possible, and that review times can be up to seven days or longer in exceptional cases. In practice developers report hours to a couple of days for an update to an established app and a few days for a first app, with new accounts and sensitive apps at the slower end.
Review is also only one step. A new personal account still has to complete the closed test before it can apply for production, and that is the longest part of the wait. See how long production access takes.
These statements come from Google's publish your app page.
| Topic | What Google says |
|---|---|
| Updates | Updates are processed and published as soon as possible, but certain apps may be subject to extended reviews. |
| Certain accounts | Google takes more time to thoroughly review apps from certain developer accounts to help better protect users. |
| Length | This may result in review times of up to seven days or longer in exceptional cases. |
| First-time apps | The page gives no separate timeframe for a first app. |
| Sending changes | Changes are not automatically sent for review. |
| After approval | With managed publishing you control exactly when the changes are published. |
The production access application has its own timing. Google says that review usually takes seven days or less, and our guide to applying for production access covers it.
Google does not publish these, so treat them as rough ranges from developer reports and third-party guides such as this one, not as promises.
| What you submitted | Rough range reported | Notes |
|---|---|---|
| Update to an established app | A few hours to about two days | Smaller changes tend to move faster. How to update an app |
| First app on an established account | About 1 to 7 days | Google gives no official number |
| First app on a new personal account | Up to about 7 days, after the closed test | The 14-day test comes first. 14-day requirement |
| Sensitive category or a flagged app | 7 days or longer | Matches Google's “exceptional cases” wording |
| Production access application | Usually seven days or less per Google | Production access timeline |
Google does not list all factors. These are the ones Google itself mentions or that developers commonly link to longer reviews.
Google says you can fix the issue and resubmit, or submit an appeal. Read the reason carefully, correct what it names, and compare your store listing and declarations with what the app does. Reasons apps get rejected and how to fix them lists the common causes, and production access rejected covers that specific case.
| Stage | Typical time |
|---|---|
| Account verification | Varies. Verification guide |
| Build, upload and forms | A few hours to a day |
| Closed test (12 testers, 14 days) | At least 14 days |
| Production access review | Usually seven days or less per Google |
| App review and release | Hours to several days |
Plan on roughly three to four weeks from first upload to a live app, and start the closed test as soon as the app is stable. Need testers? Read how to get 12 testers or see the complete closed testing guide.
Not a fixed one. Google's publishing page says updates are processed and published as soon as possible, that certain apps may get extended reviews, and that review times for some accounts may be up to seven days or longer in exceptional cases.
Google says it takes more time to review apps from certain developer accounts. New accounts, sensitive categories and apps with many permissions or recent policy changes are common reasons, though Google does not publish the full list.
For an update the status reads that Google is reviewing your update. For an item it says the item is part of an update being reviewed.
No. Google says your changes are not automatically sent for review. You send them from the Publishing overview page.
Yes. With managed publishing, Google says that after approval you control exactly when the changes are published.
Google says you can fix the issue and resubmit, or submit an appeal.