targetSdk and compileSdk often appear next to each other in an Android project, but they answer different questions.
What is compileSdk?
compileSdk tells the Android build system which Android SDK APIs are available when compiling the project. Android’s current Android 16 setup guidance uses compileSdk = 36 to compile against Android 16 APIs.
What is targetSdk?
targetSdk tells Android which platform behaviour level the app is prepared to target. Raising it can opt the app into newer platform behaviour changes that need testing.
Which value does the Google Play deadline focus on?
The Google Play target API requirement is specifically about the app’s target API level. For standard phone/tablet new apps and updates submitted from August 31, 2026, that means target API 36 or higher.
Can compileSdk be 36 while targetSdk is 35?
Yes, technically a project can compile against a newer SDK while still targeting an older API. That can be useful during migration, but it does not satisfy a Play requirement that specifically requires target API 36 for the next standard submission.
Why do migrations usually update both?
A normal Android 16 migration first gets the project compiling against the newer SDK, then raises the target and tests the behaviour changes that apply to apps targeting Android 16. Doing both in a controlled sequence makes failures easier to understand.
What about minSdk?
minSdk is different again. It controls the oldest Android API level the app declares it can run on. Raising targetSdk to 36 does not automatically mean the app can only run on Android 16 devices.
How can I see the target in a compiled build?
A compiled APK or AAB contains release metadata that can reveal the target API and other identity/version facts.
What still needs source-level testing?
- Gradle and Android Gradle Plugin compatibility.
- Java/Kotlin and dependency compatibility.
- Android 16 behaviour changes such as edge-to-edge and predictive back where relevant.
- Large-screen behaviour where applicable.
- Native 16 KB compatibility when native libraries are present.
- Install, launch and regression testing.
Last verified: 17 August 2026
Official references
- Set up the Android 16 SDK
- Android 16 behaviour changes for target API 36+
- Google Play target API requirements
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 →