DEV Community

Dainy Jose
Dainy Jose

Posted on

📱 Understanding Google Play’s 16 KB Page Size Requirement for Android Apps

Google recently introduced a new requirement for Android apps published on the Play Store: all apps must support 16 KB page sizes starting with Android 15 (API level 35). If your app does not comply, Google Play will block updates or new releases.

This article explains what this requirement is, why it matters, how to test your app, and the process of re-releasing across different testing tracks.


🔎 What’s the 16 KB Page Size Requirement?

Traditionally, most Android devices used 4 KB memory pages. With Android 15+, Google requires apps to support larger 16 KB page sizes to improve performance, memory alignment, and hardware compatibility with modern devices.

If your app is not built with 16 KB support, users with newer devices may not be able to install or run it.


⚠️ Google Developer Requirement Alert

Google Play Console now enforces this rule. You may see alerts like:

“Your app must support 16 KB page sizes. Future releases that don’t comply will be rejected.”

This is not optional. Just like target SDK level updates or privacy policy declarations, it’s a mandatory compliance requirement.


🧪 How to Test if Your APK/AAB Supports 16 KB Pages

You should always verify your builds before uploading to Google Play. Here are multiple ways:

✅ 1. Test Using Android Studio

1.1 Build your APK or AAB
  • In Android Studio, go to Build > Build Bundle(s) / APK(s) > Build APK(s) or Build Bundle(s).

  • Locate the generated file (Android Studio will show a link to the output folder).

1.2 Inspect with APK Analyzer
  • Go to Build > Analyze APK

  • Select your APK or AAB file.

  • Inside APK Analyzer, check your native .so libraries (under lib/arm64-v8a or lib/armeabi-v7a).

1.3 Verify ELF Page Size

Unfortunately, APK Analyzer doesn’t directly show page size.

  • Right-click a .so library → Save As → download locally.

  • Open a terminal, run:

readelf -h libyourlib.so | grep "Page size"
Enter fullscreen mode Exit fullscreen mode
  • Look for Page size: 16384 (✅ 16 KB).

✅ 2. Using apkanalyzer (Command Line)

  • Run the following command:
apkanalyzer files list <your-app.aab or apk> | grep libc.so
Enter fullscreen mode Exit fullscreen mode
  • Then check ELF headers to ensure 16 KB page size is supported.

✅ 3. Using readelf

  • Extract your APK and check the native libraries:
unzip app-release.apk -d extracted_apk

cd extracted_apk/lib/arm64-v8a

readelf -h libyourlib.so | grep "Page size"
Enter fullscreen mode Exit fullscreen mode
  • If it shows 16384 (16 KB) → ✅ compliant.
  • If it only supports 4096 (4 KB) → ❌ needs fixing.

✅ 4. Test Using Emulator

  • Open Android Studio Emulator with Android 15 (API 35) image.

  • Install your APK:

adb install app-release.apk
Enter fullscreen mode Exit fullscreen mode
  • If the app installs and runs normally → it supports 16 KB pages.

  • If not, you’ll see installation errors like:

“INSTALL_FAILED_INVALID_APK: unsupported ELF page size”


🔧 How to Fix & Enable 16 KB Support

1. Update your build environment

  • Use Android Gradle Plugin 8.5+

  • Ensure NDK r26 or above (supports 16 KB pages)

  • Use compileSdkVersion 35 and targetSdkVersion 35 in build.gradle.

2. Rebuild your app with:

android {
    compileSdkVersion 35
    defaultConfig {
        targetSdkVersion 35
    }
}
Enter fullscreen mode Exit fullscreen mode

3. Clean & rebuild:

./gradlew clean assembleRelease
Enter fullscreen mode Exit fullscreen mode

🚀 How to Re-Release Your App

Once you confirm support, you need to upload a new build in Google Play Console.
Here’s how:

1. Open Testing

  • Go to Release > Testing > Open testing

  • Create a new release with the updated APK/AAB

  • Add release notes like:

“Updated to support Android 15 16 KB page size requirement.”

  • Save & publish → testers get the new build.

2. Closed Testing

  • Same process under Closed testing track

  • You can choose specific testers (email lists).

3. Production

  • After confirming stability in testing tracks, promote your release to Production.

  • This ensures compliance before the deadline and avoids Play Store rejections.

✅ Summary

  • What: Android apps must support 16 KB page sizes starting Android 15.

  • Why: Improves memory management & ensures compatibility with new devices.

  • How to test: Use Android Studio, apkanalyzer, readelf or Emulator.

  • Fix: Update Gradle, NDK, and target SDK.

  • Release: Push new builds through open testing, closed testing, then production.


⚡ Next Steps

If you’ve already understood the basics of the 16 KB page size requirement, check out my follow-up guide:

👉 Troubleshooting 16 KB Page Size Issues


📚 References

Google Android Developer Docs – Page Sizes


🔗 Pro Tip: Always test on the latest Android Emulator (API 35) before uploading to Google Play.


✍️ Written by Dainy Jose — Mobile App Developer specialized in React Native and the MERN stack.

💼 Skills & Tools:

Mobile App Dev | MERN Stack | React Native | TypeScript | Redux | React.js | Node.js | MongoDB | MySQL | Express.js | REST API | JWT | Google Maps | Firebase | Jest | Agile | SDLC | Payments | Git | Bitbucket | Jira

📬 Connect with me:

🔗 LinkedIn

💻 GitHub

Top comments (0)