Google Play App Rejection Rate 2026: The Real Numbers

Google Play rejects apps constantly. In 2025 it reviewed 21,461,250 app submissions and rejected 1,692,467 of them. What Google has never published is a percentage — there is no official figure labelled "the Google Play rejection rate". This post takes the counts Google does print, works out the ratio they imply, and maps the five stages where a submission or a live app can actually be stopped, with the official Play Console page for each stage. Every figure below comes from Google's own transparency reports and security blog, read on 7 October 2026.

What is Google Play's app rejection rate in 2026?

Google does not publish a rejection rate as a percentage. What it publishes once a year are the two counts needed to calculate one. The 2025 Google Play Annual Transparency Report, published 31 March 2026, reports 21,461,250 app submissions reviewed and 1,692,467 rejected. Rejected divided by reviewed is 7.89%. The same calculation on the 2024 report — 1,955,305 rejections out of 19,292,647 reviews — gives 10.13%.

Two cautions before you quote that figure. Both ratios are platform-wide, covering every developer in one calendar year: Google does not define a cohort of first-time apps, so neither 7.89% nor its complement of roughly 92% is the probability that your own submission passes. And the unit is a submission, not an app — a team that ships updates weekly adds several submissions to the same year's count.

The counts Google publishes, and what each one measures

Google prints these numbers once a year in the Google Play Annual Transparency Report. The percentages are our calculation; Google prints the counts only.

Metric	2024	2025	What it counts
App submissions reviewed	19,292,647	21,461,250	The denominator: every app submission Google reviewed, globally
App submissions rejected	1,955,305	1,692,467	Submissions that did not pass review
Rejection ratio (our calculation)	10.13%	7.89%	Rejected ÷ reviewed; Google never prints this percentage
Approved after rejection	827,995	806,795	Submissions accepted after the developer fixed the issue and resubmitted
Apps removed after publication	3,909,324	2,012,981	Live apps taken down for terms-and-conditions violations
Terminated developer accounts	154,881	125,550	Accounts terminated during the year
Complaints (appeals) received	285,980	234,639	Developer complaints about removal decisions
Initial decision reversed	15,625	11,633	Complaints Google upheld after challenging the first decision
Median time to action a complaint	< 1 day	< 1 day	Google's own median, measured in days
Terminated accounts restored	1,559	12,569	Terminations reversed by Google

Source: Google Play Annual Transparency Report for 2024 (published 31 March 2025) and for 2025 (published 31 March 2026). Both reports describe their coverage as global.

Why Google's other "rejection" numbers are not rejection rates

Google's security blog publishes a second, separate series every year, and it is the one most articles quote. For 2025 Google wrote that it "prevented over 1.75 million policy-violating apps from being published on Google Play and banned more than 80,000 bad developer accounts that attempted to publish harmful apps." For 2024 the same post series reports 2.36 million apps prevented from publication and more than 158,000 accounts banned. The 2025 post also states that Google Play runs over 10,000 safety checks on every app it publishes, and that it prevented over 255,000 apps from getting excessive access to sensitive user data.

That series and the transparency report series measure different things. The security blog counts apps blocked from ever being published and accounts banned for harmful apps; the transparency report counts review decisions on submissions, including ordinary policy rejections that have nothing to do with malware. Dividing 1.75 million by a reviewed-submissions figure produces a number Google never asserted, and Google publishes no mapping between the two series. Keep every figure attached to its source and its year.

Where an app actually gets stopped, stage by stage

A "rejection" can land at five different points, and the fix differs at each one.

Stage	What Google does	Documented in
1. Before submission — release errors	The review summary shows an "Errors summary"; Google states "You can't publish your app until errors have been resolved." Warnings alone do not block publishing.	Publish your app, Play Console Help
2. The target API level gate	Since 31 August 2026, new apps and app updates must target Android 16 (API level 36) to be submitted, with an extension available to 1 November 2026. Existing apps must target API level 35 to stay available to new users on newer devices.	Target API level requirements
3. In review — rejected	Update status becomes "Update rejected" (or "App rejected" for a first publish out of Draft). Google allows you to "fix the issue and resubmit, or you can submit an appeal." Standard reviews can take up to 7 days, longer in exceptional cases.	Publish your app, Play Console Help
4. After publication — rejected, removed, suspended	Policy status shows the enforcement. Rejected: "the last version that you successfully published is still available on Google Play." Removed: unavailable until a compliant update is submitted. Suspended: unavailable, with an Appeal button shown.	Check your app's policy status
5. Account level — termination	The account itself is terminated. Google accepts one appeal per enforcement action and can only respond to appeals in Chinese, English, Japanese and Korean.	My app has been removed from Google Play

What the removals are actually about

Of the 2,012,981 apps removed from Google Play in 2025, the largest single category was data protection and privacy violations. Google published a top-five list for 2025 and a top-ten list for 2024, so the two columns are Google's own categories and do not match line for line.

Violation category	2024 removals	2025 removals
Data protection and privacy violations	2,151,553	876,316
Outside scope of platform service	644,888	696,355
Scams and/or fraud	335,469	100,658
Protection of minors	85,476	65,153
Data defect	590,938	not in 2025 top five

