For Google Play target API compliance, update targetSdk—not just compileSdk. The target SDK declares the Android behavior level your app is intended to support and is the value Google Play checks for its target API requirement. The compile SDK makes Android APIs available to your code at build time. They can differ, and raising only the compile SDK does not meet a target SDK requirement.
What compileSdk and targetSdk control
| Setting | What it controls | Does it satisfy Google Play’s target API requirement? |
|---|---|---|
compileSdk |
The Android API level whose APIs are available while compiling the app. | No. Increasing it alone does not change the app’s declared target API. |
targetSdk |
The Android API level whose behavior the app opts into and is intended to support. A higher value can activate behavior changes introduced in that Android release. | Yes. This is the setting relevant to Google Play’s target API requirement. |
minSdk |
The lowest Android API level on which the app can run. | No. It is a separate compatibility decision; do not raise it merely to meet a target API requirement. |
Android’s build configuration guide says that “the value of targetSdk is not connected to the value of compileSdk.” In practical terms, compileSdk gives access to APIs during development; targetSdk affects runtime behavior and is the value that matters for Play’s target API check.
As an Amazon Associate I earn from qualifying purchases.
Google Play target API requirements as of October 4, 2026
Google Play’s target API requirement page sets different thresholds according to the release type and app form factor. For the general Android app category, the thresholds effective August 31, 2026 are:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute| Release or listing situation | General Android threshold | What the threshold applies to |
|---|---|---|
| New app or app update | Android 16, API level 36 or higher | Submission to Google Play. |
| Existing app | Android 15, API level 35 or higher | Remaining available to new users on devices running an Android version above the app’s target API. |
Those are not interchangeable rules: the API 36 threshold is for new apps and updates, while API 35 is the general existing-app availability threshold. The page lists separate thresholds for Wear OS, Android Automotive OS, Android TV, and Android XR: new apps and updates generally require API 35 for Wear OS and Automotive OS, and API 34 for TV and XR. Existing-app availability cutoffs also differ by form factor, so check the current policy page for the relevant category rather than applying the general Android threshold to every app.
#1 Best Overall
The policy page also says developers who need more time can request an extension to November 1, 2026. Check the current Play Console and policy page for the request process and availability.
How to update the app correctly
- Find the target setting in the app module. Check the module’s Gradle configuration for
targetSdkand verify the target API level in the built artifact. Google Play notes that the target can be configured in Gradle or through theandroid:targetSdkVersionmanifest attribute. - Choose the applicable Play threshold. Confirm whether this release is a new app, an update, or an existing listing, and identify the app’s form factor. Set
targetSdkto the applicable threshold. - Update compileSdk when the code needs newer APIs. Set it to a level that supports the APIs the app uses, and check compatibility with the Android Gradle Plugin, Android Studio, and libraries. It may be higher than, equal to, or lower than targetSdk; changing it does not substitute for changing targetSdk.
- Review target-version behavior changes. Read the Android platform behavior changes relevant to the target release, including permission and privacy changes. A successful build alone does not show that the app works correctly under the new target behavior.
- Test real user flows and dependencies. Exercise the app on current Android devices or emulators, including flows that depend on permissions and third-party SDKs. Apps targeting older API levels can receive backward-compatibility behavior on newer Android versions, so validate the behavior after raising the target.
Why a target SDK update needs testing
Changing targetSdk is not just a declaration for Play. Android can apply behavior changes associated with the newly targeted platform level, which may affect the app even when compileSdk has not changed. Review the applicable changes in the Android device compatibility overview and test the affected app paths before release. Raising minSdk is not the remedy for target API compliance; it changes which older devices can run the app.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
