Yes, Google Play reviews apps on weekends, because the review process is largely automated and runs continuously rather than stopping for weekends. Most submissions are processed by automated systems around the clock, so a Saturday or Sunday submission is often reviewed just like a weekday one. The exception is when your app is escalated to human review, which can be slower on weekends and holidays. Google states reviews can take up to 7 days, and longer in exceptional cases, so a weekend submission that is not decided immediately is usually still within the normal window.
Short answer
Google Play review is mostly automated and runs on weekends, so submissions are typically processed continuously. Per Google's publishing guidance, reviews can take up to 7 days and occasionally longer, so weekend timing rarely changes the outcome for automated reviews. If your app is flagged for human review, weekends and holidays can add delay, because human reviewers are less available then. New accounts and first submissions tend to take the longer end of the range. Do not resubmit to speed things up, since that can restart the review, and contact Google Play support only if you pass the normal window with no update.
Does Google Play review on weekends?
Yes. Because Google Play review is largely automated, it does not pause for weekends the way a purely human process would. Automated systems evaluate submissions continuously, so an app you submit on a Friday night or over the weekend is generally entering the same pipeline it would on a weekday, and many weekend submissions are reviewed and published without any special delay. The calendar day you submit on is not, by itself, a strong predictor of how long review takes.
That said, weekend submission is not a guarantee of a weekend decision. Review time varies with the app, the account, and whether anything triggers a closer look, so a submission can still take days regardless of when you send it. The useful mental model is that automated review runs all week, so weekends do not stop it, but the normal range of review times still applies, and you should plan around that range rather than expecting an instant weekend turnaround.
Bot vs human review
Most Google Play reviews are handled by automated systems, with human reviewers involved for apps that are flagged, sensitive, or otherwise escalated. The automated layer is what runs continuously, including weekends, and it decides the majority of straightforward submissions quickly. This is why a typical app can be reviewed at any time, day or night, without waiting for staff to be at their desks.
Human review is the part that weekends and holidays affect. When an app is escalated, for example because it touches a sensitive permission or trips a policy signal, a person may need to evaluate it, and human reviewers are less available on weekends and holidays. So the practical distinction is that an automated review is largely time-of-week independent, while an escalated, human-reviewed app can sit longer if it lands over a weekend. You usually cannot tell in advance which path your app takes, which is why the overall range matters more than the submission day.
Holiday delays
Holidays can lengthen Google Play review times, more so than ordinary weekends. Two things combine around major holidays: a surge in submissions as developers rush releases before time off, which increases the queue, and reduced availability of human reviewers for anything escalated. Together these can push review times toward the longer end of the normal range or beyond it, even though automated review continues to run.
Plan around this by submitting earlier rather than right before a major holiday if your release timing matters. If you submit close to or during a holiday period and the review takes longer than usual, that is often the reason, and it does not mean something is wrong with your app. Treat holiday timing as a scheduling consideration: give yourself a buffer, avoid last-minute submissions before a holiday, and expect the range to stretch rather than assuming a problem when it does.
Normal vs abnormal waiting
Knowing the normal range keeps you from escalating too early. Google states that reviews can take up to 7 days, and occasionally longer in exceptional cases, so anything within that window is normal even if it feels slow. In practice many reviews finish much faster, from a few hours to a couple of days, but the up-to-7-days figure is the benchmark for what counts as normal rather than a delay.
Waiting becomes abnormal when you pass the normal window with no decision and no request for information. A first submission on a new account tends to take the longer end, so factor that in before concluding something is wrong. If you are well within the window, the right action is to wait; if you have clearly exceeded it with no update, that is when contacting support is reasonable. Judging your wait against the range, rather than against your hopes, tells you which situation you are in.
Does resubmitting reset the review?
Yes, resubmitting generally starts a new review, which is why repeatedly resubmitting to hurry things along usually backfires. When you upload a new version, that version enters review as a fresh submission, so canceling and resubmitting can put you back rather than advance you. An app that was progressing through review does not move faster because you resubmitted; it may simply begin again.
The practical rule is to wait rather than resubmit while a review is in progress and within the normal window. Only submit a new version when you actually have a change to make, such as fixing an issue the review raised, not as a way to prod the queue. If you are anxious about the wait, checking the status in Play Console is fine, but resubmitting a materially identical build is more likely to extend your wait than shorten it.
When and how to escalate
Escalate only after you have exceeded the normal window with no decision and no request for more information. Once you are clearly past the up-to-7-days benchmark, or the review has stalled well beyond what is typical for your case, contact Google Play developer support through the Help option in Play Console, describe the situation, and provide your app and submission details. Support can look into a review that has genuinely stalled.
Before escalating, confirm the basics: that the app is actually in review rather than held by Managed Publishing or waiting on an incomplete section, and that you have not just submitted and expected an instant result. A calm, factual support request with your package name and timeline is more effective than repeated messages. Escalation is the right step for a real overrun, but for a wait that is still within the normal range, patience resolves most cases without any action.
Review timing at a glance
Comparing the two review paths clarifies where weekends matter. The table below sets them side by side.
| Aspect | Automated review | Human review |
|---|---|---|
| Runs on weekends | Yes, continuously | Slower on weekends and holidays |
| Typical speed | Minutes to hours | Days when escalated |
| When it applies | Most submissions | Flagged or sensitive apps |
| Holiday impact | Minimal | Can lengthen noticeably |
Read the table to set expectations: an automated review is largely independent of the day, while an escalated one can be affected by weekends and holidays.
How long have you waited?
Matching your wait to the normal range tells you whether to wait or act. The table below maps common cases.
| Time waited | Normal? | What to do |
|---|---|---|
| A few hours to about 2 days | Normal | Wait; do not resubmit |
| Up to 7 days | Within Google's window | Keep waiting |
| First app or new account | Expect the longer end | Wait patiently |
| Over 7 days with no update | Longer than typical | Contact Play Console support |
Read your situation against the table. Only the last row calls for escalation; the others call for patience rather than resubmitting.
Use the wait to secure your build
A review wait, weekend or not, is time you can put to use on the build itself rather than refreshing the status page. Whether review takes an hour or several days, the quality and security of what you submitted is worth confirming, especially since a security or policy issue can turn a slow review into a rejection.
A scanner like PTKD.com analyzes your build and reports issues such as risky third-party code, leaked keys, and over-broad permissions by severity, mapped to OWASP MASVS, so you can catch problems during the wait rather than after a rejection. To be clear about the boundary: PTKD does not review your app for Google, speed up the queue, or change your review time. It helps you use the wait to make sure the build you submitted is sound.
What to take away
- Google Play reviews on weekends because the process is largely automated and runs continuously, so weekend submissions are usually processed normally.
- Most reviews are automated and time-of-week independent, while apps escalated to human review can be slower on weekends and holidays.
- Holidays can lengthen review times through higher submission volume and reduced reviewer availability, so submit earlier if timing matters.
- Reviews can take up to 7 days and occasionally longer, so treat that as the normal window, expect the longer end for new accounts, and do not resubmit to hurry it.
- Escalate to Play Console support only after clearly exceeding the window, and use the wait to scan your build with PTKD.com.
