How long does Google Play review take?

Google does not publish an average. It publishes an upper bound, twice, in the same words: "review times of up to seven days or longer in exceptional cases."

That figure appears in two contexts, and neither of them is a promise about your submission.

Anyone quoting you "usually a few hours" or "typically 3 days" is reporting their own experience or repeating someone else's. Those numbers are not published, cannot be checked, and change with Google's own capacity and with what your app does.

What Google actually publishes

Two sentences, both from the Play Console help page on publishing your app.

On account-level scrutiny:

"For certain developer accounts, we'll take more time to thoroughly review your app to help better protect users. This may result in review times of up to seven days or longer in exceptional cases."

On standard publishing:

"Updates to existing apps are processed and published as soon as possible. By default, your app will use standard publishing. Certain apps may be subject to extended reviews, which may result in review times of up to 7 days or longer in exceptional cases."

Read what those two say together. "As soon as possible" is the normal case with no number attached. Seven days plus is the documented exception, and there are two ways to land in it: something about your account, or something about your app.

Google does not say which accounts, or which apps, or how it decides. That is the honest state of it.

Why new developer accounts are slower

Google names the mechanism but not the criteria. "For certain developer accounts" is doing the work in that sentence, and the widely reported pattern is that newer accounts sit in that group.

Two things are documented and worth separating from folklore.

Extra review time is an account property, not a punishment. It attaches to the account, so your first few submissions can each take longer than an established developer's would, on identical code.

A new personal account has a separate gate before production, and it is not review time at all. This is the part that produces "my app has been in review for three weeks" posts that turn out not to be about review.

The closed testing gate, which is not review

If your Play developer account is a personal account created after 13 November 2023, you cannot publish to production until you have run a closed test. Google's wording:

"Google Play requires personal developer accounts created after November 13, 2023, to test their apps before those apps are eligible for distribution on Google Play. Certain features in Play Console, such as Production (Test and release > Production) and Pre-registration (Test and release > Testing > Pre-registration), remain disabled until developers meet these testing requirements."

The requirement itself:

"Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."

Then you apply, and the application has its own review with its own published figure:

"After you submit your application for production access, Google reviews your submission. When the review completes, an email notification is sent to the account owner. Review usually takes seven days or less, but can occasionally take longer."

So a first release from a new personal account can involve three separate waits: 14 days of closed testing, up to about a week for the production access application, and then app review on the release itself. None of those is the others, and only the last one is what people mean by "review".

Organisation accounts are not subject to the testing requirement. Account type is not trivially changed later, which is worth knowing before you sign up rather than after.

What is not review time

Before assuming Google is slow, rule these out.

Changes you never submitted. Play Console's status "Changes not yet sent for review" means exactly what it says, and Google spells out the consequence: "Your changes are not automatically sent for review." Check the Publishing overview page.

Managed publishing. If it is on, an approved change waits for you to publish it. Google's description: "Updates to existing apps are processed as usual. After it's approved, you control exactly when the changes are published." An approved release sitting there looks identical to one still in review if you are only reading the app status.

Staged rollout. A release at inProgress and 10% is live, not pending. Nobody finished raising the fraction.

Internal testing. No meaningful wait: "Builds are normally available to testers within seconds of being added in Play Console." If your internal track is instant and your production track is not, that is the review difference, not a broken upload.

App content declarations. Incomplete Data safety, target audience or content rating answers can block a submission from going anywhere.

What plausibly makes yours slower

Google does not publish the list, so treat this as the shape of the thing rather than a rulebook. The categories that attract extended review are the ones with their own policy pages: health data, financial services, apps aimed at children, VPNs, and anything requesting sensitive permissions such as QUERY_ALL_PACKAGES, SMS or accessibility services.

First submissions of a new app are slower than updates to an established one, which is consistent with Google contrasting "updates to existing apps" with everything else.

What does not speed it up

There is no expedite request on Play. Google publishes no equivalent of Apple's expedited review form. If you have found a link claiming to be one, check what it actually submits.

Resubmitting. A new bundle is a new submission, not a nudge.

Emailing support. The Help page in Play Console can raise a request, and it is the right channel for something genuinely stuck. It is not a queue jump, and Google's own guidance is blunt about the adjacent behaviour: "review is not a troubleshooting step."

Uploading to more tracks. Internal testing being instant does not pull production forward.

Planning around it, since you cannot shorten it

The move that works is the same one that works on the App Store: get approved early, then control the date yourself.

1. Turn on managed publishing. Submit well ahead of your date.
2. Let it be approved and sit there.
3. Publish when you are ready.

That converts an undocumented wait into a decision. For a first release from a new personal account, add the closed test and the production access application to the front of the plan, because together they are a bigger number than review is.

FAQ

How long does Google Play review actually take? Google publishes no average. The only published figure is "up to seven days or longer in exceptional cases", which describes extended reviews and certain accounts, not the normal case.

Why is my first app taking so much longer than my updates? New accounts and first submissions both attract more scrutiny, and Google states that some accounts get more review time deliberately. Updates to an existing app are processed "as soon as possible" by comparison.

Is the 12 testers, 14 days requirement part of review? No. It is a gate that sits before you can apply for production access at all, and it applies to personal accounts created after 13 November 2023.

My app has been in review for over a week. Is something wrong? Not necessarily, since Google's own wording allows for longer than seven days. Before contacting anyone, confirm the changes were actually sent for review, managed publishing is not holding them, and every app content declaration is complete.

Does review time differ by track? Internal testing is effectively immediate. Closed, open and production releases go through review, and production attracts the most.

AppSubmit records when each Play release was submitted and when its status changed, which is the only honest way to know your own typical wait rather than the internet's. Play Console shows the same statuses on the Publishing overview page.