Version: 2023.1
Language : English
ChromeOS
Getting started with ChromeOS

Requirements and compatibility

Important: ChromeOS isn’t a supported Unity Editor platform.

Although ChromeOS 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 ChromeOS, review the requirements, feature compatibility, and known issues specific to ChromeOS.

Requirements

The system requirements for ChromeOS 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 ChromeOS device over Wi-Fi/Ethernet.

Unity supports all brands of ChromeOS laptops, tablets, netbooks and desktops. Chromecast devices aren’t supported. Unity supports ChromeOS 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.

Compatibility

The following table describes the features that are supported when you’re developing applications for ChromeOS.

Features Compatibility
x86 and x86_64 architectures Supported only for devices running ChromeOS. 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 ChromeOS 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 ChromeOS devices. The H.265 video format isn’t supported.

Known issues

  • Applications that support auto-rotation across all orientations can suffer from several bugs. This includes the screen auto-rotating when it shouldn’t, and Unity setting the screen to the wrong resolution.
  • Non-resizable windows don’t behave properly on ChromeOS devices that have both clamshell and tablet modes. When in tablet mode, the app goes full-screen and never goes back to its original size, even when returning to clamshell mode.
ChromeOS
Getting started with ChromeOS