How Long Does Google Play Review Take in 2026? Timelines, Delays and Managed Publishing
How long does Google Play review take in 2026?
Often a few hours, sometimes a few days, and up to seven days or longer in exceptional cases. That range comes from Google's own Play Console Help, which says processing "can take a few hours or up to seven days" depending on the review time your app is subject to. Some accounts, including new developer accounts, get extended reviews. Google's own tip is to plan a buffer of at least a week between submitting and going live, and that is the rule I plan around for every Flutter release.
Below: which changes are reviewed, what the statuses mean, the one mistake that pushes you to the back of the queue, and how I use managed publishing so a release goes live on the day I choose, not the day review happens to finish.
What gets reviewed, and what doesn't
Most changes that users can see go through review. A few take effect without one.
| Change | Reviewed? | Notes |
|---|---|---|
| New production or testing release | Yes | The usual case: a new app bundle on any track except internal testing |
| Store listing text, graphics, custom listings | Yes | Screenshots and descriptions count as changes |
| App content (content rating, target audience, Data safety) | Yes | Often forgotten when you add an SDK |
| Internal testing release | Usually not | Available right away, but the first release of a new app and the release after a rejection are reviewed |
| Raising a staged rollout to 100% | No extra review | Also not held back by managed publishing |
| Price changes, in-app products | Not held by managed publishing | Applied without waiting for your Publish click |
The Data safety row catches indie developers most often. If you add an analytics or ads SDK, update the form in the same submission; my Data safety refresh routine for new SDKs covers what to change.
What the Publishing overview statuses mean
Play Console shows an update status for your latest set of changes. These are the ones you will see while waiting.
| Status | What it means | What to do |
|---|---|---|
| Changes not yet sent for review | Your edits are saved but Google hasn't seen them | Click Send for review. Changes are not sent automatically |
| In review | Google is reviewing your update | Wait, and don't add more changes unless you must |
| Changes ready to publish (managed publishing only) | Approved and held until you publish | Publish when you are ready |
| Update rejected | A change doesn't meet policy | Fix it and resubmit, or appeal |
| App rejected | Same, for an app's first publish | Fix it and resubmit, or appeal |
One trap: after a rejection, your fixes are not sent for review automatically. You have to open Publishing overview and click Send for review yourself.
The mistake that makes review take longer
Google counts review turnaround from the last change you submitted. Its Help page says that if you submit a change while other changes are in review, your app may be pushed to the back of the review queue.
In practice, that means a second "small fix" sent on day three can reset the wait. I keep a simple rule: once something is in review, new work waits on a branch. If a fix is genuinely urgent, I send it once, knowingly, and plan for the longer wait.
- Batch store listing edits with the release they belong to, not one by one.
- Finish App content forms before you upload the bundle, not while it is in review.
- Use "Save for later" on Publishing overview for changes that aren't ready, so they don't go out with the release.
Managed publishing: approve now, go live later
Managed publishing separates review from release. Google reviews your changes as usual, but once approved they wait under "Changes ready to publish" until you click Publish changes. Google says the update then goes live within a few minutes.
- Open Play Console, then Publishing overview.
- In "Managed publishing status", turn on managed publishing and save.
- Upload and submit your release and listing changes as normal.
- Wait until "Changes in review" is empty and everything is under "Changes ready to publish".
- Click Publish changes on the day you chose.
Two limits are worth knowing. Managed publishing isn't available for an app's very first publish, and it doesn't cover internal testing. You can turn it on or off at any time, even while a change is in review.
A release calendar with a one-week buffer
This is the plan I use when a release has a date attached, such as a holiday feature or a store listing change for a sale.
| Day | Step |
|---|---|
| Go-live minus 10 | Freeze features. Run the release checklist and build the app bundle |
| Go-live minus 9 | Upload to internal testing and smoke-test on real devices |
| Go-live minus 8 | Turn on managed publishing; submit the production release, listing and App content changes together |
| Go-live minus 7 to minus 1 | Wait. No new submissions unless something is broken |
| Go-live | Publish changes, start a staged rollout and watch crash rates |
The checks for go-live minus 10 are in my 24-check Flutter Firebase release checklist, and day zero continues with my staged rollout rules. If the app is brand new, add the 14-day closed testing requirement for new personal accounts before any of this.
When review is taking too long
Wait the full seven days before you worry. After that, check these in order.
- Is it actually in review? Look for "Changes not yet sent for review" on Publishing overview. Unsent changes wait forever.
- Did you resubmit during review? If so, the clock started again at your last change.
- Is there an inbox message or policy email? Rejections and requests for information arrive in Play Console and by email.
- Is the app approved but not visible? If the status says it's live but search doesn't find it, see why a new app isn't showing on Google Play.
If none of those explains it, contact Play Console support from the Help menu in Play Console.
FAQ
How long does Google Play take to review an app update?
Often a few hours, but it can take up to seven days, or longer in exceptional cases. Some accounts, including new developer accounts, are subject to extended reviews.
Does submitting another change restart Google Play review?
It can. Google counts review time from the last submitted change, so submitting while changes are in review may push your app to the back of the queue.
Can I choose when an approved update goes live?
Yes, with managed publishing. Approved changes wait under "Changes ready to publish" until you click Publish changes. It isn't available for an app's first publish.
Are internal testing releases reviewed?
Usually not, so they're available right away. The exceptions are an app's first release and the first submission after a rejection.
Sources
- Play Console Help: publish your app and publishing statuses (checked 2026-10-25)
- Play Console Help: control when app changes are reviewed and published (checked 2026-10-25)
- Play Console Help: app testing requirements for new personal developer accounts (checked 2026-10-25)