What is happening to x86 devices in Genymotion SaaS?

Genymotion SaaS is transitioning to exclusively support arm64 architecture for all Android virtual devices. On March 30, 2026, the ability to create and start x86-based virtual devices will be restricted.

Why are you removing x86 devices?

The vast majority of physical Android devices today use arm64 processors. Genymotion SaaS is aligning the platform with the hardware end-users actually have by providing a more accurate and reliable testing environment possible.

Genymotion SaaS is also ensuring users can meet Google Play's mandatory 64-bit requirement for all apps. The arm64 architecture ensures an app behaves in the virtual environment exactly as it will on users' physical devices. This behavior is critical for catching bugs and ensuring quality.

Will my tests run slower on arm64 virtual devices?

arm64 virtual devices offer significant performance advantages. Thanks to new ARM servers, faster booting and saving times for virtual devices are expected.

What do I need to do to prepare?

The actions needed to take depend on how Genymotion is used.

• If you already use only arm64 virtual devices, no action is required on your side.
• If you have custom device setups: Any user who customized a virtual device by installing specific apps, adjusting settings, or using automated recipes needs to recreate these setups on new arm64 OS images.

The new arm64 OS images are already available.

• For basic testing of apps written in Java/Kotlin: No action is required for the app itself.

arm64 devices virtual devices must be used.

• If your app uses native C/C++ code: The app needs to be recompiled to include the arm64-v8a architecture.

The app must then use arm64 virtual devices.

I'm already using arm64 virtual devices but I'm encountering errors. What should I do?

Users encountering unexpected errors with ARM devices may be using one of Genymotion's early arm64 Android OS images. Early arm64 Android OS images are tagged as “beta”.

To ensure full compatibility and benefit from the latest improvements, users should recreate the virtual device using a more recent arm64 OS image. The “beta” tag has been removed from all stable and recommended versions.

What happens if I don't migrate my testing to arm64 devices by the deadline?

After March 30, 2026, creation and startup of x86 virtual devices will no longer be possible. Existing x86-based recipes will also fail.

Existing x86 virtual devices will be transitioned to a read-only state for a short grace period. Existing x86 virtual devices will then be fully removed.

Genymotion SaaS encourages starting the transition of testing workflows now to avoid any disruption.