App store review time in 2026: what Apple and Google actually take

If you are planning a launch date, the app store review time is the one number people guess at and get wrong. Founders assume it is instant, or they assume it is two weeks, and then the marketing plan is built on the wrong figure. This guide gives you the real app store review time we see in 2026 across both stores, why the two platforms differ so much, and how to plan a launch so review is never the thing that slips your date.

We ship iOS and Android apps at Zarle, in-house, and we go through review on both stores constantly. Optima Learning, Fit Mom by Pooja Batra, Chefadora, Marcoob, these went through the same queues everyone else does. So the app store review time numbers below are not scraped off a support page. They are what we watched happen, submission after submission, including the parts that catch first-time publishers off guard.

The short version: Google Play is fast and Apple is slower in 2026 than it used to be. But the number on the review screen is only half the story. The bigger delay for most new apps is a testing gate on Google that has nothing to do with review at all, and we will get to that.

The quick answer

Here is the app store review time we work with as of August 2026, before we explain the exceptions.

• Apple App Store, first app: roughly 1 week to 10 days at the slow end, but most land in 2 to 3 days.
• Apple App Store, updates: usually 24 to 48 hours.
• Google Play, first app and updates: usually around 24 hours, at most 48 hours if something is flagged.
• Google Play, hidden gate: if you registered a personal account, you must run a 14-day closed test with at least 12 testers before you can even request production. That is not review time, but it is the real wait.

Now the detail, because the averages hide the cases that hurt.

Apple App Store review time in 2026

Apple has gotten slower. For years the App Store review time sat comfortably in the one to two day range, and Apple still quotes that most submissions are reviewed within 24 to 48 hours. In practice, through 2026, we have seen brand-new apps sit in "Waiting for Review" for a couple of days before a human even opens them, and then the review itself on top of that.

So the honest range for a first app in 2026 is 1 to 10 days. Most of ours clear in 2 to 3 days. The 10-day cases are the outliers, usually a new developer account with no history, a sensitive category, or a submission that got pulled for a closer look. Updates to an already-approved app are much faster, generally 24 to 48 hours, because the app already has a track record and the reviewer is only looking at what changed.

What stretches Apple's app store review time:

• A new developer account with no submission history. Apple treats first-timers more carefully.
• Sensitive categories and APIs: health, finance, kids, AR, and anything touching login or payments.
• AI-generated content tools, which have drawn extra scrutiny through 2026.
• An incomplete submission: missing metadata, no reviewer demo login behind a signup wall, or unclear data-use answers.

That last one matters more than people think. A rejection resets your clock. If Apple bounces the build on day two, you fix it, resubmit, and start the wait again. The way to protect your app store review time is to not get rejected in the first place, which is a content problem, not a timing one. We wrote up the specific triggers in our guide to app store rejection reasons, and the big ones are boringly consistent: no privacy policy on the signup screen, no "Delete my account" option inside the app, in-app-purchase rules ignored, and reviewers left without a working test login.

If you have a genuine emergency, a critical crash affecting live users, Apple offers an expedited review you can request. Use it sparingly. It is for real fixes, not for beating a launch deadline you set too tight.

Google Play review time in 2026

Google Play is the fast one. The app store review time on Play is usually around 24 hours, and 48 hours is the realistic worst case if your build trips an automated flag. New accounts can occasionally take up to about 3 days for the first submission, but once you are established, updates clear quickly and predictably.

That speed is real, and it is one reason India-first teams often lean Android-first anyway. But do not let the fast review number fool you into thinking Play is the quicker route to production, because there is a separate gate that dwarfs review time.

The Google gate nobody budgets for: 14 days of closed testing

Here is the part that surprises almost every first-time publisher, and it is the single most important thing in this article.

If you created a personal Google Play developer account after 13 November 2023, you cannot publish straight to production. Google requires you to run a closed test first: a minimum of 12 testers must opt in and stay opted in for 14 continuous days before you are even allowed to request production access. The rule used to be 20 testers; Google cut it to 12 in December 2024. Since April 2026, Google also checks that those testers actually use the app, not just tap "join," so near-daily opens across the two weeks are the safe target.

Read that again. The app store review time on Play is 24 hours. The path to your first production release on a personal account is at least 14 days, plus the effort of recruiting and keeping 12 real, engaged testers. That is the true launch delay, and it is invisible until you hit it.

The clean way around it is the one we push on every client: register as an organization, not an individual. An organization account can go to production from day zero, no 14-day closed-test gate at all. This is why account setup is not paperwork you do at the end. It is the first decision, and getting it wrong costs you weeks.

There is a catch that makes this a plan-ahead problem. You cannot easily fix the account type later. Apple lets you switch an individual account to an organization, but that migration takes roughly 3 to 4 weeks. Google offers no switch at all: you would have to create a brand-new account and re-register the app from scratch. So the sequence is: set up the organization properly, get your DUNS number sorted first, then create the Apple and Google accounts. We break the full trade-off down in individual vs organization developer accounts, because this one choice affects your app store review time, your testing gate, and your store commission all at once.

