Google Play 16 KB page size requirement: dates, checks and fixes

Only native code matters. If your app uses any NDK library, directly or through an SDK, it has to be rebuilt for 16 KB devices. That covers your own C or C++ code, third-party native libraries and SDKs, and apps made with builders or engines that bundle native libraries. If every line of your app and of its libraries is Java or Kotlin, you already support 16 KB devices and have nothing to change. The quickest way to know is to look for .so files inside the lib folder of your APK.

In Android Studio, open the project and choose Build > Analyze APK, pick the APK and open the lib folder: the Alignment column shows a warning for every shared library that is not aligned. Android Studio and lint also warn about prebuilt libraries and APKs that are not 16 KB compliant. From the command line, zipalign -c -P 16 -v 4 APP.apk should end with «Verification successful», and llvm-objdump -p LIBRARY.so | grep LOAD from the NDK toolchain must show align 2**14 or higher; 2**13 or 2**12 means the library is still 4 KB aligned. In Play Console, the App bundle explorer shows whether each build is compliant.

Upgrade the Android Gradle Plugin to 8.5.1 or higher, which zip-aligns uncompressed shared libraries on a 16 KB boundary. Build native code with NDK r28 or higher, which compiles 16 KB aligned by default. On NDK r27 or lower, add the linker flags -Wl,-z,max-page-size=16384 and -Wl,-z,common-page-size=16384, in LOCAL_LDFLAGS for ndk-build or target_link_options for CMake. Update every third-party SDK that ships native libraries to a 16 KB compatible version, and remove code that assumes a 4 KB page, such as a hard-coded PAGE_SIZE or 4096; read the size at runtime with getpagesize() or sysconf(_SC_PAGESIZE). If you are stuck on AGP 8.5 or lower, Google’s fallback is to package native libraries compressed with useLegacyPackaging in the jniLibs block.

Google’s May 2025 announcement names compatible versions for the main cross-platform tools: React Native 0.77 and later, compatible releases of Flutter, and 16 KB support in Unity. For these apps the fix is usually to upgrade the framework and every plugin that ships native code, rebuild, and run the checks above on the new APK.

In Android Studio, open Tools > SDK Manager, show package details for Android VanillaIceCream or higher and download the 16 KB Page Size system image for ARM 64 or x86_64, then create an emulator from it. On a real phone, Pixel 8, 8 Pro and 8a on Android 15 QPR1 or higher, Pixel 9, 9 Pro and 9 Pro XL on Android 15 QPR2 or higher, and Pixel 9a on Android 16 have the developer option Boot with 16KB page size. adb shell getconf PAGE_SIZE returns 16384 once the device runs with 16 KB pages.

Google measured the gains of 16 KB pages in its own tests: app launch under memory pressure was 3.16% faster on average, with up to 30% for some apps, and power draw during launch 4.56% lower. More importantly for release planning, an app that is not ready cannot ship updates on Google Play from February 1, 2027, so a bug fix could be blocked by a library you have not rebuilt.

Keeping the app shippable is the floor; being found is the rest. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.