How Long Does Google Play Review Take? Real Timelines for 2026

"Pending publication" is the most anxious screen in Play Console. There is no published SLA, and the honest answer is that review time depends on factors you can partly control. Here is what actually drives it.

The realistic ranges

For an established account with a history of clean releases, updates often clear within a few hours to a couple of days. For a brand-new developer account submitting its first app, allow up to seven days, and occasionally longer. Google's own guidance says reviews can take up to seven days and sometimes longer, and that is the number to plan against.

What makes review slower

• A new developer account with no release history — first submissions get the most scrutiny.
• Sensitive permissions such as SMS, call log, accessibility services, or all-files access.
• Financial features: lending, payments, crypto, insurance. These frequently need licensing evidence and can add weeks.
• A declared child audience, which brings Families policy review.
• Health, medical or COVID-related claims.
• A prior policy violation on the account.
• Broken or missing App access credentials, which turn a review into a rejection cycle.

What makes it faster

• A consistent release cadence from an account with no violations.
• Complete, accurate App content declarations that agree with your privacy policy.
• A working review login that does not expire, with written steps.
• Not changing your target audience, permissions or monetisation in the same release as a feature launch.

Production access review is a separate queue

If you are on a personal account created after 13 November 2023, you first apply for production access after completing closed testing. That application is reviewed by a human reading your written answers about tester recruitment and feedback, and it is not the same as app review. Budget for both, one after the other.

Vague answers are the main reason that application comes back. Keep a change log during the test: who reported what, which builds you shipped, what you fixed.

When your app is stuck

• Check the Publishing overview page — a release can be held because an unrelated section is incomplete.
• Check your email, including spam, for a policy notice. Rejections are emailed, not always surfaced prominently in the console.
• Verify the review account credentials still work. Expired test logins are the single most common silent cause.
• Wait the full seven days before contacting support. Contacting earlier rarely helps and resets nothing.

Plan launches around the queue, not the build

A first app on a personal account realistically takes three to four weeks end to end: account verification, then the closed testing window, then production access review, then app review. The build is the short part.

Never announce a launch date that assumes a fast review. Ship to production, wait for it to go live, then announce.

The part you can remove from the timeline

The one stage that is fully in your hands is recruiting testers who stay opted in for the whole window. Most delays we see are not Google being slow — they are a tester count that dropped on day nine and restarted the clock. CloseTesting supplies verified manual testers who stay opted in for the full period, which turns the most unpredictable stage into a fixed one.