2025-09-23
Aligning with the real world for high-fidelity virtual devices
The mobile world runs on ARM.
The vast majority of physical Android smartphones and tablets your users own are powered by arm64 processors.
Testing on an x86 virtual device, while once a convenient proxy, is now like testing a sedan on a racetrack built for Formula 1.
The environments are fundamentally different.
This divergence can hide bugs and performance issues that will only surface once your app is running on physical devices.
By focusing exclusively on arm64, we are closing this fidelity gap.
We are committing to a platform where your test results are a precise reflection of how your app will perform in the real world, giving you greater confidence with every release.
> Note > This platform upgrade is a technical evolution, not a commercial one. > Your current pricing and subscription plan will not change.
Keeping you compliant and competitive
Google’s direction for the Android ecosystem is clear: since 2019, Google Play has mandated that all apps with native code must provide an arm64 version.
This isn’t a suggestion; it’s a requirement for being published on the world’s largest app store.
By making arm64 our standard, we are ensuring you have the compliant infrastructure you need to succeed, right out of the box!
Unlocking the next generation of apps
This transition is also about the future. The arm64 architecture is the key to unlocking the next wave of mobile innovation.
Its 64-bit design allows to address more than 4GB of RAM, which is critical for memory-intensive applications like high-resolution games, complex data visualization tools, and the demanding workloads of on-device AI and machine learning.
For those working on intensive apps and games, arm64 GPU-accelerated virtual devices are also available on request.
By providing a true arm64 environment, we are giving you the platform you need to not just test today’s apps, but to build and validate the cutting-edge apps of tomorrow.
What you need to do
We want to make this transition as smooth as possible for you, but you may need to perform some update on your workflow before March 30, 2026.
For everyone:
- If you already only use arm64 virtual devices, no action is required on your side. Your workflow is already compliant with our future direction.
- If you use x86 custom recipes (with specific apps installed, settings changed, or created via automated recipes), you will need to recreate them using our new arm64 OS images.
For developers:
- If you use CI/CD integration, you will need to make sure that your system now starts arm64 virtual devices.
- If your app is written purely in Java or Kotlin, it is already compatible with arm64.
- If your app uses native code (such as C/C++), you will need to recompile it for the arm64-v8a architecture.
- For more information and answers to common questions, please consult our FAQ here.
We are incredibly grateful for the trust you place in Genymotion. By focusing our efforts on the arm64 architecture, we are confident to provide a more powerful, accurate, and future-proof platform that helps you build, test and share better applications. We are committed to supporting you through this transition, feel free to reach out if you have any questions. Thank you for being part of this journey with us. The Genymotion Team