Creator Quest Studio / Guides
ANDROID RELEASE GUIDE

Google Play API 36 deadline: what app owners need to update before August 31, 2026

Google Play changes its target API requirement on August 31, 2026. Here is what API 36 means, what happens to existing apps, and how to check an APK or AAB before your next update.

Published August 17, 2026Updated August 17, 2026

Short answer: from August 31, 2026, standard Android phone and tablet apps submitted as new apps or updates to Google Play must target Android 16, API level 36 or higher. Existing apps have a separate availability threshold: they need to target at least API 35 to remain available to new users on devices running Android versions above the app’s target level.

If you own an older Android app, that distinction matters. An app targeting API 35 is not automatically broken or removed from every device, but your next normal Google Play update will need a higher target.

What changes on August 31, 2026?

Google’s target API policy has two different tests that are easy to confuse:

Wear OS, Android Automotive OS, Android TV and Android XR have different thresholds, so a phone/tablet rule should not be blindly applied to those categories.

Does target SDK 35 mean my app stops working?

No. The target API is not the same thing as the minimum Android version your app can run on. A project can, for example, target API 36 while still supporting much older devices through its minSdk. Targeting a newer API tells Android which modern platform behaviours the app is prepared for.

The practical problem for an API 35 build is submission readiness: after the deadline, a normal phone/tablet update needs API 36.

Why changing one number is not always enough

In a modern Android project, updating targetSdk and compileSdk may be only the beginning. Android 16 introduces behaviour changes for apps that target API 36. Depending on the app, areas such as edge-to-edge UI, back navigation, large-screen behaviour, permissions, libraries and build tooling may need testing or migration.

Older projects can also be blocked by an outdated Android Gradle Plugin, Gradle wrapper, Java/Kotlin toolchain, third-party SDK or dependency. That is why a compiled APK can tell you that the target is old, but it cannot prove how difficult the source-level repair will be.

How can I check my current build?

You do not need Android Studio just to learn the basic release facts. A compiled APK or AAB contains useful release metadata including its package identity, version and target API information.

Use the free Creator Quest Studio APK/AAB checker →

The checker does not install or execute the app. It reads release information from the uploaded artifact and gives a plain-language result first, with technical details available separately.

What should I do if the build targets API 35?

  1. Keep an untouched backup of the source project and current release artifacts.
  2. Confirm the package/application ID and current versionCode before changing anything.
  3. Open and clean-build the source with a compatible toolchain.
  4. Update compile/target SDK deliberately rather than patching a compiled APK.
  5. Review Android 16 behaviour changes that apply to the app.
  6. Update incompatible dependencies or SDKs.
  7. Run the app on relevant devices/emulators and regression-test important flows.
  8. Build a fresh release AAB/APK and re-check its metadata.
  9. Use a new versionCode for the Google Play release.

Can an extension give me more time?

Google says eligible developers will be able to request an extension to November 1, 2026. Treat that as extra migration time, not as a reason to keep producing soon-to-be-stale builds.

Frequently asked questions

Is API 36 the same as Android 16?

For this requirement, yes: Android 16 corresponds to API level 36.

Does API 36 PASS guarantee Google Play approval?

No. Target API is one release-readiness check. Google Play can still reject or block a release for other technical, policy, signing, versioning, permission, billing, privacy or content reasons.

Can an APK alone tell me the exact repair cost?

No. It can reveal useful compiled metadata, but the source project is needed to determine whether the repair fits the fixed Standard or Advanced tier. If the job cannot be completed safely within either tier, Studio declines it.

Last verified: 17 August 2026

Official references

CHECK YOUR BUILD

Need the facts from your APK or AAB?

Use the free Studio checker to read the important release facts directly from the compiled artifact. You do not need Android Studio or Android development knowledge.

Analyze APK / AAB →