Google Play Target API Rules: Deadlines, Extensions and What Happens If You Miss Them

Every Android app carries a number called the target API level (written targetSdkVersion by developers). It tells Android which version of the system the app was built and tested for. Google Play sets a minimum each year, so that apps stay safe and behave properly on modern phones. As of November 2026 the main rule is this: new apps and app updates must target Android 16 (API level 36) or higher, and that has applied since 31 August 2026.

The rule in plain terms

Google's help page for target API levels draws a clear line between three kinds of app. Mixing them up is the most common source of confusion, so here they are separately.

• A brand-new app that has never been published must target API 36 or higher to be submitted.
• An update to an existing app must also target API 36 or higher. You cannot publish a small bug fix at an older target.
• An existing app you leave alone must target API 35 (Android 15) or higher by 31 August 2026 to stay visible to new users on newer phones.

Other device types have lower numbers. Wear OS and Android Automotive OS apps need API 35 for new apps and updates, and Android TV and Android XR apps need API 34. The same page marks permanently private apps, restricted to one organisation for internal use, as exempt.

The extension has already closed

Google offered developers who needed more time an extension to 1 November 2026. The request form lived in Play Console, linked from the policy warning on the Policy status page. That date passed two days before this post was written. The help page I checked on 3 November 2026 does not announce any further extension, so do not plan around one. If your app received a warning and you did not request an extension, check Play Console today for its current status.

What happens if you miss it

For an app that targets API 34 or lower and is not updated, the outcome is a loss of reach rather than deletion. The app stops being offered to new users whose phones run a newer Android version than the app targets. People who already installed it can keep using it and can reinstall it. People on older phones can still find it. Google also notes that this can reduce download numbers, simply because fewer new users can find the app.

For an update that targets too low, Play Console will refuse the upload. That is the more painful case in practice, because it tends to happen at the moment you urgently need a fix live. Raising the target can need real work, since Android 16 brought changes such as mandatory edge-to-edge screens and predictive back.

What is the next deadline?

Google has not announced one, as far as the official pages show on 3 November 2026. The help page lists API 36 as the latest level and no date for Android 17 (API 37). The recent pattern has been a new level each year on 31 August (API 35 in 2025, API 36 in 2026), but that is an observed pattern, not a promise, so treat any "next deadline" claim from a blog or a vendor as unconfirmed until it appears on Google's page. Related policy dates that do exist for apps targeting API 37 are covered in our Play policy checklist.

A maintenance routine that avoids the scramble

1. Open Play Console and read the Policy status page; clear any warnings.
2. Ask your developer for the app's current target level. If you cannot get an answer, that itself is a risk.
3. Book a compatibility release once a year, ahead of 31 August, not after it.
4. Keep a staging track on Play, so the update can be tested on real phones before it reaches customers.
5. Check third-party SDKs (payments, maps, analytics) for versions that support the newer target.
6. Keep the source code, signing key and Play account in your own control, so any developer can pick the work up.

Treat this routine as part of owning an app, in the same way you renew a domain name or a hosting plan. It is a small recurring cost, and skipping it is what turns a routine release into an urgent one.

That last point matters for businesses with an app from an old vendor. VS Tech Builders transfers full source code and accounts on final payment, so you are never locked out of your own update. Our app maintenance cost guide shows how annual compatibility work is usually priced, and the Play Store publishing service covers the submission side.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• Target API level requirements for Google Play apps — Play Console Help
• Upcoming Android and Google Play deadlines — Android Developers

Frequently asked questions

What API level must my app target on Google Play now?

Since 31 August 2026, new apps and updates to mobile apps must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API 35, and Android TV and Android XR apps need API 34. An existing app you do not update should target API 35 or higher to stay visible to new users on newer phones.

Can I still request a Google Play extension?

The extension Google offered ran to 1 November 2026, so it has ended. The Play Console help page I checked on 3 November 2026 announced no further extension. If your app has a policy warning, open the Policy status page in Play Console to see exactly what applies to it now.

Will Google delete my app if I do not raise the target level?

No. The app stays published. It stops being offered to new users whose devices run a newer Android version than the app targets, while existing users keep it and can reinstall it. The practical damage is lost discovery and being unable to publish updates, not removal from your Play account.

Does a private app for my own staff have to follow this?

Google lists permanently private apps, restricted to users in one organisation for internal distribution only, as an exception to the target API requirements. Even so, staff phones get newer Android versions over time, so an old target can still cause behaviour problems. Keeping internal apps reasonably current is cheaper than fixing them after they break.