Apple vs Google review time: the comparison

Here is the app store review time picture side by side, so you can plan against both at once.

The takeaway from the table: Apple review is the longer wait per submission, but Google's testing gate is the longer wait to your first launch if you set the account up as an individual. Different problems, both fixable in advance.

How to plan a launch around review time

Review time only wrecks a launch when you treat it as an afterthought. Build it into the plan and it becomes a non-event. This is how we sequence it.

Set up the organization account first. Before a line of production code is finalized, get the business entity and DUNS number in place, then open both developer accounts as an organization. This kills the 14-day Google gate and avoids the multi-week account switch later. It is the highest-leverage thing you can do for your timeline.

Submit for review before you think you are ready. One of the most common mistakes we see is founders holding the build back for a final polish, then discovering approvals take days they did not budget. Get the app into review early, once the core MVP works, so any rejection cycle happens well before your public date, not on top of it. If you are still scoping, our take on how long it takes to build an app folds review into the overall timeline.

Launch iOS and Android together, and account for both clocks. We strongly recommend shipping both platforms at the same time rather than iOS-then-Android. That means the slower of the two review times is your real critical path, which in 2026 is Apple. Plan your marketing around Apple's 2-to-3-day window with a buffer, not Google's 24 hours.

Pad the estimate for a first-ever submission. A new account with no history is the slow case on both stores. If this is your company's first app, add a few days of buffer and do not announce a hard date until the build is approved and sitting in "Ready for Sale."

Use OTA updates for post-launch fixes where you can. Once you are live, not every change has to go back through review. Server-driven changes and JavaScript or asset-level updates in a React Native build can ship without a new store submission. Since Microsoft's CodePush shut down in March 2025, the path for React Native is Expo EAS Update. Anything that changes native code or the binary still needs a full review, and you must never use OTA to change the app's core purpose, which breaks store rules. Choosing the right stack up front is part of this, and it ties into the wider cross-platform app development decision.

What review time does not tell you about cost

Review is free. The accounts around it are not, and people forget them. Apple's Developer Program is a recurring fee of about 99 USD a year, so budget the renewal every year. Google Play is a one-time 25 USD fee. On top of that sits the store commission of 15 to 30 percent on paid and in-app-purchase revenue. None of that changes your app store review time, but it does change your launch budget, and we fold it into the fuller picture in our mobile app development cost breakdown.

Frequently asked questions

How long does app store review take in 2026?

For Apple, a first app typically takes 2 to 3 days, with a slow-case range up to 7 to 10 days, and updates clear in 24 to 48 hours. For Google Play, review is usually around 24 hours and at most 48 hours. Apple is the slower of the two per submission in 2026.

Why is Apple's review slower than Google Play's?

Apple runs more manual, human review and has tightened scrutiny through 2026, especially on new accounts, sensitive categories, and AI content tools. Google Play leans more on automated checks, so most submissions clear in about a day. The gap is a difference in review philosophy, not something you can speed up from your side beyond submitting a clean build.

Do I really have to test for 14 days before launching on Google Play?

Only if you registered a personal developer account after 13 November 2023. Those accounts must run a closed test with at least 12 engaged testers for 14 continuous days before requesting production. An organization account skips this gate entirely and can publish to production from day zero, which is why we register clients as organizations.

Can I switch my developer account from individual to organization later?

On Apple, yes, but the migration takes roughly 3 to 4 weeks. On Google, there is no switch at all, so you would have to create a new account and re-register the app. Because of this, set up the organization and get your DUNS number before you ever open the developer accounts.

How can I speed up app store review?

Submit a complete build with all metadata, a working reviewer demo login behind any signup wall, a linked privacy policy, a "Delete my account" option, and correct data-use answers. That avoids rejection, which is what actually resets the clock. Apple also offers an expedited review for genuine critical fixes, but use it only for real emergencies.

Does getting rejected reset the review time?

Effectively yes. A rejection sends you back to fix and resubmit, and the review clock starts over on the new submission. This is why avoiding common rejection triggers matters more for your timeline than the raw review speed does.

Should I launch iOS and Android at the same time given the different review times?

Yes, we recommend launching both together. Just plan against the slower store, which is Apple in 2026, so Apple's 2-to-3-day window with a buffer becomes your real critical path rather than Google's 24 hours.

Plan the launch, not just the build

The app store review time is predictable once you know the real 2026 numbers: Apple slower, Google faster, and a 14-day Google testing gate that only bites personal accounts. The teams that miss their launch date are almost never the ones whose review ran long. They are the ones who set up the wrong account type, submitted too late, or got rejected on a detail they could have fixed in an afternoon.

We handle all of this in-house, from account setup and the DUNS registration through submission, review, and post-launch OTA updates, so the store timeline is planned rather than discovered. If you are mapping a launch and want the review-and-release path built into it from the start, have a look at our mobile app development work and let us plan the timeline with you.