TesterAgent

16 KB page size on Android: what it means and how to check your APK

Android devices can use a 16 KB memory page size, so apps with native code (.so libraries, used by many Flutter, React Native and game apps) must have those libraries aligned to 16 KB. Google says all apps targeting Android 15 (API 35) and higher must support 16 KB pages on 64-bit devices, and from 1 February 2027 updates that don't can't be released. TesterAgent's free APK check reads each 64-bit native library and reports any whose ELF segments or position in the APK are not 16 KB-aligned. Usually the fix is to update the NDK, Flutter or React Native version and rebuild.

By TesterAgent · Last reviewed

App (APK)

Android .apk only, up to 150 MB. We check the file (security, Google Play rules, translations) — the free check does not run the app. We delete the file right after the check.

By running a check you agree to the Terms and the Acceptable Use Policy.

No account needed for one free check — a website or an app. The report link works for 7 days. Create a free account to keep every report. · See a sample report

Who is affected

Only apps that ship native libraries (lib/arm64-v8a/*.so, lib/x86_64/*.so). Pure Kotlin/Java apps without native code already work.

How our check decides

  • Each 64-bit library’s ELF LOAD segments must be aligned to at least 16 KB (16384 bytes).
  • Uncompressed libraries must also start at a 16 KB-aligned offset inside the APK (zip alignment).

Source: Android Developers: Support 16 KB page sizes

Typical fixes

  • Update to a recent Android Gradle Plugin and NDK (r28 or newer aligns to 16 KB by default) and rebuild.
  • Flutter and React Native: update to a version whose engine libraries are 16 KB-aligned, then rebuild.
  • Update third-party SDKs that ship their own .so files.

Frequently asked questions

Does this affect 32-bit libraries?

No. The requirement is about 64-bit devices; our check reads the 64-bit libraries.

Is the check free?

Yes: one APK up to 150 MB without an account.