What changes is Genymotion making regarding virtual device architecture support?

**Genymotion SaaS is moving to arm64**

We’re transitioning Genymotion SaaS to exclusively support arm64 for all Android virtual devices, effective March 30, 2026. After that date, creating or starting x86-based virtual devices will be restricted. This change aligns with real-world device architecture and Google Play requirements for arm64 native code. If you’re currently using arm64, no action is needed. If you use x86 or custom recipes, you’ll need to recreate them using arm64 OS images. For developers with CI/CD pipelines, you’ll want to ensure your automation can start arm64 VMs. Arm64 GPU-accelerated devices are available on request.

Key points:

- Effective date: March 30, 2026

- x86 support will be restricted starting then

- No price or subscription changes due to this upgrade

- Guidance for workflows: migrate x86 workflows, recreate custom recipes on arm64

Sources:

- Genymotion SaaS is moving to arm64 — Genymotion download page: https://genymotion.com/download

- Genymotion SaaS is moving to arm64 — Support/News article: https://support.genymotion.com/hc/en-us/articles/115000969669-PayPal-license-purchase-order-received-but-no-license-key

Would you like help assessing how this affects your current projects or a step-by-step migration plan for your specific setup (CI/CD, custom recipes, or specific apps)? Also, what platforms and environments are you currently using Genymotion on (cloud, desktop, and your OS)?