OpenXR adds cross-platform spatial multitasking for XR apps

What the new OpenXR extensions do

OpenXR is getting a more practical answer to a problem that has dogged mixed-reality software for years: how to let several spatial apps share a user’s surroundings without every platform inventing its own rules. The Khronos OpenXR Working Group has released a pair of extensions called Spatial Containers, creating a cross-platform API for spatial windowing and multitasking.¹

The extensions give an application a system-managed space in which it can display XR content. Developers can move an app between a bounded mode, designed for sharing attention with other applications, and an immersive mode that takes over the display. The runtime controls where each container sits, so a user can place content where it is useful or let it follow them in an on-the-go scenario.¹

The first extensions are XR_EXT_spatial_container and XR_EXT_spatial_container_self_rendering. The former handles creation and management of spatial containers, while the latter lets apps render into them through OpenXR composition layers.¹ Khronos says the specifications and samples are already published, with implementations expected to begin arriving across the OpenXR ecosystem during 2026.¹

That is a meaningful shift from the usual XR split between a single immersive application and a handful of system-level 2D panels. The API is intended to give multiple 3D applications a common model for co-existing, receiving input and being shown or hidden as needed. In practice, the experience will still depend on support from headset runtimes, engines and individual developers.

The announcement positions the work as an open alternative to platform-specific spatial desktop APIs. Apple’s visionOS has offered a comparable shared-space model on Vision Pro, while other headsets have generally kept spatial apps more isolated. Road to VR notes that Quest currently permits one spatial app at a time alongside system features such as the dashboard and browser.²

Khronos lists Android XR, Meta Quest, SteamVR-compatible PC headsets, Steam Frame, Varjo, Magic Leap and XREAL among the wider OpenXR ecosystem. That does not mean every listed device will receive the extensions immediately: a ratified specification still needs runtime and application support before users see the benefit.

Our opinion

Spatial Containers are the sort of unglamorous plumbing XR needs if it is going to become useful beyond short, isolated demos. The clever part is not the promise of floating windows; it is giving developers a shared way to decide how an app behaves when it is no longer allowed to demand the whole view. The next test is adoption. If the major runtimes implement the extensions consistently, OpenXR could make spatial multitasking feel like a platform feature rather than a collection of bespoke tricks. If they do not, the standard will remain an appealing specification that users never encounter.

For now, developers can inspect the published registry entries and Khronos’ sample material. The extensions are available to build against, but the first compatible releases will determine whether this becomes a real cross-platform capability or simply another promising layer in XR’s still-fragmented stack.¹