How long does Google Play review take in 2026? What to do when your app is stuck in review

How long does Google Play review take? Officially, anywhere from a few hours to seven days, and "longer in exceptional cases". In practice, the Google Play review time has become the most unpredictable step in shipping an Android app this autumn. On September 16, 2026, Daniel Gultsch, the developer of the 12-year-old XMPP client Conversations, posted that "the Google Play app review process now regularly takes longer than a week", with a screenshot of an update submitted on September 9 and still pending. The post reached the front page of Hacker News with more than 350 comments, many of them from developers with the same story.

This guide sets out what Google actually promises, what developers are seeing in 2026, what every status in Play Console means, and a practical plan for the day your app is stuck in review. It also covers how to plan a launch or a critical fix so that a slow review does not decide your release date for you.

Key takeaways

• Google says review "can take a few hours or up to seven days (or longer in exceptional cases)" and tells you to plan "a buffer period of at least a week."
• Some developer accounts get extended reviews on purpose; new and less established accounts are the most likely to wait.
• Adding changes while an update is in review can push it "to the back of the app review queue."
• There is no expedited review on Google Play. Managed publishing, pre-review checks and small, clean submissions are your levers.

How long does Google Play review take? What Google says#

Google's help pages give two numbers, and both are worth quoting exactly.

On the managed publishing page, Google says processing "can take a few hours or up to seven days (or longer in exceptional cases)" and recommends planning "a buffer period of at least a week" before any date that matters. The same page carries a warning that most developers miss: submitting more changes while others are in review may push your app "to the back of the app review queue."

On the publishing status page, Google explains why some apps wait longer than others: "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."

So the official Google Play review time is not one number. It depends on the account, the app and what changed. Google does not publish which accounts get the slower path, but its own documentation of the testing requirement for new personal accounts, and the developer verification that started on September 30, 2026, both point the same way: the less history Google has with you, the more scrutiny you should expect.

How it compares with App Store review#

Apple is more specific. Its App Review page says App Review typically reviews "at least 50% of submissions in less than 24 hours and 90% in less than 48 hours", and Apple accepts expedited review requests for critical bug fixes and event deadlines. Google's help pages document no equivalent request. If you ship on both stores, the Android build is now often the one to submit first. (If your iOS build is the one that keeps coming back, our guide to App Store rejection reasons covers the usual causes.)

Google Play review time in 2026: what developers are reporting#

The Hacker News thread is a useful snapshot because so many of the replies come from maintainers of large, long-lived apps:

• The AnkiDroid team, with a 17-year-old app, wrote that an alpha submitted on September 3 was still pending review when the thread was posted on September 16.
• A developer writing for Signal said "review times are extremely inconsistent. Sometimes it's 4 hours, sometimes it's 5 days, and there's no visibility as to why." Their working theory: "there's automated and manual queues, and occasionally, for whatever reason, we fall into the manual queue" (comment).
• Others reported the opposite: one team with a 16-year-old app said their reviews "consistently" take 30 minutes to an hour, and another had a production submission approved within 4 hours.

Then, on October 4, a post on Hacker News described how Peter Steinberger publicly asked for help after OpenClaw's Android app spent "over a week in review limbo", got a reply from Google's CEO, and saw the update go live hours later. Most developers cannot tag a CEO, so the useful lesson is the rest of this guide: make your submission easy to approve, and stop depending on a review finishing on a given day.

The same app can clear review in four hours one week and five days the next. Plan for the slow case. Photo: Christina Morillo / Pexels

Why your next review may be slower than usual#

Two dates make the coming weeks busier than normal. Apps that took Google's one-time extension for the API 36 requirement must target API 36 by November 1, 2026, after which Play will not accept their updates at all, and holiday releases usually land in the same window. If your update depends on that migration, submit it now rather than in the last week of October.

What each Play Console review status means#

Most "stuck in review" questions are really "what does this status mean?" questions. These are Google's definitions from the publishing status page:

The first row catches more people than any delay. Since Google's 2023 changes to the Publishing overview, edits made in Play Console sit under Changes not yet sent for review until you send them yourself. If your release has shown no movement for days, check that it was actually sent.

Why some Google Play reviews take longer#

Google does not publish its review criteria, so treat this list as the factors Google itself names, plus the patterns developers report most often.

1. Your account. Google says "certain developer accounts" get longer reviews. New personal accounts also have to pass the 12 testers for 14 days rule before their first production release, and the production access application has its own review of up to about a week.
2. What you changed. A new app, a first production release, new permissions, a changed target audience or new app content declarations give reviewers more to check than a bug fix.
3. Restricted access. If any part of the app is behind a login, Google's preparation checklist says you must "provide all required details to enable access to your app." A reviewer who cannot sign in cannot approve you.
4. Piling on changes. Google says the review turnaround "is counted from the last submitted change to an app", so a change sent while another is in review can push your app to the back of the queue. Every extra listing edit or rollout tweak restarts your wait.
5. Volume. Gultsch blamed queues "clogged with AI slop". Google has not confirmed this, but it matches the timing of the reports.

How to make your next Google Play review faster#

