How do I check if an APK or AAB supports 16 KB page sizes?

Upload the APK, AAB, APKM, AAR, ZIP, or native .so file into this checker. It analyzes packaged native libraries, ELF PT_LOAD alignment, and packaging warnings directly in your browser.

Does this site upload or store my APK, AAB, or errors?

No. Files are analyzed locally in your browser. The site does not upload or store your files, file names, library names, or detailed error contents on the server.

What is the current Google Play deadline for 16 KB page-size fixes?

As noted on the site from Play Console messaging, affected apps currently have time until May 31, 2026 to fix the 16 KB page-size violation and continue publishing updates.

Android 16 KB Page Size Checker for APK, AAB, APKM and AAR

Choose or drop an artifact

Everything runs in the browser. No upload.

Studio mode prioritizes 64-bit ABI ELF failures like Android Studio. APK packaging offset mismatches are shown as warnings.

Choose or drop an artifact Supported: APK, AAB, APKM, AAR, ZIP, and native shared libraries

Choose an artifact to start the scan.

Studio View

Studio mode prioritizes arm64-v8a and x86_64. ELF failures are blockers. Packaging mismatches are warnings.

Primary ELF Failures

These are the 64-bit libraries with real ELF-level 16 KB blockers.

Warnings

Packaging mismatches and non-blocking ELF notes that are worth reviewing before release.

Library Report

Per-library result for the Android Studio-like primary view.

Library	ABI	Compressed	Packaging	ELF

What this site checks

A practical pre-upload checker for Android native library issues related to 16 KB page-size support.

This checker inspects packaged native libraries in APK, AAB, APKM, AAR, ZIP, and raw .so files.

It checks ELF PT_LOAD alignment and flags real blockers as failures.
It treats APK packaging offset mismatches as warnings, because Play may still accept the AAB delivery path.
Studio Mode focuses on arm64-v8a and x86_64 to match the Android Studio-style primary view.
Strict Mode expands the report to all discovered ABIs and extra ELF notes.

This site does not currently parse AndroidManifest target SDK values, and it is not a guaranteed replica of Play Console’s internal review pipeline.

For the full written reference, see CHECKS_AND_LIMITATIONS.md in the project repository.

Google Play Policy Context

This tool is built for the two Play Console warnings teams are hitting most often: 16 KB page size support and target API level 35 for Android 15.

16 KB Page Size Warning

Google Play requires apps targeting Android 15 and above to work correctly on devices that use 16 KB memory page sizes. This tool checks native libraries and packaging to help identify the exact blocker.

Current deadline note as of March 25, 2026: Play Console is showing an extension for affected apps, giving more time to fix this violation until May 31, 2026.

Target API Level 35 Warning

From November 1, 2025, apps that are not within one year of the latest Android release cannot be updated on Google Play. If your highest target API level is Android 13 or Android 14, you need to move to Android 15 (API level 35) or higher.

Scope note: this checker validates native library and packaging issues. It does not currently parse AndroidManifest target SDK values.

Official References

Current official Android and Google Play references as of March 25, 2026.

Android Developers: Support 16 KB page sizes. Official technical guidance for verifying and fixing 16 KB page-size support.
Play Console Help: Google Play's target API level policy. Official policy overview for target API compliance.
Android Developers: APK Analyzer. Official Android Studio documentation for APK inspection.
Play Console extension shown in your account: apps currently affected by the 16 KB issue have been given time until May 31, 2026 to fix the violation and continue publishing updates.

How To Fix Google Play Android 15 Policy Warnings

Useful guidance for teams troubleshooting Play Console compliance.

App Must Support 16 KB Memory Page Sizes

This usually means one of two things: your APK stores native libraries without proper 16 KB ZIP alignment, or a bundled native library was built with 4 KB PT_LOAD alignment.

Common causes include old NDK-built libraries, outdated third-party SDKs, and old Android packaging pipelines that generate non-compliant APKs from AAB files.

App Must Target Android 15 (API Level 35) Or Higher

If Play says your highest non-compliant target API level is Android 13 or Android 14, update your app to target API level 35 or higher and publish a new production release after testing in internal, closed, or open testing.

This policy issue is separate from 16 KB page-size support. You may need to fix both before a release is fully compliant.

Privacy Policy

What this site tracks and what it never sends to the server.

This checker analyzes files locally in your browser. We do not upload or store your APK, AAB, APKM, AAR, ZIP, native libraries, error contents, warnings, or file contents on our server.

For product analytics only, we track aggregate usage events such as page visits, scans started, file type scanned, result status, number of warnings, number of failures, number of successful scans, and button clicks like mode changes or copy actions.

We do not store the actual library names, actual error messages, actual warnings, file names, or file contents in analytics. Analytics is used only to understand site usage and improve the tool.