What is happening to x86 devices in Genymotion SaaS

Source:

Published:

Keywords: Genymotion SaaS, arm64, x86, device migration, Android virtualization, Google Play 64-bit

Document ID: https://support.genymotion.com/hc/en-us/articles/30419556610333#split1

Audience

Genymotion SaaS users.

Genymotion SaaS is transitioning to arm64 exclusively for Android virtual devices.

On March 30, 2026, the ability to create and start x86-based virtual devices will be restricted.

Overview

Genymotion SaaS is transitioning to arm64 exclusively for all Android virtual devices.

On March 30, 2026, the creation and starting of x86-based virtual devices will be restricted.

Why x86 devices are being removed

The majority of physical Android devices today use arm64 processors.

Genymotion SaaS aligns its platform with the hardware end-user devices actually have to improve testing accuracy.

This alignment also helps meet Google Play's mandatory 64-bit requirement for all apps.

The arm64 architecture ensures apps behave in Genymotion SaaS the same as on end-user devices, which is critical for catching bugs and ensuring quality.

Performance impact

arm64 virtual devices offer significant performance advantages.

Thanks to Genymotion's new ARM servers, you will experience faster booting and saving times for your virtual devices.

Preparation steps

Actions to prepare 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 has customized a virtual device by installing specific apps, adjusting settings, or using automated recipes will need to recreate these setups on our 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.

However, you will need to start using arm64 devices for testing.

If your app uses native C/C++ code

You will need to recompile it to include the arm64-v8a architecture.

Then use our arm64 virtual devices.

I'm already using arm64 virtual devices but I'm encountering errors

If you are encountering unexpected errors with your 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, 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 I 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 any disruption.

Will this migration affect my pricing or subscription cost?

No. This is a technical upgrade to Genymotion SaaS.

This upgrade will not change your current pricing or subscription plan.

There will be no cost change associated with this migration.

Related articles