How Long Does App Store Review Take in 2026? (And How to Speed It Up)

Most apps clear App Store review in under 24 hours. Apple's own App Review guidance says the large majority of submissions are reviewed within a day (Apple states that, on average, 90% of submissions are reviewed in under 24 hours), and in practice many go through in a few hours. Plan for 24 to 48 hours to be safe, and expect longer for your very first submission, an app that touches a sensitive area (payments, health, kids, login), or anything that gets pulled for a closer manual look.

That's the honest answer. The frustrating part is the variance: two near-identical builds can clear in three hours and thirty hours, and Apple publishes no per-submission SLA. Below is what actually drives the number, what each status in App Store Connect really means, how to request an expedited review when a launch or a critical bug fix is on the line, and what to do the moment your app goes live and the reviews that matter to your rating start rolling in.

For a typical update to an existing app, review usually completes within a day, often within a few hours once it moves into active review. First submissions tend to run longer because the whole app gets scrutinized rather than just the diff, and brand-new developer accounts sometimes see extra attention. Treat 24 to 48 hours as your planning window and anything faster as a bonus, not the rule.

TestFlight is a separate, faster track. Your first TestFlight build for external testers needs a Beta App Review that's usually quicker than full App Store review, and subsequent builds under the same version often become available to testers with little or no re-review. So if you need real-world testing before launch, get on TestFlight early — it doesn't count against your App Store review clock, and it surfaces the kind of crash a reviewer would reject you for anyway.

The other lever is timing your submission. Submitting Monday morning rather than late Friday won't change the SLA, but if your app does get routed to a manual reviewer, you're less likely to sit in a queue over a weekend or a holiday. Give yourself buffer before any hard launch date — never submit the morning of.

Half of "is my review stuck?" panic is just misreading the status. Here's the ladder a submission climbs, and which states are normal waiting versus a real problem:

"Waiting for Review" for many hours is not a bug — it's the queue, and queue depth swings with Apple's volume (spikes around major OS releases and the pre-holiday rush). If you've been in "In Review" for an unusually long stretch, it typically means a human is examining something specific: a permission you request, a login wall with no demo account, an in-app purchase flow, or a feature that overlaps a sensitive guideline.

The most common self-inflicted delays are avoidable. Missing or wrong demo credentials for a login-gated app is the number one stall — reviewers can't test what they can't get into. Server-side features that aren't live yet, an incomplete App Privacy section, a beta-looking build, or purchase flows a reviewer can't complete all push you toward a rejection round, and every rejection resets the timer. Front-load the App Review notes with everything a reviewer needs to reach and exercise your core feature.

Yes. Apple offers an expedited review request for genuinely time-sensitive cases — a critical bug or crash affecting live users, a security issue, or a launch tied to a fixed public event or date. Expedited reviews often turn around in a matter of hours, but approval of the request itself is at Apple's discretion and never guaranteed. Here's how to ask:

Yes — App Review runs seven days a week, including weekends and holidays, so a Saturday submission can absolutely clear on a Saturday. That said, throughput and queue times can wobble around major holidays and the late-December stretch, when submission volume surges and staffing shifts. In past years Apple paused certain App Store Connect release functions for a few days around the holidays; whether that applies in a given year is worth checking against Apple's current developer announcements (Apple no longer shuts App Store Connect down over the holidays, but it warns that reviews can run slower around December 20 to 26, so submit anything time-sensitive early).

Practical takeaway: don't bank on a holiday-week miracle. If you have a fixed launch date near a holiday, submit several days early and keep an expedite request in your back pocket only for true emergencies.

They're closer than they used to be, but different in shape. Google Play review can range from a few hours to several days, and Google's own guidance notes reviews may take longer than 7 days in some cases. The bigger gotcha on Play in 2026 is new personal developer accounts: before you can even ship to production, Google requires a closed-testing period with a minimum number of testers over a set stretch of days (currently at least 12 opted-in testers running continuously for 14 days, for personal developer accounts created after November 13, 2023 — down from the 20-tester rule that applied before December 2024). That's not a review delay so much as a gating requirement — but it means "time to live" on Play for a first-time solo developer can be far longer than a single App Store review.

If you're shipping to both stores, the two platforms diverge on more than review time — moderation, reply limits, and how reviews surface all differ, and we lay those out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies). Worth reading before launch so nothing about the Play side blindsides you.

Here's the part most pre-launch checklists skip: the day you clear review, a second, longer-running clock starts — your reviews. Early ratings punch above their weight because your review count is tiny, so a couple of one-stars in week one can drag a fresh average down fast, and how quickly you respond shapes whether an unhappy first user updates their rating. Answering fast and well in those first weeks is one of the highest-leverage things a new app can do; we get into why in [review velocity](/blog/review-velocity).

The problem is that launch week is exactly when you have no time to babysit two stores. This is where [ReplyArgus](/features) fits: it watches your Apple App Store and Google Play reviews in one inbox and drafts an on-brand reply, in the reviewer's own language, the moment one lands — grounded in your past approved replies, ready for you to approve. So a launch-day one-star doesn't sit unanswered for three days while you're firefighting. A good early reply looks like this:

One steady, specific reply like that, sent within hours instead of days, is often the difference between a two-star that sticks and a two-star the user quietly bumps to four. You want that habit running from day one, set up before the reviews start, not after they've piled up. And when launch week's inevitable angry one-star does land, here's [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) without making it worse.

Bottom line: budget 24 to 48 hours for App Store review, submit clean to avoid a rejection round, and keep expedited review for real emergencies. Then get ready for the clock that actually shapes your rating — the reviews. [Start free with ReplyArgus](/signup) — no card — and the moment your app is live, Argus pulls every App Store and Google Play review into one inbox and drafts your reply on the spot, so launch week's first one-star gets a thoughtful answer in minutes, not days.