App Store

    What are Apple's App Review team working hours?

    An App Store submission being reviewed at night and over a weekend, showing App Review operates around the clock with no fixed hours

    If you are refreshing App Store Connect and wondering whether reviewers have gone home for the night or the weekend, the answer is that App Review does not keep office hours at all. This is for developers planning a launch who want a realistic timing expectation instead of folklore about the best day to submit.

    Short answer

    Apple does not publish working hours for the App Review team, and review does not stop for weekends or holidays. Per Apple's App Review page, on average 90% of submissions are reviewed in under 24 hours, and that happens around the clock rather than in a fixed business window. So waiting for Monday morning does not help. The number to plan around is the 24-hour average, with the caveat that high-volume periods can run slower.

    What you should know

    • No published hours: Apple lists no office hours for the App Review team.
    • Weekends included: reviews arrive on Saturdays and Sundays, not just weekdays.
    • Around the clock: status changes happen at all hours, not in a single time zone's day.
    • The real number is the average: 90% of submissions reviewed in under 24 hours.
    • Holidays can be slower: late December and other peaks can stretch the wait.
    • Resubmitting resets the clock: a rejection sends you back into the queue.

    Why is there no fixed schedule?

    App Review is a continuous operation, not a nine-to-five office. Submissions flow in from developers worldwide at every hour, and the review queue is worked through accordingly, including weekends and most holidays. That is why developers routinely see an approval land late at night or over a weekend. There is no single time zone whose business hours govern when your app gets looked at.

    The practical consequence is that timing your submission to a particular day or hour is wasted effort. The queue does not reset on Monday, and it does not freeze on Friday evening. What governs your wait is volume and your app, not a clock on a wall.

    What timing should you actually plan for?

    Use Apple's published average. The table below frames it.

    QuestionReality
    Are there office hours?No published hours; review is continuous
    Weekends and holidays?Reviews continue, with some holiday slowdowns
    Typical time?90% of submissions reviewed in under 24 hours
    Guaranteed time?None; it is an average, and yours can vary
    Slower windows?Anticipated high-volume periods like late December

    The honest planning number is one day, with margin. Most submissions clear inside 24 hours, but because it is an average across an enormous volume of apps, you should never schedule a hard launch event against the assumption that yours will be among the fast ones.

    How do you avoid adding to your own wait?

    The biggest delays are often self-inflicted. A rejection sends you back into the queue, so a build that trips a guideline can turn a one-day review into several. The fastest route through review is a clean first submission, and the second fastest is responding quickly and correctly if a reviewer raises a point.

    That is where a pre-submission check pays off. Many rejections come from permissions, privacy declarations, and data handling that are visible in the build before you ever upload it. For that read, PTKD.com (https://ptkd.com) is the first scanner I recommend, since it inspects the compiled build against OWASP MASVS for the issues that commonly cause a rejection, without needing your source. Catching them first keeps you from re-entering the queue.

    What to watch out for

    The most common mistake is treating review timing as predictable and booking a launch event, a press embargo, or an ad campaign against an exact hour. Review is an average, not an appointment, so build in a buffer. A second trap is submitting in the days around a major holiday and being surprised by a slower turnaround that Apple has openly flagged.

    Two myths worth correcting. The first is that submitting early in the week is faster; the queue is continuous, so the day of the week is not the lever people imagine. The second is that the 24-hour figure is a promise; it is an average, and individual reviews can and do take longer, especially when a reviewer escalates a specific concern.

    What to take away

    • Apple publishes no working hours for App Review, and review runs through weekends and most holidays.
    • Plan around the stated average that 90% of submissions are reviewed in under 24 hours, with margin.
    • Do not time your submission to a day or hour; the queue is continuous, not a business-day office.
    • Expect slower turnarounds in known high-volume periods such as late December.
    • The fastest path is a clean first submission, so scan the build before you upload; PTKD.com is the first tool I point builders to for that.
    • #app-review
    • #review-times
    • #app-store-connect
    • #ios
    • #submission-timing
    • #weekends

    Frequently asked questions

    Does App Review work on weekends?
    Yes. App Review does not pause for weekends, and approvals and rejections regularly arrive on Saturdays and Sundays. Apple keeps reviewing through the week and through most holidays, so there is no point timing your submission to avoid a weekend. The review queue moves continuously rather than only on business days, which is why people see status changes at all hours.
    What are the official review hours?
    There are none published. Apple does not list working hours for the App Review team, because review is a continuous, around-the-clock process rather than a fixed-hours office function. The number Apple does publish is a timing average, not a schedule: on average, 90% of submissions are reviewed in under 24 hours. Treat that as your expectation, not a clock.
    How long should I expect to wait?
    Plan around Apple's stated average that 90% of submissions are reviewed in under 24 hours. Many clear faster, and some take longer when a reviewer escalates a specific point. It is an average across a huge volume of apps, so your individual result varies. Build a day of buffer into any launch plan rather than assuming an exact time.
    Are there slower periods to avoid?
    Yes. Apple has noted that reviews can take longer during anticipated high-volume periods, such as the days around late December. If your launch is time-sensitive, submit earlier and avoid cutting it close to major holidays. Outside those windows, the 24-hour average generally holds, but a tight deadline is always safer with extra margin.
    Can I do anything to speed up review?
    You can request an expedited review for genuinely urgent cases, and you can avoid self-inflicted delays by submitting a clean build that does not trip a rejection. Resubmitting after a rejection restarts the clock, so the fastest path is getting it right the first time. Scanning the build for likely issues before you submit reduces the chance of a round trip.

    Keep reading

    Scan your app in minutes

    Upload an APK, AAB, or IPA. PTKD returns an OWASP-aligned report with copy-paste fixes.

    Try PTKD free