Google Play requires new apps and app updates to target Android 16 (API level 36) or higher, a rule in force since August 31, 2026. Wear OS and Android Automotive OS apps need API level 35, and Android TV and Android XR apps need API level 34. Existing apps you don’t update only need API level 35 to stay visible to new users.
The current Google Play target API level, by app type
The Google Play target API level depends on what kind of app you ship. Google’s Play Console Help page lists one level for phones and tablets and lower levels for other form factors.
| App type | Minimum target for new apps and updates |
|---|---|
| Phone and tablet apps | Android 16 (API level 36) |
| Wear OS | Android 15 (API level 35) |
| Android Automotive OS | Android 15 (API level 35) |
| Android TV | Android 14 (API level 34) |
| Android XR | Android 14 (API level 34) |
Google offered extensions to November 1, 2026 for developers who needed more time. As I write this in November 2026, that date has passed, so treat API level 36 as a hard floor for anything you upload.
The only exception on the Android Developers requirement page is for permanently private apps restricted to one organization and meant for internal distribution only.
What the rule means for your situation
The rule hits differently depending on whether you’re shipping something new or leaving an old listing alone. Here are the cases from Google’s page.
| Your situation | What you need |
|---|---|
| Publishing a brand-new app | Target API level 36 |
| Uploading an update to an existing app | Target API level 36 |
| Existing app, no update planned | Target API level 35 to stay visible to new users |
| Existing app targeting API level 34 or lower | Only shown to new users on devices running that Android version or older |
| Private internal app for one organization | Exempt |
People miss the third row. A B4X forum thread puts the common view well: if you don’t need to update your app, you don’t need to worry yet. True for submission. Meanwhile an untouched app slowly loses reach.
What happens if you miss the requirement
Missing the target API level blocks the upload itself. Play Console won’t accept a new app or update below API level 36.
For apps already live, the penalty is visibility. Google says apps that target API level 34 or lower are only available to new users on devices running the same Android version or lower. A phone on a newer Android won’t see the listing.
People who already installed your app can still discover, re-install and use it, according to Google.
Target API level vs minimum SDK
The target API level and the minimum SDK are two separate settings, and Google Play’s rule applies only to the target. The <uses-sdk> reference defines them like this:
- minSdkVersion is the lowest API level the app can run on. Android blocks installation on anything older.
- targetSdkVersion is the API level the app targets. It tells the system you tested against that version, so Android doesn’t switch on old compatibility behaviours.
If targetSdkVersion is not set, it defaults to minSdkVersion. An app with a low minimum and no explicit target fails the rule.
Apps built with webtoapkfree.com require Android 8.0 or newer, which is minimum SDK 26 (per its website to APK guide). That number decides who can install the app, not whether Google Play accepts the upload.
How to change the target API level in your project
You set the target API level in your app’s Gradle file or in the manifest. Google’s requirement page says you can confirm or change targetSdkVersion in the module’s Gradle file, or use the android:targetSdkVersion attribute in the manifest.
- Open the module-level Gradle file (
app/build.gradleorapp/build.gradle.kts). - Raise the target value to the required API level. Keep the compile SDK at the same level or higher.
- Test on a device running the new Android version. Raising the target turns off compatibility behaviours, so things that worked before can break.
- Increase the version code before you build the release. Our guide to the Android version code explains when and why.
- Build an AAB and upload it. New Play submissions use the Android App Bundle, as covered in what’s replacing APK files on Google Play.
Checking a no-code or WebView builder’s output before you upload
With a no-code or WebView builder, the builder sets the target API level, not you. You can still check it yourself before you waste a Play Console upload.
Google’s apkanalyzer tool prints it in one command. It ships with the Android SDK Command-Line Tools:
apkanalyzer manifest target-sdk my-app.apk
If the number printed is below the level in the table above, Play Console will reject the update. Run it on the signed APK your builder gives you, since the APK and AAB come from the same build.
The limitation: webtoapkfree.com, like most no-code wrappers, gives you no target API option. Its settings cover the app name, package name, icon, colour, theme, navigation and content sections. The generic Android template the browser downloads decides the target, so check the output with apkanalyzer. If the number is too low, contact the tool’s support before you plan a release (for this one, support@webtoapkfree.com).
Plan for next year’s bump
The target API level is a moving requirement, and the pattern in Google’s tables is one step up each year. Google’s pages don’t yet name the next level or date.
My take: don’t wait for Google’s email. I’d set a yearly calendar reminder for early summer, a couple of months before the late-August deadline. Rebuild, run the apkanalyzer check, test on the newest Android, and ship a small update. Apps that wait for the deadline email end up with a rushed release and a broken screen on new phones.
If this is your first upload, the target level is only one gate. New personal developer accounts also face a closed testing requirement, and wrapper apps get extra scrutiny, covered in do WebView apps get rejected by Google Play.
FAQ
What API level must a new app target on Google Play?
Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API level 35, and Android TV and Android XR apps need API level 34.
Will my old app be removed if it targets an older API level?
No. Existing apps that target Android 15 (API level 35) or higher stay available to new users. Apps that target API level 34 or lower only show to new users on devices running the same Android version or older. People who already installed the app keep it.
Is the target API level the same as the minimum SDK?
No. minSdkVersion is the oldest Android version that can install the app. targetSdkVersion is the version you tested against, and Google Play’s rule applies to that value.
Can I still get an extension?
Google offered extensions to November 1, 2026. That date has passed, so plan on meeting API level 36 for any new app or update you submit now.
Sources
- Target API level requirements for Google Play apps, Play Console Help
- Meet Google Play’s target API level requirement, Android Developers
<uses-sdk>manifest element, Android Developers- apkanalyzer, Android Developers
- App must target Android 16 (API level 36) or higher, B4X forum
- Website to APK guide, WebToAPK Free