Essentials

Compatibility mode

Updated: Nov 11, 2026
Compatibility mode helps older apps run on newer VR devices. After an app launches, it changes some device information returned by selected APIs.
If you’re looking for how to control which build a device receives, see Target app builds by device instead.

What is compatibility mode

In compatibility mode, selected APIs report an older model instead of the physical device. This helps existing apps avoid results they were not built or tested to handle. Compatibility mode does not change anything about the device’s physical hardware.

How compatibility mode works

Meta Quest 2, Meta Quest Pro, Meta Quest 3, Meta Quest 3S, and Meta VR Glasses support compatibility mode.
Horizon OS manages compatibility mode automatically.
When an app launches, Horizon OS checks the app’s com.oculus.supportedDevices manifest entry. Compatibility mode turns on if the entry does not list the physical device. The runtime then chooses the most recent older model that the app lists. This is the app’s compatibility model.
For Meta Quest 3, the older compatibility models are Meta Quest Pro, Meta Quest 2, and Meta Quest 1. If the manifest entry is missing, the runtime uses Quest 2 (reported as Oculus_Quest_2). This choice doesn’t depend on the app’s target Android SDK version. The fallback doesn’t require adding the Quest 2 identifier to a new app’s manifest.
To declare support for Meta VR Glasses, include vrglasses in the com.oculus.supportedDevices manifest entry.
On Horizon OS v209 and later, an app whose com.oculus.supportedDevices manifest entry includes vrglasses runs on Meta VR Glasses without compatibility mode. If the entry does not include vrglasses, Horizon OS uses compatibility mode for third-party immersive Store apps on Meta VR Glasses and applies the model-selection behavior described above.
To make a build available on Meta VR Glasses, in Store targeting, select Future devices and at least one current device. Select every current device that should receive the build.

What compatibility mode changes

In compatibility mode:
  • Device-identification APIs can report the compatibility model instead of the physical device.
  • Some APIs return only values supported by both the physical device and the compatibility model. For example, available display refresh rates are limited to rates that both models support.
  • If the app sends a compatibility-adjusted device-type result to a backend, the backend receives the compatibility model.
  • Code that uses the reported model can behave differently than it did on the device used for testing.
These changes apply only to specific APIs. Do not assume every API or backend signal reports the compatibility model.
Compatibility mode does not change CPU or GPU speed. It also does not change passthrough quality.

How can my application specify which devices are supported

The com.oculus.supportedDevices manifest entry lists the VR devices that your app supports. The runtime uses this list to decide whether to turn on compatibility mode. It also uses the list to choose the compatibility model.
The canonical com.oculus.supportedDevices identifiers are:
DevicesupportedDevices identifier
Meta Quest 2
quest2
Meta Quest Pro
questpro
Meta Quest 3
quest3
Meta Quest 3S
quest3s
Meta VR Glasses
vrglasses
Separate multiple identifiers with a pipe (|).
To declare support for all current Meta VR devices, add this element to the application node in AndroidManifest.xml:
<meta-data
    android:name="com.oculus.supportedDevices"
    android:value="quest2|questpro|quest3|quest3s|vrglasses" />
Unity and Unreal can generate this entry from project settings. If the project or engine version predates a newer device, inspect the generated manifest. Confirm that it includes every device model the app supports.

Check capabilities directly

No public API directly reports whether compatibility mode is active.
Don’t use android.os.Build.MODEL to infer whether compatibility mode is active. Don’t use it, or any single reported device value, to decide whether a feature is available.
Check for the capability that your app needs. Don’t rely only on the reported device model. Provide a fallback when a capability is unavailable.

Engine-specific guides