How Long Does App Store Review Take in 2026 (and How to Avoid Re-Review Delays)
21 Jun 2026 · 5 min read · Erik van Kammen
Quick answer: Apple states that most app submissions are reviewed within 24 hours, and that historically around 90 percent are reviewed in less than a day. In practice, third-party trackers in 2026 show more variance, with the "Waiting for Review" stage sometimes adding a few days during busy periods, and new apps often taking longer than updates. The single biggest delay is a rejection, because fixing and resubmitting puts you back in the queue. Here is what affects review time and how to avoid the re-review loop.
Review time is really two questions: how long does Apple take on a clean submission, and how long does the whole trip take if something gets kicked back. The first is mostly out of your hands. The second is almost entirely in your control.
How long does App Store review actually take?
Apple's own guidance is that most submissions are reviewed within 24 hours, and Apple has long stated that around 90 percent are reviewed in less than a day. Third-party trackers that sample real submissions report broadly fast turnaround in 2026 as well, but with more variance than the headline number suggests: the "Waiting for Review" stage can add time before active review even starts, and new apps tend to take longer than updates.
Treat any single number as indicative, not a guarantee. Your own time depends on the factors below far more than on a published average.
What affects your position in the queue?
- New app versus update. First submissions of a brand-new app generally get more scrutiny than an update to an existing one.
- Prior rejection history. An app that has bounced before can attract closer review.
- Sensitive categories. Kids, health, finance, and similar categories are reviewed more carefully.
- Metadata problems. Screenshots, description, or keywords that do not match the binary slow things down or trigger a rejection.
- Seasonal slowdowns. Review can be slower around major holidays.
- Expedited review. Apple offers an expedited request for genuine emergencies, such as a critical bug fix, but it is not for routine releases.
The real time sink: the re-review loop
A clean submission is fast. A rejection is not, because you have to diagnose it, fix it, resubmit, and wait in the queue again. One avoidable rejection can add days to your time-to-live, which is why the highest-leverage thing you can do is pass on the first attempt.
That is also why the common technical rejection reasons matter so much for planning: missing purpose strings, a privacy label that does not match the binary, broad App Transport Security exceptions, and similar issues are exactly the ones that send you back to the start. See why apps get rejected and the 2026 guideline changes for what reviewers are checking now.
The factors at a glance
| Factor | Effect on review time | What to do |
|---|---|---|
| New app vs update | New apps often slower | Plan extra buffer for a first submission |
| Prior rejections | Can attract closer review | Resolve issues fully before resubmitting |
| Sensitive category | Slower, closer review | Prepare complete metadata and review notes |
| A rejection | Adds days via the re-review loop | Pre-check the binary to pass on attempt one |
| Genuine emergency | Expedited review can help | Use it sparingly and honestly |
How to avoid re-review delays (checklist)
- Run a pre-submission check of the binary for the common technical rejections (permissions and purpose strings, privacy-label mismatch, App Transport Security exceptions).
- Make sure metadata matches the binary and contains no placeholder content.
- Provide a working demo account and clear notes so the reviewer can reach every feature.
- If you are rejected, respond promptly and completely in the Resolution Center rather than resubmitting blindly.
- Reserve expedited review for real emergencies so it remains credible when you need it.
Where a pre-submission check helps
You cannot control Apple's queue, but you can control whether you enter it twice. Catching the common technical rejection reasons before the first submission removes the biggest and most avoidable source of delay. A pre-submission scan of the binary flags those issues in CI, so a slow review is at least a single trip rather than a loop. For the full pre-flight, see the iOS app submission checklist and the guide to fixing 5.1.1 privacy rejections.
Frequently asked questions
How long does App Store review take in 2026?
Apple states that most submissions are reviewed within 24 hours, and historically around 90 percent in less than a day. Third-party trackers show more variance in 2026, with the "Waiting for Review" stage sometimes adding time, especially for new apps and during busy periods.
Why is my app stuck in "Waiting for Review"?
That stage means your build is in the queue but a reviewer has not started on it yet. It can last from hours to a few days depending on volume. It is normal and does not by itself indicate a problem.
Can I speed up App Store review?
You can request expedited review for genuine emergencies such as a critical bug fix. Beyond that, the most reliable way to shorten total time-to-live is to avoid a rejection, since a rejection sends you back into the queue.
Does a rejection reset my place in the queue?
Effectively yes. After you fix the issue and resubmit, the new build re-enters review. That is why passing on the first attempt is the biggest lever on how quickly your update goes live.