Are Google Play new apps and updates required to target Android 16 now?

Are Google Play new apps and updates required to target Android 16 now

Yes. Google Play requires new apps and app updates to target Android 16, API level 36, starting August 31, 2026. Google also says developers can request an extension to November 1, 2026 if they need more time to update. The policy applies to submission eligibility, not just to what your app can run on.

The part people get wrong is that targetSdkVersion is not the same as minSdkVersion. You can still support older Android versions on devices, but Google Play now checks the target API level on the version you submit. If your upload targets an older API level than the current requirement, Play can block the release.

Google’s policy page says this requirement applies to new apps and app updates. It also lists exceptions for some form factors, including Wear OS, Android Automotive OS, Android TV, and Android XR, which have their own target levels. For a standard phone or tablet app, the current bar is Android 16.

The inconvenient part is timing. If your team plans release work around a date like September 2026, the submission gate is already fixed by the policy date, not by your internal schedule. A build that is functionally finished can still fail review if it is still targeting Android 15 or lower when you submit after the deadline.

If you need more time, Google says you can request an extension to November 1, 2026. That does not change the target requirement itself, it only gives you a later cutoff for distribution or submission in the cases covered by the extension flow. The extension form is available in Play Console from the policy warning or issue page.

Existing apps have a separate availability rule. Google says apps that do not meet the latest target API requirement can stop being available to new users on devices running newer Android versions than the app targets. That is the part teams notice only after a release stalls or user reach changes, because the app may still be installed on older devices while becoming harder to discover on newer ones.

The clean way to check your status is to open your Play Console policy page, confirm the app’s current targetSdkVersion, and compare it with the active policy deadline for your app type. If you are planning a release now, set your build to Android 16 first, then test the migration, then upload. That sequence avoids a submission failure at the last step.

If you are also managing Play testing, keep that separate from target API compliance. Closed testing, internal testing, and production access are different policy tracks. A test track does not override the target API level requirement for the release artifact you submit. The tracker at https://devconnectplatform.com can help coordinate testers, but it does not change Google Play policy.

For teams that maintain more than one app, the practical rule is simple: standard Android apps need Android 16 for new submissions and updates after the August 31, 2026 deadline, while specialty form factors need to follow their own listed target levels. If you are shipping on Play, check the target level before you package the release, not after.

A quick example makes the cutoff obvious. If you submit a regular app update on September 2, 2026 and the manifest still targets Android 15, Play can reject the upload. If you submit the same app after changing the target to Android 16, the target API check is satisfied, and review can proceed on the rest of the release.

The policy page also says Google Play requires all apps to meet the listed target API level requirements, which is why relying on an older target as a long-term release strategy is risky. The safer path is to upgrade the target early, run compatibility testing, and keep one release branch ready for the deadline instead of trying to rush the migration at the end.

If your app is one of the exceptions, read the specific section for that form factor before you change anything. A Wear OS, TV, Automotive, or XR app does not follow the same target API level as a standard phone app, and the wrong assumption can send a release into review with the wrong manifest target.

FAQ

Does Android 16 mean my app can no longer run on Android 14 or Android 15 No. The target API level is a submission and behavior target, not a minimum supported device version. Your app can still run on older devices if your minSdkVersion and compatibility testing support them. Google’s policy page separates target API level from minSdkVersion.

Can I keep my existing app on an older target and just avoid updates Google says older-target apps can lose availability to new users on newer Android devices. You can keep an app live for older-device users, but that does not avoid the target API policy, and it can shrink reach on current devices.

Does the extension mean I can ignore Android 16 until November 1, 2026 No. The extension is a temporary path for the apps and situations Google lists in Play Console. It buys time, it does not replace the requirement. If your app is covered, you still need to complete the migration before the extension ends.

Where do I confirm the rule for my app type Google’s target API level policy page is the source of truth. Read the standard app section first, then check the specialty sections for Wear OS, TV, Automotive, or XR if your app belongs there.

What is the first technical step if my app is still on Android 15 Change the targetSdkVersion to Android 16, then run your compatibility tests against the new target. Google’s policy page points developers to the migration guidance, and the Play policy update page shows the current deadline tied to the new target.