Skip to content
Google Play

Google Play guide · · 5 min read

Android target API requirement for Google Play, AAB and 16 KB

Google Play rules as of November 2026: target API 36, app bundles, 64-bit libraries, the 16 KB page size date, size limits and what Godot 4.5.1 exports.

A staircase of four blocks labelled API 33, 34, 35 and 36, with a flag on the tallest orange block, beside the words target API 36.

What does Google Play require from a new Android game in November 2026?

Five things decide whether an upload goes through. New apps are published as Android App Bundles. New apps and updates must target Android 16, API level 36. Native libraries need 64-bit versions. Updates must support 16 KB memory pages from February 1, 2027. And the compressed download must stay under the size limits, 500 MB for the base module. The board below is each rule with a way to check it.

Everything here is from Android Developers and Play Console Help as of November 2026, and the dates move, so read the linked pages again before you plan a release. We ship Godot 4 games on iPhone and do not have a game on Google Play, so the Godot parts are things we read from the 4.5.1 templates on our own machine, not a launch report.

Five rows: AAB for app bundles, API 36 for the target level, 64-bit libraries, 16 KB page support from February 1, 2027 and a 500 MB base module limit, each with a way to check it.
The checks to run before any Play upload.

Which target API level do you need, and has the deadline passed?

It has passed. Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play. Wear OS and Android Automotive OS apps need API 35, and Android TV and XR apps need API 34. Google offered an extension to November 1, 2026, and that date is also behind us.

Existing apps have a softer rule. They must target API 35 or higher to stay available to new users on devices running a newer Android version than the app targets. An app that targets 34 or lower stays visible only on devices running that Android version or older. People who already installed it can keep it and reinstall it. Permanently private apps for one organization are exempt.

Targeting a level is not the same as compiling for it, and it changes behavior: some Android changes apply only to apps that target the new version. Read Google's Android 16 behavior changes and test on a real device before you upload.

Animated to-scale timeline from August 2026 to March 2027. A marker travels to November 8, 2026, passing the August 31 API 36 deadline and the November 1 extension deadline, with 85 days left to February 1, 2027, counted from that date.
Deadlines drawn to scale. Today in the picture is the day this guide was checked.

What does Godot 4.5.1 target by default?

API 35. We read the template: the android_source.zip that ships with Godot 4.5.1 stable sets compileSdk 35, targetSdk 35, minSdk 24, Android Gradle plugin 8.6.1 and NDK 28.1.13356709. A default export therefore does not meet the API 36 rule for a new app or an update.

The export preset has a Target SDK field under Gradle Build. Godot says it can only be overridden when Use Gradle Build is on, which you need for an AAB anyway: see our Godot Android export and keystore guide. We have not shipped a 4.5.1 build with Target SDK set to 36, and the template is compiled against 35, so build it, install it on a device and play every screen before you upload. Check the release notes of the Godot version you use too: a newer one may raise the default.

What is the 16 KB page size rule?

Android 15 and later can run on devices whose memory pages are 16 KB instead of 4 KB. Google's rule: apps targeting Android 15 (API 35) and higher must support 16 KB page sizes on 64-bit devices, and starting February 1, 2027 an update that does not support them cannot be released. Apps written only in Java or Kotlin already comply. Anything with native code, which includes every Godot game, has to be built with its libraries aligned to 16 KB.

The fix is mostly the toolchain. NDK r28 and newer compile 16 KB aligned by default, and Android Gradle plugin 8.5.1 or newer aligns uncompressed libraries in the zip. With NDK r27 or older you pass linker flags for a 16384 byte page. Any prebuilt library you add, such as an ads plugin, must be built the same way, so check each one.

Two strips of memory split into 4 KB and 16 KB pages. With 4 KB alignment code and data share one 16 KB page, marked in red. With 16 KB alignment the data starts on a new page.
A segment that starts inside a page shared with another one is what breaks on a 16 KB device.

How do you check that your build is ready for 16 KB?

We checked the Godot 4.5.1 release template ourselves by reading the ELF program headers of its libraries. The arm64-v8a and x86_64 libraries have a LOAD alignment of 0x4000, which is 16 KB. The 32-bit armeabi-v7a and x86 libraries are at 0x1000. That matches Google, which states the rule for 64-bit devices. It says nothing about plugins you add, so run the checks below on your own export:

# alignment of each 64-bit library (expect: align 2**14)
llvm-objdump -p lib/arm64-v8a/libgodot_android.so | grep LOAD

# zip alignment of the APK
zipalign -c -P 16 -v 4 game.apk

# what a bundle asks for (PAGE_ALIGNMENT_16K is what you want)
bundletool dump config --bundle=game.aab | grep alignment

# on a 16 KB test device or emulator (expect 16384)
adb shell getconf PAGE_SIZE
Four rows for arm64-v8a, x86_64, armeabi-v7a and x86 libraries from the Godot 4.5.1 template. The two 64-bit rows show 0x4000 alignment in green, the two 32-bit rows show 0x1000.
Our own measurement of lib/*/libgodot_android.so in the 4.5.1 stable android_release.apk.

What else can block an upload?

These are the other numbers and rules that trip a first release:

  • Size: compressed limits are 500 MB for the base module, 1.5 GB per asset pack and 4 GB for the cumulative download. A dialog warns people on mobile data above 200 MB. App bundles do not support OBB expansion files.
  • 64-bit: for every 32-bit architecture you ship, include the 64-bit one. The Godot template does, but check your plugins.
  • Version code: the maximum is 2,100,000,000. Play Console blocks bundles above it.
  • Signing: new apps are enrolled in Play App Signing by default. You sign the bundle with an upload key and Google signs what users download. If you lose the upload key you can request a reset. The app signing key can only be changed before the first release to open testing or production.
  • Privacy forms: a bundle that passes the checks above still needs the Data safety form, and a new personal account needs the closed test first.

Questions people ask

What target API level does Google Play require now?
As of November 2026, new apps and updates must target Android 16, API level 36, or higher. Wear OS and Automotive OS need 35, and Android TV and XR need 34.
Do you still need to upload an AAB to Google Play?
Yes for new apps. Google has required the Android App Bundle for new apps since August 2021, and bundles do not support OBB expansion files.
When is the 16 KB page size requirement enforced?
Google says that starting February 1, 2027, updates to apps targeting Android 15 or higher that do not support 16 KB page sizes cannot be released.

Sources and further reading