Google Play's Target API Level Requirement in 2026: What It Means for Your App

If you've tried to upload an app update recently and Play Console said "Your app must target Android 16 (API level 36) or higher", you've hit Google Play's yearly target API level requirement. It catches a lot of people with apps made by website-to-app converters, because the person who owns the app usually isn't the one who controls how it was built. This guide explains what the rule means, the dates that matter, and what to do about it.

What "target API level" means

Every Android version has an API level number. Android 15 is API 35 and Android 16 is API 36. An app's target API level tells Android which version's rules the app was built for. When an app targets a newer level, it opts in to that version's privacy and security protections, such as stricter background limits and permission rules. Google raises the minimum target every year so that apps on the Play Store keep up with those protections.

The target API level is not the same as which phones can install your app. That's the minimum SDK. An app can target API 36 and still run on phones as old as Android 7.

The 2026 dates

• New apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher.
• If you needed more time, Google allowed developers to request an extension to November 1, 2026 from Play Console.
• Existing apps that aren't updated must target at least Android 15 (API level 35) to stay available to new users on phones running a newer Android version than the app targets.
• Wear OS, Android TV, Android Automotive and Android XR apps have lower thresholds. Check Google's target API page if you publish for those.

What happens if your app falls behind

Your app isn't deleted, but it effectively freezes. You can't fix bugs, change the icon or respond to a policy issue until it's rebuilt on a current target. That's a bad position to be in if Google flags something and gives you a deadline.

Why converter-built apps get stuck

If you wrote your app yourself, updating the target is a change in your build file plus some testing. If your app was made by a website-to-app converter, you depend on the converter updating its Android template. Free and abandoned tools often don't, and some only give you an APK you can't rebuild. Ask your provider, or check yourself:

1. 1Upload your latest AAB to an internal testing track in Play Console. If the target is too low, it tells you straight away.
2. 2Or open Play Console, go to your app, then App bundle explorer, and look at the target SDK for each version.
3. 3If your converter can't produce a build targeting API 36, you'll need a new build from a tool that can, using the same package name and signing key so it installs as an update.

That last point matters. An update has to use the same package name and be signed with a key Google Play recognises. If you use Play App Signing, which is required for new apps, you can request an upload key reset from Play Console if you lost access to the old tool's key, but the package name can never change. More on what to look for in a tool in free website to APK converters.

How Capsule handles it

Capsule's Android template targets Android 16 (API level 36) today, and every build uses the current template, so a rebuild picks up new target requirements as Google raises them. Every build of your app is signed with the same key and keeps your package name, so updates install cleanly over earlier versions, both from Google Play and for people who installed the APK directly. When next year's requirement arrives, you rebuild from the dashboard and upload the new AAB.

Does targeting Android 16 change how my app behaves?

For most website-based apps, very little. The visible change on recent Android versions is edge-to-edge display: apps draw behind the status bar and navigation bar, so the app has to handle those areas properly. Capsule handles this in the native shell and colours the system bars to match your brand in light and dark mode, so your site isn't hidden under them. The other changes in recent versions mostly affect background work and permissions, which a website-based app rarely uses.

For the rest of the publishing process, see how to publish an app on Google Play, and why Google Play rejects WebView apps for the other policy checks reviewers run.