Skip to the scanner
Preflight

Apple rejected 2,093,244 submissions in 2025

Find out before the reviewer does.

Paste your listing, answer a few questions about the app, and see the rejection risks, each with the policy clause behind it.

Scan a submission

Which store are you submitting to?

Your listing

The words and images that go on the store page.

Play allows 80 characters.

Apple allows 30 characters.

Apple allows 100 characters in total, comma separated.

Apple allows 170 characters.

Paste it exactly as you will submit it, line breaks and any HTML included. Both matter.

About your app

Most rejections are not about the listing at all. These are the ones we can check without your build.

We fetch it and check that it loads. A policy URL behind a certificate error is a rejection.

Your manifest optional

Several Android permissions need a separate Play declaration, and requesting one without filing it is a rejection nothing in your listing would reveal. Add your AndroidManifest.xml and we will check for them.

The source file from your project, not a built app. It is read here in your browser — only the permission names are sent, never the file.

Your images and your manifest are read in your browser and never uploaded — only their measurements and the permission names leave this page. Your listing text is sent to our server, because we have to read it to check it.

What we actually check

The listing

Character limits, promotional wording the stores forbid, HTML that silently breaks your description, icon and screenshot dimensions, exact aspect ratios, and the alpha-channel rule that runs in opposite directions for the icon and the feature graphic.

The declarations around it

We fetch your privacy policy and support URLs and check they really load — a certificate error and a 404 are different problems. The rest we ask you, and then check your answers against the policy and against each other: accounts that can be created but not deleted, a login wall with no way in for a reviewer, data you collect but did not declare. We do not open your build, so these are your declarations, not an inspection of the app — and a contradiction between them is a rejection waiting to happen.

What we could not check

Named every time. Leave the icon out and the report says the icon was not checked, never that the icon is fine. A gap you know about is worth more than a clean result you cannot trust.

Why Apple is free and Play is not

Because we have earned the right to charge for one of them, and not for the other.

The Play checks come from rejections and warnings measured on our own submissions: the single line break that silently disappears, the price word that costs you featuring without costing you approval, the version code that is burned the moment Play accepts it. None of those are in the documentation.

The Apple checks come from Apple's published guidelines. We have not submitted to Apple, so we have measured nothing there. That is a real difference in what a check is worth, and charging the same for both would be pretending otherwise. Apple stays free until it is earned, and every Apple report says on its face where its checks came from.

What that distinction means in practice →

Your screenshots never leave your browser

Your screenshots, icon and feature graphic are measured on your own device. Your browser reads their dimensions, file size and colour type, and sends us only those numbers.

Your listing text is sent to our server, because we have to read the actual words to check them, and it is going to be public on the store in any case. We would rather tell you exactly where that line falls than claim a tidier one.