"In review" on Google Play means your app or update is being evaluated against Google's policies before it goes live, and it is a normal step, not a sign of a problem. The review combines automated systems with human reviewers, so the answer to "human or bot" is both: automated checks handle most of the work, and people review where a closer look is needed. It usually clears within a few days, though Google says it can take longer than seven in some cases, especially for new apps. While it is inside that window, there is nothing to do but wait.
Short answer
"In review" means Google Play is checking your app or update against its policies before publishing it. Per Google's review guidance, this is standard for every release and usually takes a few days, sometimes longer than seven for new apps and testing tracks. The review is a mix of automated analysis and human reviewers, so it is not purely a bot and not purely a person: automation does most of the screening, with human review where warranted. The status does not mean something is wrong. While you are inside the normal window, the right action is simply to wait, since resubmitting only restarts the clock.
What "In review" means
The status means Google is evaluating your submission against the Play policies before making it available to users. Every app and every update goes through this, whether it is a first release or a small change, and whether it targets production or a testing track. It is the gate between submitting and going live, not an indication that a reviewer has found anything.
Seeing it is expected. Once you submit, your release moves into review automatically, and it stays there until the evaluation completes and the app is either published or, less often, sent back for a policy issue. Reading it as a routine processing state, rather than as a verdict, sets the right expectation for what happens next. It is closer to a package that is out for delivery than to a decision that has already been made about your app.
Is it a human or a bot?
Both, working together. Google Play review relies heavily on automated systems that scan each submission for policy and security problems, such as malware, disallowed behavior, or metadata issues, and these handle the bulk of the screening quickly. On top of that, human reviewers evaluate apps where the automated analysis or the app's nature calls for a closer look.
So the honest answer is that it is not a simple choice between a person and a machine. Most of the routine checking is automated, which is part of why many reviews finish quickly, while human judgment is applied where it adds value, such as sensitive categories or borderline cases. From your side the process looks the same either way: you wait for the combined review to finish. You do not choose or influence which path your app takes, and there is no action that switches it from automated to human review.
How long does "In review" take?
Usually a few days. Google indicates that review can take some time and, in some cases, longer than seven days, with new apps, new developer accounts, and testing tracks tending toward the longer end. A status that has sat in review for a day or two is comfortably normal, and there is nothing to fix during that period.
Beyond about seven days with no change, you are past the typical window, and it becomes reasonable to check your own declarations and, if nothing explains it, to consider contacting support. Google does not promise a fixed time, so treat any figure as an average rather than a guarantee. The practical takeaway is to note when the review started so you can tell a normal wait from a genuine over-run. Without that reference point, a two-day wait can feel far longer than it is, and impatience is what leads people to resubmit and reset the clock.
In review versus other Play statuses
It helps to place "In review" among the statuses you may see, so you know where your release sits. The table below summarizes the common ones and what each means.
| Status | What it means |
|---|---|
| Pending publication | Approved and being rolled out to the store |
| In review | Google is evaluating the release before publishing |
| Update in review | An update to a live app is being evaluated |
| Published | The release is live on Google Play |
| Rejected | A policy issue was found and must be fixed |
Use the table to interpret your dashboard at a glance without guessing. "In review" and "Update in review" are the normal waiting states, "Pending publication" means the decision is already positive, and only "Rejected" calls for action beyond waiting.
Does "In review" mean something is wrong?
No. On its own, "In review" is simply the processing state every submission passes through, and it carries no implication that a reviewer has flagged anything. A long time in review is more often a queue or a completeness issue than a hidden rejection, which Google would communicate explicitly through a rejection status and a reason.
If there is a real problem, you will usually see it surface as a rejection or as an item in your Policy status or App content sections, not as a silent freeze. So rather than reading worry into a normal review wait, check those places directly if you are concerned; a clean policy status alongside an in-review release generally means the app is simply waiting its turn.
What to do while in review
For most releases, the answer is to wait and leave the submission alone. The checklist below covers the few things worth confirming so that a normal wait does not turn into a self-inflicted delay.
| Check | Action | Done? |
|---|---|---|
| Confirm it is normal | Under a few days needs no action at all | [ ] |
| Complete declarations | Finish any required App content declarations | [ ] |
| Avoid resubmitting | Do not restart the clock without a real fix | [ ] |
| Track elapsed time | Note when the review actually started | [ ] |
| Escalate only if needed | Contact support only after about seven days | [ ] |
The most common mistake is resubmitting out of impatience, which replaces the in-review release and restarts the review, lengthening the wait. Complete your declarations, note the start time, and otherwise let the review run; act only if you clearly pass the normal window.
Scan before you submit
Because review includes automated policy and security screening, a preventable security or privacy issue can turn a routine review into a rejection and another wait. Common triggers include permissions the app cannot justify, cleartext traffic, or a secret embedded in the build, all cheaper to catch before you submit.
A scanner like PTKD.com analyzes your app build and reports findings ordered by severity and mapped to OWASP MASVS, so you fix them before the release enters review. To be clear about the boundary: PTKD does not speed up Google's review or change a status. It removes the preventable findings that would turn an in-review release into a rejection and a second review cycle.
What to take away
- "In review" means Google Play is evaluating your app or update against its policies before publishing, and it is a normal step.
- The review is both automated and human: automation does most of the screening, with human review where a closer look is warranted.
- It usually takes a few days and can exceed seven in some cases, so note the start time to tell a normal wait from an over-run.
- On its own it does not mean something is wrong; a real problem shows up as a rejection or in Policy status, not as a silent freeze.
- Wait rather than resubmit, and scan with PTKD.com before submitting so a preventable issue does not turn review into a rejection.
