How Long App Review Actually Takes in 2026

Apple says most App Store submissions clear in one or two days. Google says review can take a few hours or up to seven days, and tells you to leave at least a week before a hard launch date. Forum threads about month-long waits are real, but they are the long tail, not the plan you should write a release calendar around.

This post sticks to what each store publishes, plus one independent tracker for Apple. No invented averages from my own inbox.

Apple: 90% under this

0days

Google: minimum buffer

0days

Play closed-test gate

What Apple publishes

App Review works around the clock. Apple's goal is to review at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Updates with small changes and bug fixes usually move faster. First apps, apps that need licenses, and apps that touch new or regulated capabilities can take longer.

Apple also lists cases where review stretches on purpose: little or no prior App Review history, missing documentation, and complex or novel issues. Those are the cases where a two-day buffer is thin.

What an independent tracker shows

Runway publishes truncated means from teams that use its release tool. In late September 2026 it showed roughly 7 hours waiting for review and about 2 hours in review for App Store submissions. Monthly averages through 2026 stayed under a day of waiting in most months, with a long tail: one July waiting time hit 42 days.

Treat that as a mood check, not a promise. The sample is established release teams, and the average hides the outliers that fill the developer forums.

What Google publishes

Google does not promise a fixed review time. Play Console Help says processing can take a few hours or up to seven days, or longer in exceptional cases. The same page tells you to plan a buffer of at least a week between submitting and going live.

Two extra rules matter for first launches:

If you submit more changes while a review is open, the clock restarts from the last change and you can drop to the back of the queue.
Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 opted-in testers for 14 continuous days before they can apply for production. That gate alone is two weeks, before production review even starts.

There is no expedited review button on Google Play. Managed publishing lets you approve a reviewed build later. It does not make the review itself faster.

Plan the buffer, not the average

Averages tell you what usually happens. A launch date needs the margin for what the store itself asks you to assume. Use the planner below with your store and your scenario. The buffer days come from the published goals and tips above, not from a private sample of my apps.

Store

What you are shipping

Hard launch date

2days

Recommended buffer

2026-11-18

Submit by

Apple's published goal: 90% of submissions reviewed in under 48 hours. Two calendar days covers that goal for a routine update.

Buffers are planning margins from Apple and Google docs, not measured averages. A rejection still adds another full review cycle.

How to avoid restarting the clock

Most delays you can control are unfinished homework, not the queue:

Put demo credentials and review notes in App Review Information or Play Console before you submit.
Attach licenses and partnership docs when the app needs them. Do not wait for a rejection to dig them up.
Do not yank a waiting App Store submission just to resubmit. Apple says the process then starts over.
On Play, freeze the change set once review starts. Extra uploads push you to the back of the queue.
Use staged rollout or managed publishing so a green review does not have to mean "live this minute."

If you are past three or four days on Apple with no status change, treat it as an exception and follow up in App Store Connect. Do not rebuild your whole launch plan around the longest forum story you found that week.

The actual takeaway

For a routine App Store update, plan two days. For a first App Store app, plan four. For Google Play, plan a week, and add the 14-day closed test if your personal account is new. The stores publish those margins. The planner above turns them into a submit-by date.

I ship every update this way. If you want a second look at a release plan before you hit Submit, let's talk.