Important: Chrome OS isn’t a supported Unity Editor platform.
Although Chrome OS development is very similar to Android, there are specific differences that you need to be aware of. Before you start to develop your application for Chrome OS, review the requirements, feature compatibility, and known issues specific to Chrome OS.
The system requirements for Chrome OS are similar to Android development. The only difference is that there are USB connection issues. To avoid these, you can connect the Unity Editor to a Chrome OS device over Wi-Fi/Ethernet.
Unity supports all brands of Chrome OS laptops, tablets, netbooks and desktops. Chromecast devices aren’t supported. Unity supports Chrome OS version R89 and later releases on the stable release channel. As with other platforms, you can use beta and development OS builds at your own discretion.
The following table describes the features that are supported when you’re developing applications for Chrome OS.
| Features | Compatibility |
|---|---|
| x86 and x86_64 architectures | Supported only for devices running Chrome OS. These architectures aren’t supported on Android devices with an Intel processor. Both architectures support IL2CPP only. Mono isn’t supported. |
| Project Tiny | Not supported on Chrome OS x86 and x86–64 devices. |
| Havok Physics (from Unity Physics package) | Not supported. |
| Script debugging and profiling | Supported over Wi-Fi or Ethernet only using Android Debug Bridge. |
| Script only builds | Not supported. |
| Profiling and debugging in Android Studio | Supported only when your target device is in Developer Mode. For more information, refer to the Chromium documentation. |
| Unity video player | The H.264 video format is supported on Chrome OS devices. The H.265 video format isn’t supported. |