How Long Does Google Play Take to Approve a New App in 2026?

Google Play review used to be a joke. In the early 2010s a submission cleared in two hours. By 2018 it was a few hours. By 2022 you might wait a day. In 2026, the answer to "how long does Google Play take to approve a new app" is more complicated than it has ever been, because Google has spent the last three years tightening review on identity, policy compliance, and minimum-quality requirements.

The numbers below are based on developer reports across 2026 and Google's own public guidance at support.google.com/googleplay/android-developer/answer/9859751. They are approximate. Your mileage will vary depending on your account history, your app's category, and which way the policy enforcement winds are blowing that week.

The headline numbers

• First submission from a brand-new developer account: 7 to 14 days.
• Subsequent updates to an existing app: 1 to 3 days, often hours.
• First submission to a category that requires special declarations (health, finance, gambling, kids, government, COVID-19): 14 to 21 days.
• Submissions with unresolved policy issues: Indefinite. Google's bot rejects, you fix, you resubmit, and the clock resets.

These numbers are noticeably longer than they were in 2022 or 2023. The most-cited explanations from Google itself are the expanded content policy reviews introduced through 2024, and the developer identity verification rules that became mandatory for new accounts in late 2023.

What actually takes the time

For a first submission, the review breaks into roughly four stages. None of them are the technical "is the APK well-formed" check most people think of when they hear "app review".

Stage 1: Developer identity verification (days 1 to 5)

Google introduced mandatory developer identity verification in 2023. Every new developer account has to verify identity with a government ID, a bank account, and either a residential or business address. If you registered as a business, Google additionally verifies you actually represent the business through a D-U-N-S Number lookup or a phone call.

This stage is where most first-time submissions stall. If you uploaded a low-resolution photo of your ID, or the name on your bank account does not match the name on your ID, you wait. Google will not tell you what is failing; it just sits in "review pending" for an extra few days. Google's identity verification help article covers the requirements but undersells how strict the matching is.

Stage 2: Policy review of metadata (days 2 to 7)

Google reviewers (a mix of bots and humans) check your store listing for policy compliance. The 2024-onwards policy is much stricter than 2020. Issues that get flagged at this stage include:

• Screenshots that show features not actually present in the app.
• Descriptions that promise things the app cannot deliver.
• Generic "boost your productivity" descriptions with no concrete functionality.
• Missing required policy declarations (Data Safety section, target audience, ads in app, financial product disclosures).

Many small businesses get hung up on the Data Safety section. It is genuinely tricky if your app does anything beyond the basics. Google's Data Safety form guidance is the canonical reference. Errors in the Data Safety section are one of the top three rejection causes for first submissions.

Stage 3: Static and behavioural analysis of the APK or AAB (days 1 to 3)

This is where Google's automated systems decompile your build and look for malware signatures, copycat behaviour, third-party SDKs with known issues, and excessive permissions relative to the stated functionality. For a normal first-party app, this stage is fast. For apps using older or less-known SDKs (especially older ad networks), this stage can flag warnings that require manual review.

Stage 4: Manual human review (days 3 to 10 if triggered)

Google does not human-review every submission. They human-review submissions that the automated systems flag, that fall into categories requiring extra scrutiny, or that come from new accounts. If your app is human-reviewed, it adds days. There is no way to opt out or speed this up.

What changed between 2024 and 2026

Three things are noticeably different.

The 12-tester rule. Since late 2024, new developer accounts have to ship a closed test to at least 12 testers for 14 days before they can apply for production access. This effectively adds a two-week window before your first public release is even possible. Google's developer guidance on this is the canonical source. There is no way around it. It is a real two weeks added to every new developer's launch timeline.

Mandatory app bundle format. Google switched fully to the AAB format for new apps in 2021. By 2026, even small updates must be AAB. APKs work for internal distribution and testing but not for the store. If you are building with a no-code platform and seeing only APK output, check whether the platform also generates an AAB.

Stricter category-specific rules. Finance, health, kids, news, government, and a few other categories now require additional declarations and sometimes extra documentation (financial licenses, health-data agreements). Apps in those categories should expect 14-day-plus reviews even on updates.

How to actually keep the wait short

The short version: get everything right the first time. Specifically:

• Verify your identity before you start the closed test. Do the photo ID upload on day one, not day fourteen. This way the identity check runs in parallel with your test period rather than after it.
• Fill out every metadata field thoroughly. The "Data Safety" section especially. Missing or incomplete answers trigger manual review and lose you days.
• Take real screenshots of the app, not mockups. Mockups get flagged.
• Avoid generic descriptions. "An app for your business" is the kind of phrase that triggers human review. Concrete is better.
• Use known, well-established SDKs. The Google AdMob SDK clears review without a hitch. A no-name ad network you found yesterday might delay you a week.
• Submit Monday or Tuesday. Google's review staff are heaviest Monday to Wednesday. Friday submissions sit through the weekend before review starts.

Apple, for comparison

Apple's App Store review is faster than Google Play in 2026, surprisingly. Most submissions clear in 24 to 48 hours. First submissions for new developers take 3 to 7 days. The trade-off is that Apple's rejection rate on first submissions is higher: roughly 35 percent of first submissions get rejected, mostly for guideline issues that the developer did not realise applied. Our App Store rejection reasons guide covers the main ones.

Practically speaking, if you submit to both stores at the same time, Apple usually approves first and Google usually approves second. Plan for two separate review windows rather than treating them as one.

What happens if your app is rejected

Google rejections come with a category code (4.1, 8.3.7, etc., mapped to the developer content policy) and a short explanation. Sometimes the explanation is useful. Sometimes it is two sentences of boilerplate that does not really tell you what to fix.

If the explanation is unclear, the best path is to use the developer console's appeal mechanism. You file an appeal explaining what you have changed (or what you think is mistaken) and a human reviewer will look at it. Appeal turnaround in 2026 is roughly 3 to 7 days. Most appeals do not succeed, but the human reviewer's response usually tells you specifically what to fix.

What you cannot do

There is no premium fast-track for Google Play review. There is no "I am paying you, please prioritise me" option. Even larger established developers wait in roughly the same queues.

There is no support phone number for review issues. The only contact path is through the developer console's messaging system.

There is no way to know exactly where your app is in the review queue. Google will tell you "your app is under review" until the moment they tell you "your app is approved" or "your app is rejected". The opacity is part of the experience.

Bottom line

For a first submission, plan on two to three weeks between hitting submit and your app being live in Google Play. For updates to an established app, plan on one to three days. Build that into your timeline. If you launch a marketing campaign tied to a specific date, do not assume your first submission will be approved by then.

For most small businesses, the practical advice is to start the submission process the moment your app is ready for closed testing, not the moment it is "ready for the public". The two-week closed-test minimum alone catches most launch plans off guard.