Google Play 16 KB page size requirement: dates, checks and fixes
Short answer: if your app targets Android 15 (API level 35) or higher and ships native code, it must support 16 KB memory page sizes on 64-bit devices. The requirement has applied to new apps and updates since November 1, 2025, and from February 1, 2027 Google Play will not let you release updates that do not support 16 KB page sizes. Apps written only in Java or Kotlin, with no native libraries, already comply.
The 16 KB requirement at a glance
From Android Developers «Support 16 KB page sizes» and the Android Developers Blog (May 2025), read 30 September 2026.
| Question | Answer |
|---|---|
| Which apps | Apps targeting Android 15 (API 35) or higher, on 64-bit devices |
| In force since | November 1, 2025, for new apps and updates |
| Hard stop for updates | February 1, 2027: updates without 16 KB support cannot be released |
| Not affected | Apps with only Java or Kotlin code, including all libraries and SDKs |
| Build tools that fix it | Android Gradle Plugin 8.5.1 or higher; NDK r28 or higher aligns to 16 KB by default |
| Where to see status | App bundle explorer in Play Console |
Is my app affected?
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.
How to check an APK for 16 KB alignment
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.
How to fix it
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.
React Native, Flutter and Unity
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.
How to test on a 16 KB device
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.
Why it is worth doing before the deadline
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.
Where Censuus fits
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.
Frequently asked questions
What is the last date for the Google Play 16 KB page size requirement?
The requirement has applied to new apps and updates targeting Android 15+ since November 1, 2025. From February 1, 2027, Google Play will not let you release updates that do not support 16 KB page sizes.
Does a Kotlin-only app need to change anything for 16 KB?
No. Google says apps that only use Java or Kotlin code, including all their libraries and SDKs, already support 16 KB devices.
Which NDK version supports 16 KB page sizes?
NDK r28 and higher compile 16 KB aligned by default. With NDK r27 or lower, add the linker flags -Wl,-z,max-page-size=16384 and -Wl,-z,common-page-size=16384.
How do I check if my APK is 16 KB aligned?
Run zipalign -c -P 16 -v 4 on the APK, use Build > Analyze APK in Android Studio and read the Alignment column for the lib folder, or open the App bundle explorer in Play Console.
Which React Native version supports 16 KB page sizes?
Google’s May 2025 announcement lists React Native 0.77 and later as compatible.
Guides for app developers
- Google Play target API level requirements for 2026
- Migrating to Android Gradle plugin 9
- Android 17 app memory limits: detect, test and stay under them
- The UIScene life cycle is required in iOS 27
- CocoaPods goes read-only: what changes and when
- The Android 17 location button and Google Play’s precise location rules
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.