What is happening to x86 devices in Genymotion SaaS?

Overview

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.

The vast majority of physical Android devices today use arm64 processors.
Genymotion SaaS is aligning its platform with the hardware end-users actually have to provide the most accurate and reliable testing environment.
This move helps meet Google Play's mandatory 64-bit requirement for all apps.
The arm64 architecture ensures your app behaves in the virtual environment exactly as it will on end-users' physical devices, which is critical for catching bugs and ensuring quality.

Arm64 virtual devices offer significant performance advantages.
Thanks to our new ARM servers, you will experience faster booting and saving times for your virtual devices.

If you already use only arm64 virtual devices, no action is required on your side.
If you have custom device setups:
You have custom device setups if you installed specific apps, adjusted settings, or used automated recipes.
Those setups must be recreated on the new arm64 OS images.
The arm64 OS images are already available.
For basic testing of apps written in Java/Kotlin:
No action is required for your app itself.
You will need to start using arm64 virtual devices.
If your app uses native C/C++ code:
You will need to recompile it to include the arm64-v8a architecture.
You must use our arm64 virtual devices.
I'm already using arm64 virtual devices but I'm encountering errors:
If you are encountering unexpected errors with ARM devices, you may be using one of our early arm64 Android OS images tagged as "beta".
To ensure full compatibility and benefit from the latest improvements, please recreate your virtual device using a more recent arm64 OS image.
The "beta" tag has been removed from all stable and recommended versions.

What happens if you don’t migrate by the deadline:
After March 30, 2026, you will no longer be able to create or start x86 virtual devices.
Your existing x86-based recipes will also fail.
Existing x86 virtual devices will be transitioned to a read-only state for a short grace period before being fully removed.
We strongly encourage you to begin transitioning your testing workflows now to avoid disruption.

Was this article helpful?

Need more help?

How to run applications and games for arm (arm64)?
Genymotion Desktop and Hyper-V (Windows)
I can't install or run an application/game in Genymotion Desktop
How to enable kiosk mode with Genymotion SaaS (Cloud)?
How to use Android Studio, Eclipse, VS Code, JetBrains Rider or any other IDE with Genymotion SaaS?