# Google Play target API level 2026: the Android 16 (API 36) requirement

> Since August 31, 2026, new apps and app updates on Google Play must target Android 16 (API level 36), or API 35 for Wear OS and Android Automotive OS and API 34 for Android TV and Android XR, and existing phone apps that target below API 35 stop being available to new users on newer Android versions.

Uptika team · Published: 2026-11-05 · Last updated: 2026-11-05 · https://uptika.app/en/guides/google-play-target-api-level

## What is the target API level requirement?

Every Android app declares a `targetSdkVersion`, the target API level, which tells Android which version's behaviour the app was built for. Google Play sets a minimum target so users get the security, privacy and performance changes of recent Android versions. The target is not the same as `minSdkVersion`: an app targeting API 36 can still run on older Android versions down to its minimum.

## What are the rules in 2026, by device type?

Two rules apply at once. One decides whether you can **submit** a new app or update; the other decides whether an **existing** app stays available to new users on newer devices.

| Form factor | New apps and app updates, since August 31, 2026 | Existing apps, to stay available to new users on newer Android versions |
|---|---|---|
| Phones, tablets and Android Auto | Android 16 (API 36) or higher | Android 15 (API 35) or higher |
| Wear OS | Android 15 (API 35) or higher | Android 14 (API 34) or higher |
| Android Automotive OS | Android 15 (API 35) or higher | Android 12L (API 32) or higher |
| Android TV | Android 14 (API 34) or higher | Android 13 (API 33) or higher |
| Android XR | Android 14 (API 34) or higher | Android 14 (API 34) or higher |

The only exception Google lists is "Permanently private apps that are restricted to users in a specific organization and intended for internal distribution only."

> Status on November 5, 2026: Google let developers request an extension to November 1, 2026. That date has passed, and the help page mentions no later extension. If you were relying on one, the requirement applies to you now.

## What happens if my app targets an older API level?

- **Updates are blocked.** A new app or update below the submission target is not accepted.
- **New users on newer devices lose access.** An existing app below the availability target is shown only to people whose devices run the same Android version as the app's target, or older.
- **Existing users are not affected.** Google says people who installed the app before "will still be able to discover, re-install, and use the app on any Android OS version that your app supports."
- **Downloads may fall.** Google notes it "may impact your app download levels" because new users on newer devices cannot find or install it.
- **Deep links show a message.** A user on a newer device who opens your store link is told the app is "not available to install on their device because it was made for an older version of Android."

For existing apps, the consequence Google describes is limited availability to new users, not removal of the listing. If you want to stop serving an app you will not update, even to new users on older devices, Google points to unpublishing it.

## How do I check and change targetSdkVersion?

1. Open your app module's Gradle file. Google's guide says you can "confirm or change the current value of targetSdkVersion in your app's Gradle file", or use the `android:targetSdkVersion` attribute in the manifest's uses-sdk element.
2. In the Gradle Kotlin DSL the value sits in the `defaultConfig` block, for example `targetSdk = 36`.
3. Work through the official behavior changes list for each version you move past (Android 13, 14, 15 and 16 are linked from Google's migration guide); some changes only apply once your app targets that version.
4. Test on a device or emulator running the newest Android version, then build a new release and upload it to every track you use.
5. After review, open **Policy status** in Play Console (select the app, left menu). Non-compliant apps receive a warning there and in Notifications.

## How do I avoid this next year?

The last two requirements took effect on August 31, 2025 (API 35) and August 31, 2026 (API 36). Plan the next target bump into an early-summer release each year, so the update is reviewed before the deadline rather than during it. A rejected update for a target level is an ordinary rejection; the [Google Play rejection reasons guide](https://uptika.app/en/guides/google-play-rejection-reasons) explains how to resubmit, and the [metadata policy guide](https://uptika.app/en/guides/google-play-metadata-policy) covers the listing checks worth running in the same release.

## Where Uptika fits

Uptika does not inspect your app bundle or its target SDK. What it shows is the effect on the store side: Günlük ping (daily brief, paid plans) reports keyword rank moves and listing changes each day, so a drop after a release or availability change is visible quickly. [Create an account](https://uptika.app/app/#/?signup=1) to track your Google Play listing.

## Questions

### What target API level does Google Play require in 2026?

From August 31, 2026, new apps and app updates must target Android 16 (API level 36). Wear OS and Android Automotive OS apps must target API 35, Android TV and Android XR apps API 34. Existing phone apps must target at least API 35 to stay available to new users on newer Android versions.

### What happens if my app targets an old API level?

An update that targets below the requirement cannot be submitted. An existing app that targets API 34 or lower is only shown to new users whose devices run the same or an older Android version. People who already installed it keep it and can reinstall it.

### Can I request an extension?

Google allowed extension requests until November 1, 2026, through a form on the warning in the Policy status page. That date has passed, and Google’s help page mentions no further extension, so update the target now.

### Does the requirement apply to Wear OS apps?

Yes, with a lower level. New Wear OS apps and updates must target Android 15 (API level 35) since August 31, 2026; existing Wear OS apps need API 34 or higher to stay available to new users on newer versions.

### Are any apps exempt?

Google lists one exception: permanently private apps that are restricted to users in a specific organization and intended for internal distribution only.

## Sources

- [Target API level requirements for Google Play apps (Play Console Help)](https://support.google.com/googleplay/android-developer/answer/11926878)
- [Meet Google Play’s target API level requirement (Android Developers)](https://developer.android.com/google/play/requirements/target-sdk)
- [Check your app’s policy status (Play Console Help)](https://support.google.com/googleplay/android-developer/answer/9842754)

---

Uptika is an ASO and store-intelligence tool for the App Store and Google Play. https://uptika.app/en