You cannot pay for speed, but you can remove every reason for a reviewer to pause.

Use pre-review checks and Save for later#

In January 2026, Google added Save for later to the Publishing overview. It works with pre-review checks, which scan your pending changes for issues "that may prevent your app from being published" before you send anything. If one track has a problem, save that change for later and send the rest. App-wide problems, such as an incomplete App content section, block everything until fixed, so clear those first.

Send small, complete submissions#

• One release and the listing changes that go with it, not a month of accumulated edits.
• App content declarations, data safety answers and the privacy policy URL finished before you press Send for review.
• Login credentials and any special instructions in App access, and test that the account works the same day.
• A release note that says what changed. It is not a review requirement, but it makes the reviewer's job easier.

Separate approval from launch with managed publishing#

Managed publishing holds approved changes until you select Publish changes, after which the update is live "within a few minutes". That turns review into a step you finish days early instead of a gamble on launch morning. Two limits: "you can't use it when publishing an app for the first time", and it does not cover internal test tracks. Some changes also skip it, including increasing a staged rollout to 100%, updating release notes and changing prices.

Managed publishing lets you collect approval days before launch and publish in minutes when you are ready. Photo: Pixabay / Pexels

Plan a first launch around the review, not a date#

Because managed publishing is not available for a first release, a new app goes live as soon as it is approved. A safer plan:

1. Finish closed testing and production access first; those steps alone can take three weeks for a new personal account.
2. Submit the production release at least a week before you announce anything.
3. If you need people waiting on day one, run Google Play pre-registration while you wait. Pre-registered users get a notification the moment you launch.
4. Schedule the announcement for after approval, using the launch-week visibility checklist so every link you share points at a ready listing.

Stuck in review? A day-by-day plan#

If your app has been in review longer than you expected, work through this in order:

• Day 0 to 3: confirm it is really in review. Check the Publishing overview for Changes not yet sent for review, check the Inbox and the Policy status page for messages, and make sure every declaration is complete.
• Day 3 to 7: leave it alone. Do not add changes or pull the release back. Google notes that changes removed from review "may still be subject to review", so withdrawing rarely saves time. Google's own range runs to seven days.
• After 7 days: contact support. Use the contact options in the Play Console Help Center and include the package name, the release name and the date you sent it. Keep the message factual.
• If you are rejected: fix and resubmit. Google says you can resubmit "without contacting or waiting for a reply from the policy support team", so do not wait on an appeal if the fix is clear. Appeal only when you believe the decision is wrong.
• For a critical bug: reduce what you ask Google to review. Ship the smallest possible fix, with no listing edits or permission changes in the same submission. To get the build to your own team or key testers while you wait, use the internal test track: Google says updates there "are not subject to reviews" and are available immediately "in most cases", though they may be reviewed retroactively. The exceptions: an app's first release, and the next submission after a rejection, are reviewed first.

Google Play review checklist#

• At least a week of buffer between submission and any public date.
• Changes actually sent: nothing left under Changes not yet sent for review.
• Pre-review checks clear; App content section complete.
• Working test credentials and instructions in App access.
• One release per submission, no extra changes while it is in review.
• Managed publishing on for updates, so approval and launch are separate steps.
• API 36 migration shipped well before November 1, 2026, if you took the extension.
• New personal account: closed testing and production access done before the launch plan starts.

Keep promoting while the queue moves#

A slow review delays your update, not your audience. While a release waits, the version already on Google Play is still the one people can install, so the traffic you send now still counts. That is a good time to work on what you control: your store listing, your App Store analytics on iOS, and the places people find you outside the stores.

On AppRanker, an Android app's rank on the leaderboard is a plain sort on what each listing has paid, with no review queue and no algorithm in between, and every row links straight to your Google Play page. To see what a position costs today, paste your Google Play link on the AppRanker home page: every rank shows its price before you pay.

FAQ#

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

Google's documentation says review can take up to seven days, or longer in exceptional cases, and new or less established developer accounts are the most likely to get extended reviews. New personal accounts also need 14 days of closed testing and a production access review before the first production release.

How long does Google Play review take for an update?#

Often a few hours to a day for an established app, but 2026 reports range from under an hour to more than a week for the same kind of update. Google tells developers to plan a buffer of at least a week.

Can I expedite a Google Play review?#

Google's help pages describe no way to request an expedited review. What you can do is submit only the change you need, keep App content and App access complete, avoid adding changes while the update is in review, and contact Play Console support if it passes seven days.

Why does my update say "Changes not yet sent for review"?#

Play Console does not send edits for review automatically. Open the Publishing overview and select Send for review. Until you do, nothing is in the review queue.

Does managed publishing make review slower?#

Managed publishing does not change the review itself. It only holds approved changes until you select Publish changes, so you can approve early and release on your own schedule. It cannot be used for an app's first release.

Image credits#

• Cover, hourglass on a desk: photo by Mike on Pexels, Pexels License. Cropped to 1200x630.
• Developer with an Android sticker on a laptop: photo by Christina Morillo on Pexels, Pexels License. Resized.
• Android phone beside a laptop keyboard: photo by Pixabay on Pexels, Pexels License. Resized.