For submissions rather than live apps, Google names its own common rejection reasons: its expanded pre-review checks "help catch common reasons for rejection, like improper usage of credentials or permissions and broken privacy policy links." Developers also report a third group of reasons in the Google Play Developer Community — reviewers unable to log in because the app access credentials are missing or expired, broken functionality after an update, and "app loads, but not responsive" notices. Those are community reports of reviewer feedback, not a published Google list of rejection reasons, so treat them as patterns to check rather than official categories.

How often do appeals succeed?

Less often than a fix-and-resubmit, on Google's own numbers. In 2025 developers filed 234,639 complaints about removals; Google reversed the initial decision in 11,633 cases, upheld it in 130,761, and recorded no decision in 91,504 (withdrawn, no action needed, or resolved by the developer). Among complaints that received a substantive decision, 11,633 out of 142,394 were reversed — 8.2%. The 2024 figures give 15,625 reversals out of 188,528 decided complaints, or 8.3%. The three outcome buckets fall 741 short of the 2025 total, presumably complaints still open at publication.

The better news sits in a different row: 806,795 submissions were approved after rejection in 2025, which is 47.7% of that year's rejection count; in 2024 it was 827,995, or 42.3%. Google's own footnote explains the mechanism — "Developers can address the issues resulting in the app rejection and resubmit without an appeal." Google does not state whether those approvals match up with the same year's rejections, so read it as an order-of-magnitude signal rather than a conversion rate: this is our analysis, not a Google statistic.

Terminated accounts show the same pattern. Google restored 12,569 terminations in 2025 against 125,550 terminations — about 10% — while 2024 saw 1,559 restorations against 154,881 terminations, about 1%. Again Google does not say whether a restoration belongs to a termination from the same year, and restorations may trail terminations by months.

The practical reading: a rejection notice is a request to change something, not a verdict on your app. Fix what the notice names, resubmit, and keep the appeal in reserve for the case where the notice is factually wrong.

What to do if your submission is rejected

Google's resubmission procedure is specific, and skipping a step is what makes the second rejection look like a pattern:

1. Read the enforcement message and the notification emails for the exact policy cited, then check that the rest of the app still complies — "additional enforcement could occur if there are further policy violations."
2. Fix the app and update all release types, not just production: open, closed and internal tracks.
3. Upload the compliant bundle to every track and deactivate the non-compliant bundles. Google warns that if you fail to deactivate them, "your attempt to resubmit your app will fail, and live versions of your app bundle(s) may be removed from Google Play."
4. Roll out the compliant release to 100% on each affected track, then submit the changes for review from Publishing overview.
5. Only if the notice is wrong: appeal. Google allows one appeal per removal, suspension or other enforcement action.

Two related problems get confused with policy enforcement constantly. A production-access refusal after closed testing is an eligibility decision, not a policy enforcement — we explain the difference in why Google Play rejects production access, and it is the most common mix-up we see in our own support records across 1,500+ closed-testing campaigns (our observation from those records, not Google data). And a rejected or slow review is often a quality signal rather than a policy one: the metrics that decide it are in Android vitals: what the numbers mean and what to fix first. Before every submission, run the pre-launch report and confirm your developer verification details are current, because account-level problems stop releases that no code change can fix.

Frequently Asked Questions

Does Google publish an official rejection percentage?

No. Google publishes counts — submissions reviewed, submissions rejected, apps removed, accounts terminated — in its annual Google Play Annual Transparency Report, but it does not print a percentage called a rejection rate. The 7.89% figure for 2025 is a calculation from Google's counts, not a number Google states.

Is 7.89% my app's chance of being rejected?

No. It is a platform-wide ratio for one calendar year across all submissions, including updates from established developers. Google does not define a first-attempt cohort, so neither the ratio nor its complement is a probability for any individual app.

Do I have to appeal after a rejection, or can I just fix it?

You can usually just fix it. Google's own footnote on the transparency report says developers "can address the issues resulting in the app rejection and resubmit without an appeal." Appeals are for when the decision itself is wrong, and Google allows only one appeal per enforcement action.

Does a rejection make my live app unavailable?

Not by itself. On the Policy status page, a rejected app keeps the last version that was successfully published on Google Play. A removed app is unavailable until you submit a compliant update, and a suspended app is unavailable until an appeal succeeds.

Why do two Google reports give different numbers for the same year?

Because they count different things. The transparency report counts review decisions on app submissions; the security blog counts apps prevented from being published and accounts banned for harmful apps. Google publishes no conversion between the series, so they should never be combined into a single rate.

What is the single biggest category of removals?

Data protection and privacy violations: 876,316 apps removed globally in 2025 and 2,151,553 in 2024, out of total removals of 2,012,981 and 3,909,324 respectively. The drop year over year is large, and Google does not publish an explanation for it.

Sources

• Google Play Annual Transparency Report 2025 (PDF, published 31 March 2026)
• Google Play Annual Transparency Report 2024 (PDF, published 31 March 2025)
• Keeping Google Play & Android app ecosystems safe in 2025, Google Security Blog
• How we kept the Google Play & Android app ecosystems safe in 2024, Google Security Blog
• Publish your app, Play Console Help
• Check your app's policy status, Play Console Help
• My app has been removed from Google Play, Play Console Help
• Target API level requirements for Google Play apps, Play Console Help

Data read and verified on 7 October 2026.