[INFO] Unity Engine support for 16 KB memory page sizes (Android 15+)

Hello folks,

We are excited to bring support for future 16 KB compatible devices to the Unity Engine!

With Android 15, Google introduced support for 16 KB memory page sizes in the OS. It is expected that device manufacturers will start bringing out devices with these capabilities to the market. Google’s testing suggests that there are noticeable performance gains on apps and games launching on 16 KB capable devices, with up to 10% improvement.

Support for 16 KB sizes is now available from the following Unity versions:

  • Unity 6000.1.0b5 expected to be released February 9, 2025
  • Unity 6000.0.38f1 expected to be released February 14, 2025
  • Unity 2022.3.56f1 released January 15, 2025
  • Unity 2021.3.48f1 released January 22, 2025 accessible under extended LTS support for Enterprise/Industry customers

What do I need to do?

Apps that depend on native code, like Unity apps, will need to be rebuilt to include 16 KB support. At minimum you will need to:

  • Update to an Engine-compatible patch and above.
  • Update any native plugins that need updating.
  • Rebuild and resubmit your application to the Store.

16 KB support is in addition to 4 KB. The same executable will be able to support both memory page sizes.

Can my existing app (4 KB) run on a 16 KB page size device?

No. Our tests indicate that Unity apps compiled for 4 KB memory page size will not work on 16 KB devices.

I am using an older/unsupported version of Unity

The 16 KB feature will be available for supported versions of Unity (2021 Extended Support/2022 LTS/Unity 6). To benefit from this feature, please update to one of these versions.

How do I know if my project is affected?

Unity Editor versions compatible with 16 KB will help you understand how your project complies with the requirement. The Unity Editor will warn you during a build, and on the plugin’s properties if your project contains a plugin with .so filetype that is not 16 KB aligned.

I depend on 3rd-party plugins/SDKs that link to native libraries. What do I need to do?

Reach out to the plugin creators to ensure that their native libraries are 16 KB compatible. You will need to update any related SDKs and resubmit your application.

I am a plugin developer with native libraries. What do I need to do?

Follow Google’s guidance to rebuild your libraries with 16 KB support. If your plugin relies on a third party native library, contact the original developer to provide 16 KB support.

How do I test 16 KB memory page sizes?

Please follow the official Android testing guidelines. You will need to make sure that your app does not make assumptions about 4 KB size across its whole functionality. You can test this via certain Pixel hardware or official Android emulators that can switch between the different memory sizes.
Currently (Jan 2025), these are available through developer options on the following devices:

  • Pixel 8 and 8 Pro (with Android 15 QPR1 or higher)
  • Pixel 8a (with Android 15 QPR1 or higher)
  • Pixel 9, 9 Pro, and 9 Pro XL (with Android 15 QPR2 Beta 2 or higher)

Is this a requirement to target Android 15?

Currently (Jan 2025), it is not a hard requirement for targeting Android 15 in August 2025. However, this may change, and we will update this post if it does.

Thank you,

Platform Android team


Official Google Docs

12 Likes

How can we check if our plugins are supported when using the gradle injection method (default) for AdMob, Firebase etc (thus only gradle would probably detect unsupported native code right?)

1 Like