Google Play target API level deadline checker
Enter your app's targetSdkVersion, whether you are publishing an update or leaving an existing app, and the device type. The checker says whether Google Play accepts it, since when, whether an extension applies and what to change in Gradle, using Google's pages checked on 11 November 2026.
Updated
Phones and tablets, new app or update, 11 Nov 2026
Blocked
Apps for Phones and tablets have had to target API 36 or higher since 31 Aug 2026, and the extension to 1 Nov 2026 has ended. Raise targetSdk to 36, rebuild and upload.
- Fail · Meets the new-app and update level (API 36)API 34 is 2 levels short
- Fail · Meets the existing-app level (API 35)API 34 is 1 level short
Gradle change
// app/build.gradle.kts
android {
compileSdk = 36
defaultConfig {
targetSdk = 36
}
}
// then test the behaviour changes for Android 16 and the versions in between- Device type
- Phones and tablets
- Your targetSdk
- Android 14 (API 34)
- Needed for new apps and updates
- Android 16 (API 36)In force since 31 Aug 2026.
- Needed for existing apps to stay available to new users on newer devices
- Android 15 (API 35)
- Extension
- Ended 1 Nov 2026Requested in Play Console from the policy warning. Not given automatically.
- Next required level
- Not yet published on Google's pagePlanning estimate, ours not Google's: one API level higher each year, so API 37 (Android 17) around August 2027. Confirm on the page below.
| Device type | New apps and updates | Existing apps, to stay available to new users on newer devices | Your API 34 |
|---|---|---|---|
| Phones and tablets | API 36 | API 35 | below new / below existing |
| Wear OS | API 35 | API 34 | below new / meets existing |
| Android Automotive OS | API 35 | API 32 | below new / meets existing |
| Android TV | API 34 | API 34 | meets new / meets existing |
| Android XR | API 34 | API 34 | meets new / meets existing |
- Permanently private apps restricted to one organisation and not distributed publicly are exempt from these requirements.
- Changing targetSdk is not just a number: test the behaviour changes for each level between 35 and 36 (Google lists them per Android version).
App Maintenance Plans & Pricing: from ₹20,000 / $210 a month
Play moves the target level every year. A maintenance plan keeps targetSdk, libraries and behaviour changes current.
How does the checker decide?
Google Play sets a minimum targetSdkVersion in two places. New apps and updates must meet a level to be submitted at all: since 31 Aug 2026, API 36 for phones and tablets, API 35 for Wear OS and Android Automotive OS, and API 34 for Android TV and Android XR. Existing apps that are not updated are held to a lower level: below it they stay installed for current users but are not offered to new users on devices running a newer Android than the app's target.
You enter your targetSdk, whether you are publishing an update or leaving an existing app alone, the device type and a date. The tool compares your level to the row for that device type and tells you whether it is accepted, when it stops being accepted, and whether an extension applies.
The extension Google offered runs to 1 Nov 2026. It is requested from the policy warning in Play Console, so it is never automatic, and after that date the checker says it has ended. Google has not published the level after these on the page checked, so the next-level row is an estimate labelled as ours.
new app or update: accepted if targetSdk >= level for the device type existing app: available to new users on newer devices if targetSdk >= existing-app level extension: until 1 Nov 2026, if requested
Which target API level does each device type need?
| Device type | New apps and updates | Existing apps stay available to new users on newer devices |
|---|---|---|
| Phones and tablets | Android 16 (API 36) | Android 15 (API 35) |
| Wear OS | Android 15 (API 35) | Android 14 (API 34) |
| Android Automotive OS | Android 15 (API 35) | Android 12L (API 32) |
| Android TV | Android 14 (API 34) | Android 14 (API 34) |
| Android XR | Android 14 (API 34) | Android 14 (API 34) |
How to check your target API level against Google Play
- 1Find your targetSdkOpen app/build.gradle(.kts) and read targetSdk in defaultConfig. If it is missing, check the manifest's uses-sdk element.
- 2Choose update or existingPick publishing a new app or update if you plan to upload a build. Pick existing app if you only want to know about availability to new users.
- 3Pick the device type and datePhones and tablets use the highest level. Wear OS, Automotive, TV and XR use lower ones. Leave the date as today or set a future date.
- 4Read the result and plan the bumpIf it is below the level, copy the Gradle change, then test the behaviour changes for every Android version between your level and the new one.
Frequently asked questions
Is targetSdk 34 still accepted on Google Play?
Can I still get an extension for the target API deadline?
What happens to an app that does not update its target API level?
Do Wear OS, Android TV and Automotive apps need the same level as phones?
Are private enterprise apps affected by the target API rule?
What target API level comes after the current one?
Sources
- Android Developers, Meet Google Play's target API level requirement (checked 11 Nov 2026)
- Play Console Help, Target API level requirements for Google Play apps (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter