ReferencePlay Console

Target API Level Requirements for Google Play

What target API level Google Play requires for new and existing apps, what happens if you miss the deadline, per-device form-factor exceptions, and how to check and raise your app's target SDK.

Reviewed August 22, 2026May change — always verify in Play Console5 min read2 official sources

Written & maintained by AppsTestLabAbout AppsTestLabHow we research

A phone screen showing an Android API level number overlay
A phone screen showing an Android API level number overlay
On this page
  1. Current requirements
  2. Per-device / form-factor requirements
  3. Exceptions
  4. What target API level, compileSdk, and minSdk mean
  5. How to check your app's target API level
  6. How to change it
  7. What to test after raising targetSdk
  8. Frequently asked questions

Every Android app publishes a ``targetSdkVersion`` (the target API level) that tells Android how your app is intended to run. Google Play enforces a minimum target API level to keep the Play Store ecosystem current with Android security, privacy, and behavior changes. This guide explains the current requirements, what breaks if you miss them, and how to raise your target safely.

Current requirements

Requirements differ for new apps and existing apps, and they are tied to Android version milestones. The key dates and targets are below.

In practice: if your app targets API 34 and a user on Android 16 visits your store listing, Google Play tells them this app is not available on your device because it was made for an older version of Android. Users who already installed your app are unaffected and can still reinstall on newer devices.

Per-device / form-factor requirements

Target API floor by form factor (2026 requirements)
Form factorNew apps & updates by Aug 31, 2026Existing apps by Aug 31, 2026
Mobile / tablet / foldableAPI 36 (Android 16)API 35 (Android 15)
Wear OSAPI 35 (Android 15)API 34 (Android 14)
Android TVAPI 34 (Android 14)API 33 (Android 13)
Android Automotive OSAPI 35 (Android 15)API 32 (Android 12L)
Android XRAPI 34 (Android 14)API 34 (Android 14)
Target API floor by form factor (2026 requirements)

Exceptions

What target API level, compileSdk, and minSdk mean

Three Gradle properties are frequently confused. They control different things.

SDK terms
TermWhat it doesWho enforces it
minSdkVersionLowest Android version your app can install onAndroid OS at install
targetSdkVersionNewest API your app assumes; opts into Android behavior changesAndroid OS + Google Play publishing
compileSdkAPI level the build tools compile againstBuild time only (no runtime effect)
SDK terms

compileSdk only affects which APIs you can use at build time and which warnings you get — it does NOT change runtime behavior. targetSdkVersion is the one Google Play checks. You should usually compile against the latest stable compileSdk, but only raise targetSdkVersion after testing.

How to check your app's target API level

  1. In Android Studio

    Open build.gradle (module: app) and read the defaultConfig block: compileSdk, minSdk, and targetSdk. Alternatively, Build > Analyze APK/AAB to inspect a built artifact's AndroidManifest.xml targetSdkVersion attribute.

  1. On the command line

    Inspect build.gradle / gradle.properties for targetSdk, or read the AndroidManifest.xml attribute android:targetSdkVersion. (./gradlew :app:properties can also surface the resolved value.)

How to change it

  1. Raise the target

    In build.gradle (module: app), update targetSdk in the defaultConfig block: ``` defaultConfig { minSdk 24 targetSdk 35 // raise this compileSdk 36 // keep at latest stable } ``` Then rebuild. Google's migration guide for the specific Android version lists the behavior changes you opt into.

What to test after raising targetSdk

Each new target API level enables behavior changes. Do not assume your app works — test.

Frequently asked questions

Frequently asked questions

Does compileSdk need to match targetSdk?

No. compileSdk can be higher than targetSdk (and usually should be, to get the latest lint warnings). compileSdk does not opt your app into behavior changes.

Will raising targetSdk break my app for existing users?

It can change behavior (stricter permissions, new splash screen, storage changes). Test on the new target before releasing an update.

My app depends on an old library — can I defer the requirement?

No. The target API level requirement applies per app regardless of libraries. Update or replace the library before raising the target.

What if I do nothing on Aug 31, 2026?

New apps/updates submitted after the deadline that do not target API 36 (or API 35 for existing apps) are rejected. Existing apps targeting API 34 or below stop being discoverable to new users on newer Android devices.

Sources & references

Official Google documentation

These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.

Get help doing this

AppsTestLab can run your testing for you

Ready to test?

5,000+ apps tested. A 99% historical approval rate. And a 100% money-back guarantee.

Tell us about your app and we'll confirm the right testing approach. One WhatsApp message to start, no complicated setup.

Guarantee applies to eligible app testing orders · Google makes the final approval decision

Chat on WhatsApp