Skip to content
webtoapkfree

How long does Google Play review take for a new app?

Google Play review time for a new app runs from a few hours to seven days, longer in exceptional cases. Plan at least a week before launch.

GuidesNookesh Karri

Light cover card with the title 'How long does Google Play review take for a new app?' in dark text and a green accent bar

Google Play review time for a new app is anywhere from a few hours to seven days, and Google says it can run longer in exceptional cases. New developer accounts are the ones most likely to sit at the long end. Google’s own advice is to leave at least a week between submitting and your planned launch date.

What Google says about review time

Google’s Play Console help page on controlling when changes are reviewed states that processing “can take a few hours or up to seven days (or longer in exceptional cases)”. The same page recommends a buffer period of at least a week between submitting your app and going live.

Google doesn’t publish an average. Its publishing page only says that for certain developer accounts it takes more time to review apps thoroughly, which can push reviews to seven days or more. There’s no queue position and no countdown in Play Console.

Why new apps and new accounts take longer

New developer accounts get extended review times because Google has no history with them yet. The help page on review control names “apps submitted by new developer accounts” as an example of apps subject to extended reviews.

A first app also carries more to check than a typical update. The listing, content rating, Data safety answers and permissions are all new. Google’s page on preparing a release says permission requests are evaluated during the release process, and some need a Permissions Declaration Form approved before you can publish. If your app asks for camera, location or SMS access, expect that part to slow things down.

The full timeline for a new personal account

For a personal account opened after November 13, 2023, the app review is the last wait, not the only one. Google’s testing requirements page asks for a closed test with at least 12 testers opted in for 14 days in a row before you can apply for production access.

Here is the order the waits come in:

Stage Who controls the clock Typical length
First internal test release Google reviews it A few hours to seven days
Closed test with 12+ testers You and your testers 14 days in a row, minimum
Production access application Google reviews your answers Hours to a few days (see below)
Production release review Google A few hours to seven days, sometimes longer

On the production access step, one app-conversion vendor tracked its own customers’ applications: across 27 apps, the median was 31.3 hours and 90% were approved within 93.8 hours. That vendor also says it has no reliable measured average for the app review itself, which matches Google’s silence.

Organisation accounts aren’t covered by the closed test rule. They go straight to the production review, so their first launch is mostly that one wait.

The Play Console steps that quietly add days

Two Play Console details stretch review time more often than Google does.

  1. Saving isn’t submitting. Since a January 2023 change, edits land in the Publishing overview and wait there. Google’s help page says items “are not sent for review until you click Send for review”. A saved change can sit there for days without a review ever starting.
  2. New changes reset your place. The review turnaround is counted from the last submitted change. Google warns that sending more changes while one is in review may push your app to the back of the queue.

My take: gather every fix, the listing text, screenshots and the Data safety form first, then send it all for review once. Don’t tweak the description while the app shows In review.

Reading the status in Play Console

Play Console shows review progress in the Publishing overview, grouped into three sections. Each one tells you where the review timer stands:

  • Changes not yet sent for review holds anything saved but not submitted. The clock hasn’t started.
  • Once Google has it, the item moves to Changes in review and your app’s status reads In review.
  • Approved changes wait for you under Changes ready to publish (only with managed publishing on).

Managed publishing can’t be used for a first launch, so a new app goes live once it’s approved. For later updates you can switch it on and pick your release moment. After you click publish, the update goes live within a few minutes.

If the review fails, the status changes to Update rejected, or App rejected for an app still in Draft. The next submission must pass review before anything goes out.

What to do if your app is stuck in review

If an app has been in review past seven days, check Play Console first, then ask for help. Google’s publishing page notes you can request help from the Help page inside your Play Console account.

Before you write in, check your inbox and the Policy status page for a request you missed. Missing test login details and unanswered declaration forms are common blockers. Don’t resubmit just to “nudge” it: a new submission counts as the last change and can send the app back in the queue.

Where a WebView app fits in

Wrapped websites go through the same review as any other app. They also face extra scrutiny under the minimum functionality policy, and a rejection there restarts the whole wait. Read the 12 testers rule before planning dates, and what to do if production access is refused.

webtoapkfree.com builds a signed APK to test on your phone and an AAB to upload to Play Console, for free and without an account. A generated AAB is not Google Play approval: the developer account, listing, testing and policy compliance stay your job, and the review time is entirely Google’s. The Play publishing guide walks through the submission itself, and this guide to Data safety for WebView apps covers one form that often holds a review up.

The limit: nothing on your side makes Google faster. A clean first submission only saves you a second wait.

FAQ

Is there a way to speed up a Google Play review?

Google’s Play Console help pages don’t offer one. The practical moves are to send everything for review in one go, avoid new changes while the app is in review, and answer policy forms fully the first time.

Why is my first app taking longer than my friend’s update?

Google says extended review times apply to apps such as those from new developer accounts. An established account pushing an update usually has a track record the review can lean on.

Does the internal testing track skip review?

Not the first time. Google reviews the first release you roll out to an internal test track. Later internal test updates aren’t reviewed up front, though they can be reviewed after they go live.

Does the 14-day closed test count as review time?

No. For personal accounts created after November 13, 2023, the closed test and the production access application come before the production review, so they add to the wait.

Sources